{"version":"2.1.296","anchor":"telemetry-for-auto-approved-project-mcp-servers","canonical_anchor":"telemetry-for-auto-approved-project-mcp-servers","heading":"Usage data now counts project MCP servers that were approved automatically","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/telemetry-for-auto-approved-project-mcp-servers","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Usage data now counts project MCP servers that were approved automatically\n\nOnce per session, Claude Code reports how many project `.mcp.json` servers were approved by settings, by bypass or without asking\n\n**What**\n\nMCP servers are outside programs that give Claude extra tools, and a project can list them in a `.mcp.json` file. Once per session, Claude Code now reports in its usage data how many of those project servers were approved:\n\n- by your settings\n\n- by bypass mode\n\n- non-interactively, without a prompt\n\nThe count is split by the connection type each server uses. A second new report records the outcome of MCP message streams.\n\n**Why**\n\nThese reports describe how project MCP servers get approved. They do not change how servers are approved or connected.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}