{"version":"2.1.317","anchor":"mcp-standard-key-server-key-moved-event","canonical_anchor":"mcp-standard-key-server-key-moved-event","heading":"Claude Code reports when an MCP server's settings key is moved","tier":"internal","area":"Telemetry","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-standard-key-server-key-moved-event","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Claude Code reports when an MCP server's settings key is moved\n\nClaude Code now sends a one-time usage report when an MCP server's key moves, and MCP server settings gain a displayName field\n\n**Unclear.** Whether `displayName` is something you can set yourself, and what causes a server's key to move, is not stated.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools, and each one is listed in Claude Code's settings under a key, which is its name in the configuration. Claude Code now sends a one-time report in its usage reporting when a server's key has moved. Before, it only reported when it had kept older names.\n\nThe MCP server configuration also gains a `displayName` field.\n\n**Why**\n\nTogether these point to Claude Code moving how MCP servers are named in its settings.\n\n- Area: Telemetry\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 1\/5\n- Scope: individual\n- Heads-up: no"}