{"version":"2.1.292","anchor":"mcp-toolcommand-listing-servers-appear-before-resources-lo","canonical_anchor":"mcp-toolcommand-listing-servers-appear-before-resources-lo","heading":"MCP servers can be listed before their resources finish loading","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/mcp-toolcommand-listing-servers-appear-before-resources-lo","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### MCP servers can be listed before their resources finish loading\n\nClaude Code can now register an MCP server's tools and commands before fetching its resources, and a later resource failure no longer marks it failed\n\n**Unclear.** It is not clear what turns on the early-registration path or when it applies.\n\n**What**\n\nAn MCP server is an outside program that gives Claude extra tools. When Claude Code connects to one, it can now take a second path:\n\n- It registers the server's tools and commands first.\n\n- It fetches the server's resources (files or data the server shares) afterwards.\n\n- If that later resource fetch fails, the server is no longer marked as failed.\n\nPreviously the server was registered only once its tools, commands and resources had all loaded. MCP prompt commands also gain a check that stops them with an error before they run.\n\n**Why**\n\nOn this path an MCP server can show up as connected sooner, without waiting on resources.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}