{"version":"2.1.292","anchor":"mcp-resource-reads-can-be-served-by-an-alternate-handler-bef","canonical_anchor":"mcp-resource-reads-can-be-served-by-an-alternate-handler-bef","heading":"MCP resource reads try another handler before asking the server","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292\/e\/mcp-resource-reads-can-be-served-by-an-alternate-handler-bef","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.292","markdown":"### MCP resource reads try another handler before asking the server\n\nWhen reading a resource from an MCP server, Claude Code now tries another handler first and only asks the server if that handler does not answer\n\n**Unclear.** It is not stated what the other handler is or which resource reads it answers.\n\n**What**\n\nMCP (Model Context Protocol) is the way Claude Code connects to external tools and data sources, called MCP servers. Those servers can offer resources, such as files or records, that Claude Code can read.\n\nWhen Claude Code reads one of these resources, it now tries a different handler first. It only sends the request to the MCP server when that handler does not supply the resource. Before, every read went straight to the server.\n\n**Why**\n\nIn practice, some resource reads may now be answered without the MCP server being asked.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5\n- Scope: individual\n- Heads-up: no"}