{"version":"2.1.301","anchor":"sdk-type-mcp-servers-can-now-be-recognised-as-the-ccr-server","canonical_anchor":"sdk-type-mcp-servers-can-now-be-recognised-as-the-ccr-server","heading":"SDK-type MCP servers can now be recognised as one of Claude Code's own servers","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301\/e\/sdk-type-mcp-servers-can-now-be-recognised-as-the-ccr-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.301","markdown":"### SDK-type MCP servers can now be recognised as one of Claude Code's own servers\n\nA check that recognises a particular built-in session MCP server now also accepts SDK-type servers that meet several conditions\n\n**Unclear.** What being recognised as this server allows or changes is not stated.\n\n**What**\n\nMCP servers are add-on programs that give Claude Code extra tools. Claude Code has a check that recognises one particular server of its own used inside sessions. Before, only http servers added during a session could match. Servers of type `sdk` can now match too, when all of these hold:\n\n- the server announces a matching server ID\n\n- its name is the expected one\n\n- it is not running in remote mode\n\n- a particular environment setting is not set\n\n**Why**\n\nThis changes which servers Claude Code treats as this particular first-party server.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}