{"version":"2.1.248","anchor":"telemetry-events-can-now-carry-mcp-server-and-tool-names","canonical_anchor":"telemetry-events-can-now-carry-mcp-server-and-tool-names","heading":"Telemetry events can now carry MCP server and tool names","tier":"internal","area":"Telemetry","scope":null,"heads_up":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248\/e\/telemetry-events-can-now-carry-mcp-server-and-tool-names","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.248","markdown":"### Telemetry events can now carry MCP server and tool names\n\nTelemetry events can now include MCP server and tool names plus account and org identifiers.\n\n**What**\n\nThe event serialiser gained fields for the MCP server name and MCP tool name, plus a client-reported authentication block holding account and organization identifiers, alongside the existing session, skill, plugin and marketplace fields. These are sent whenever the calling code fills them in.\n\n**Evidence**\n\n`mcp_server_name`\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 2\/5\n- Signal: 3\/5"}