diff --git a/.github/upstream-projects.yaml b/.github/upstream-projects.yaml index d796f9509..aea12a16e 100644 --- a/.github/upstream-projects.yaml +++ b/.github/upstream-projects.yaml @@ -287,6 +287,6 @@ projects: - id: toolhive-studio repo: stacklok/toolhive-studio - version: v0.40.2 + version: v0.41.0 docs_paths: - docs/toolhive/guides-ui diff --git a/docs/toolhive/guides-ui/run-mcp-servers.mdx b/docs/toolhive/guides-ui/run-mcp-servers.mdx index aaf278727..7a5092d3b 100644 --- a/docs/toolhive/guides-ui/run-mcp-servers.mdx +++ b/docs/toolhive/guides-ui/run-mcp-servers.mdx @@ -140,7 +140,9 @@ On the **MCP Servers** page, you can manage your installed MCP servers. Each server's card includes: - The server name -- Its status (Running or Stopped) with a toggle button to start or stop it +- Its status, such as Running or Stopped, with a toggle button to start or stop + it (see [Status warnings](#status-warnings) for authentication and policy + statuses) - A menu (︙) with additional options Use the **Start/Stop** toggle to start or stop the MCP server. When you stop a @@ -169,6 +171,26 @@ When you quit the application, ToolHive prompts you to stop all running MCP servers. The running servers are recorded and ToolHive restarts them automatically the next time you launch the application. +### Status warnings + +When an authentication or policy problem keeps a server from running, ToolHive +shows its status in a warning color on both the card and table views: + +| Status label | Meaning | +| --------------------------- | -------------------------------------------------------------------------------------------------------------------------- | +| **Authentication required** | Authentication with the server failed, for example because an OAuth token refresh failed or the server rejected the token. | +| **Retrying authentication** | Token refresh is failing temporarily, and ToolHive keeps retrying. | +| **Stopped by policy** | A policy blocked the server from starting. | + +Hover over or focus on the status label to see a tooltip with the reason +ToolHive reported, when one is available. + +For these statuses, the toggle shows as off. Turn the toggle on to restart the +server. For a remote MCP server, restarting runs the sign-in flow again so you +can re-authenticate. If you need different credentials, use **Edit +configuration** to update the server's +[authorization method](./configure-mcp-servers.mdx#authorization-method) first. + ### Upgrade registry image versions For MCP servers installed locally from the registry, ToolHive shows an upgrade