{"version":"2.1.319","anchor":"mcp-results-can-carry-meta-through-remote-tool-envelopes-m","canonical_anchor":"mcp-results-can-carry-meta-through-remote-tool-envelopes-m","heading":"MCP tool results keep their extra details when they pass through remote tools","tier":"notice","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319\/e\/mcp-results-can-carry-meta-through-remote-tool-envelopes-m","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.319","markdown":"### MCP tool results keep their extra details when they pass through remote tools\n\nMCP extra details in the _meta field now survive the remote tool path, and finished MCP tasks include delivery details in their notice\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Their results can carry a `_meta` field with extra details. Claude Code now handles these in more places:\n\n- results from tools that run remotely now pass the `_meta` field through instead of dropping it\n\n- the list of tools used can mark an entry as an MCP tool\n\n- when an MCP task finishes, its completion notice now includes details about how the task's result is delivered\n\nClaude Code also records cases where the extra details could not be passed on, such as when a hook rewrote the output or the result was over a size limit.\n\n**Why**\n\nTools that rely on `_meta` to carry information alongside their results now keep it when called through the remote path.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}