{"version":"2.1.317","anchor":"mcp-server-displayname-stripped-for-non-claudeai-proxy-serve","canonical_anchor":"mcp-server-displayname-stripped-for-non-claudeai-proxy-serve","heading":"Display names are dropped from ordinary MCP server settings","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-server-displayname-stripped-for-non-claudeai-proxy-serve","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### Display names are dropped from ordinary MCP server settings\n\nClaude Code now removes `displayName` from MCP server settings unless the server is of type `claudeai-proxy`\n\n**What**\n\nMCP servers are outside services that add tools to Claude Code. When Claude Code reads and tidies up the settings for an MCP server, it now removes the `displayName` field. The only exception is a server of type `claudeai-proxy`, which keeps it. Before, the field was left in place.\n\n**Why**\n\nIf you set `displayName` on an ordinary MCP server, Claude Code no longer passes it through.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}