{"version":"2.1.295","anchor":"mcp-tool-result-meta-now-passed-through-a-transform-and-re","canonical_anchor":"mcp-tool-result-meta-now-passed-through-a-transform-and-re","heading":"MCP result metadata now comes from the tool result and is converted","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295\/e\/mcp-tool-result-meta-now-passed-through-a-transform-and-re","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.295","markdown":"### MCP result metadata now comes from the tool result and is converted\n\nClaude Code now takes an MCP tool result's `_meta` from the result itself and converts it, and also converts the metadata it sends\n\n**Unclear.** It is not shown what the conversion steps change in the metadata.\n\n**What**\n\nMCP (Model Context Protocol) is how Claude Code connects to outside tools, and `_meta` is a block of extra information that can ride along with a request or a result.\n\nTwo things are different:\n\n- The `_meta` on a tool's result is now taken from the tool result itself and passed through a conversion step. Before, it was copied straight across from a different object.\n\n- The metadata Claude Code sends with a tool request is now also passed through a conversion step instead of being sent as it is.\n\n**Why**\n\nThis may change the extra details an MCP server receives with a request, or that come back with a result.\n\n- Area: MCP\n- Names: `_meta`\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}