{"version":"2.1.299","anchor":"mcp-serve-caller-can-log-shared-events-toolscall-telemetr","canonical_anchor":"mcp-serve-caller-can-log-shared-events-toolscall-telemetr","heading":"Claude Code as an MCP server can leave tool call records to its host","tier":"internal","area":"MCP Serve","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-serve-caller-can-log-shared-events-toolscall-telemetr","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### Claude Code as an MCP server can leave tool call records to its host\n\nWhen running as an MCP server, Claude Code skips its own records of tool call outcomes if the calling program says it logs them\n\n**What**\n\nClaude Code can run as an MCP server, offering its tools to another program. When the calling program signals, through the details sent with a request, that it records certain usage events itself, Claude Code now skips its own records of whether a tool call succeeded or failed. It also tells its permission checks about this. Before, it always recorded the outcome.\n\n**Why**\n\nThe same tool call is not counted twice when both the host program and Claude Code would record it.\n\n- Area: MCP Serve\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}