{"version":"2.1.284","anchor":"tengu-sdk-result-telemetry-gains-turn-index-and-mcp-pending","canonical_anchor":"tengu-sdk-result-telemetry-gains-turn-index-and-mcp-pending","heading":"SDK usage data now counts the turn and the MCP servers still connecting","tier":"internal","area":"Telemetry","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284\/e\/tengu-sdk-result-telemetry-gains-turn-index-and-mcp-pending","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.284","markdown":"### SDK usage data now counts the turn and the MCP servers still connecting\n\nEach SDK result report now records the turn number and how many MCP servers were still connecting when the turn started and ended\n\n**What**\n\nWhen Claude Code runs through the SDK, it records a report for each result. That report now includes:\n\n- `turn_index`: which turn of the conversation this was\n\n- `mcp_pending_at_start`: how many MCP servers were still connecting when the turn began\n\n- `mcp_pending_at_end`: how many were still connecting when it ended\n\nMCP servers are add-ons that give Claude extra tools.\n\n**Why**\n\nThis lets Anthropic see how often a turn starts before all of a session's MCP servers have finished connecting.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}