{"version":"2.1.268","anchor":"mcp-discovery-can-skip-cacheconnect-when-tools-are-already","canonical_anchor":"mcp-discovery-can-skip-cacheconnect-when-tools-are-already","heading":"MCP discovery can skip cache\/connect when tools are already known","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-discovery-can-skip-cacheconnect-when-tools-are-already","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP discovery can skip cache\/connect when tools are already known\n\nMCP server setup can now skip the discovery cache and connection entirely when a server's tools are already known\n\n**What**\n\nWhen Claude Code connects to an MCP server and discovers its available tools, the setup function can now be given a pre-supplied map of tools. If a server's tools are already known this way and it isn't a live connection, discovery short-circuits straight to building the result, skipping the discovery cache lookup and skipping opening a new connection entirely.\n\n**Why**\n\nThis avoids redundant cache checks and connection attempts when the tool list for a server is already known, which should make repeated MCP setup faster in that case.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 2\/5"}