{"version":"2.1.285","anchor":"mcp-connect-waiting-logic-for-plugin-function-hooks","canonical_anchor":"mcp-connect-waiting-logic-for-plugin-function-hooks","heading":"Plugins now explain why their MCP servers did not connect","tier":"notice","area":"Plugins","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285\/e\/mcp-connect-waiting-logic-for-plugin-function-hooks","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.285","markdown":"### Plugins now explain why their MCP servers did not connect\n\nPlugin MCP servers now report clear reasons when they are not connected, such as sign-in needed, still connecting, `--bare` or policy blocks\n\n**Unclear.** Whether this plugin hook feature is available to users yet is not clear.\n\n**What**\n\nMCP servers are outside tools Claude Code can connect to, and plugins can bring their own. Claude Code now explains when a plugin's MCP server is not available:\n\n- Waiting to connect: plugin hooks (plugin code that runs at set moments) that need an MCP server now wait for it to finish connecting. If it fails, they say why, for example that the server `needs you to sign in; run \/mcp`, or that it \"is still connecting after\" a period of time.\n\n- Reasons for not connecting: a plugin's MCP server can be refused because of safe mode, `--bare`, `--strict-mcp-config`, a remote client, a managed MCP setup that allows only its own servers, the server not being approved, being disabled, or being blocked by policy. For example: \"This session runs with --bare, which connects no plugin servers.\"\n\n**Why**\n\nWhen a plugin's tools are missing, you now get a specific reason instead of silence, and often the fix, such as signing in with `\/mcp` or starting without `--bare`.\n\n- Area: Plugins\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 2\/5"}