{"version":"2.1.299","anchor":"mcp-task-telemetry-events-and-tool-search-model-list","canonical_anchor":"mcp-task-telemetry-events-and-tool-search-model-list","heading":"More usage reporting for MCP tasks","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299\/e\/mcp-task-telemetry-events-and-tool-search-model-list","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.299","markdown":"### More usage reporting for MCP tasks\n\nClaude Code now records separate usage events when an MCP task starts, stops and delivers its result\n\n**What**\n\nClaude Code now records usage events for three points in the life of an MCP task: when it starts, when it stops and when it delivers its result. MCP (Model Context Protocol) is the system that lets Claude Code connect to outside tools and services. An internal helper that lists models also now returns its list in a different shape.\n\n**Why**\n\nThis gives finer-grained reporting on how MCP tasks run. It does not change what you see.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}