{"version":"2.1.290","anchor":"built-in-mcp-container-server-name","canonical_anchor":"built-in-mcp-container-server-name","heading":"Claude Code's MCP tool naming now refers to a container server","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/built-in-mcp-container-server-name","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### Claude Code's MCP tool naming now refers to a container server\n\nClaude Code now refers to an MCP server name, mcp__container, but nothing appears to use it yet\n\n**Unclear.** It is not clear whether anything in Claude Code actually uses this server name yet.\n\n**What**\n\nMCP (Model Context Protocol) is the way Claude Code connects to outside tool servers, and their tools get names that start with `mcp__`. Claude Code now refers to the name `mcp__container` beside that naming prefix. A placeholder function next to it returns nothing.\n\n**Why**\n\nThe name may point to tools hosted inside a container, which is a sealed-off environment for running programs. Because the placeholder returns nothing, this has no visible effect in this build.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 4\/5\n- Scope: individual\n- Heads-up: no"}