{"version":"2.1.268","anchor":"mcp-connection-telemetry-now-records-server-instructions-len","canonical_anchor":"mcp-connection-telemetry-now-records-server-instructions-len","heading":"MCP connection telemetry now records server instructions length\/truncation","tier":"internal","area":"MCP","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268\/e\/mcp-connection-telemetry-now-records-server-instructions-len","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.268","markdown":"### MCP connection telemetry now records server instructions length\/truncation\n\nMCP connection telemetry now records the length of a server's instructions and whether they were truncated\n\n**What**\n\nThe `tengu_mcp_server_connection_succeeded` telemetry event, sent when Claude Code successfully connects to an MCP (Model Context Protocol) server, now includes two new fields: `instructionsLength`, the character count of the instructions text the server returned, and `instructionsTruncated`, which is true when that text is longer than 2048 characters.\n\n**Why**\n\nThis lets Claude Code track how often MCP servers send unusually long instructions and whether those instructions get cut off, which can affect how well the server's guidance reaches the model.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5"}