{"version":"2.1.307","anchor":"mcp-oauth-flow-start-telemetry-gets-extra-fields","canonical_anchor":"mcp-oauth-flow-start-telemetry-gets-extra-fields","heading":"More details recorded when signing in to an MCP server starts","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/mcp-oauth-flow-start-telemetry-gets-extra-fields","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### More details recorded when signing in to an MCP server starts\n\nThe usage data recorded when an MCP server sign-in begins now includes extra details taken from the server's settings and its redirect address\n\n**What**\n\nSome MCP servers (add-on services that give Claude extra tools) ask you to sign in through your browser. When that sign-in starts, Claude Code records some usage data. That record now carries extra details taken from the server's settings and from the address the browser is sent back to after signing in.\n\n**Why**\n\nThis only changes recorded data. Signing in works the same way.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}