{"version":"2.1.309","anchor":"mcp-status-ignores-some-clients","canonical_anchor":"mcp-status-ignores-some-clients","heading":"\/mcp leaves out some more servers from its counts and actions","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/mcp-status-ignores-some-clients","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### \/mcp leaves out some more servers from its counts and actions\n\nThe inline \/mcp command now skips some additional servers in its counts and in reconnect, enable and disable, as it already did for the IDE\n\n**Unclear.** Which servers are now left out is not stated.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. The inline `\/mcp` command already ignored the IDE connection. It now also ignores some other servers. These are left out of:\n\n- the server counts\n\n- `reconnect`\n\n- `enable` and `disable`\n\n**Why**\n\nSome MCP servers may no longer show up in `\/mcp` output or respond to its commands.\n\n- Area: MCP\n- Names: `\/mcp`\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}