{"version":"2.1.268","anchor":"mcp-connect-now-threads-a-knownlistings-set-through-server","canonical_anchor":"mcp-connect-now-threads-a-knownlistings-set-through-server","heading":"MCP connect now threads a 'knownListings' set through server connection to skip redundant discovery","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-connect-now-threads-a-knownlistings-set-through-server","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP connect now threads a 'knownListings' set through server connection to skip redundant discovery\n\nClaude Code now skips redundant tool\/resource discovery for MCP servers it already has a listing for\n\n**What**\n\nWhen connecting to MCP servers (external tool providers via the Model Context Protocol), Claude Code now passes along a set of 'known listings' it already has. A server that's already in this known set is now also treated as eligible to always be loaded.\n\n**Why**\n\nThis avoids repeating discovery work for MCP servers whose tools, commands, and resources are already known, which should make connecting to already-known servers faster.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}