{"version":"2.1.290","anchor":"mcp-tools-now-carry-mcpinfo","canonical_anchor":"mcp-tools-now-carry-mcpinfo","heading":"MCP tools now carry details about the server they come from","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290\/e\/mcp-tools-now-carry-mcpinfo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.290","markdown":"### MCP tools now carry details about the server they come from\n\nTools that come from an MCP server now carry information about that server inside Claude Code\n\n**Unclear.** It is not clear which parts of Claude Code read this server information or whether anything visible changes because of it.\n\n**What**\n\nMCP (Model Context Protocol) is a way to plug outside tools into Claude Code from a separate program called an MCP server. Each tool that comes from an MCP server now carries a record of information about that server, held alongside the tool's own definition. This field was not there before.\n\n**Why**\n\nOther parts of Claude Code can now tell which MCP server a tool belongs to by looking at the tool itself.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}