{"version":"2.1.267","anchor":"mcp-tool-listing-pipeline-refactored-to-a-shared-metadata-ob","canonical_anchor":"mcp-tool-listing-pipeline-refactored-to-a-shared-metadata-ob","heading":"MCP tool-listing pipeline refactored to a shared metadata object plus overrides","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267\/e\/mcp-tool-listing-pipeline-refactored-to-a-shared-metadata-ob","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.267","markdown":"### MCP tool-listing pipeline refactored to a shared metadata object plus overrides\n\nInternal rework of how Claude Code builds MCP tool listings, with no user-facing behavior change described\n\n**What**\n\nThe internal code that builds the list of tools exposed by MCP (Model Context Protocol, a standard for connecting external tools to Claude) servers was restructured. Shared metadata for a server, such as its name, scope, prompt overrides, and telemetry info, is now built once per server, and each individual tool merges in its own overrides (such as Claude-in-Chrome or SDK server overrides) through a shared builder function, instead of each tool being assembled inline from scratch.\n\n**Why**\n\nThis is a code organization change to how MCP tool metadata is assembled internally; it does not describe a change in what tools do or how they behave.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}