{"version":"2.1.293","anchor":"mcp-resource-listing-and-cached-tools-now-awaitedbatched-l","canonical_anchor":"mcp-resource-listing-and-cached-tools-now-awaitedbatched-l","heading":"MCP resource and tool loading reworked, with groundwork for cutting large results","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293\/e\/mcp-resource-listing-and-cached-tools-now-awaitedbatched-l","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.293","markdown":"### MCP resource and tool loading reworked, with groundwork for cutting large results\n\nClaude Code now loads MCP resources and cached tools step by step, and has a new marker for trimming large MCP results\n\n**Unclear.** Whether large MCP results are actually cut short in this build, and how much of a result a reader would lose.\n\n**What**\n\nMCP (Model Context Protocol) is the standard way to connect Claude Code to outside tools and data sources, called MCP servers. Several parts of how Claude Code handles them have changed:\n\n- Listing an MCP server's resources (the files or data it offers) now waits on a helper and is built in batches instead of all at once.\n\n- Building the list of tools that were saved from an earlier connection also now waits on a helper.\n\n- A new feature marker exists for cutting down large results returned by MCP servers.\n\n- For remote MCP connections, Claude Code now recognises the messages that start a connection, and can carry the ID of the tool call that caused a request.\n\n**Why**\n\nTogether these point to changes in how large MCP results are limited.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}