{"version":"2.1.317","anchor":"mcp-server-config-accepts-an-optional-displayname","canonical_anchor":"mcp-server-config-accepts-an-optional-displayname","heading":"MCP server settings accept an optional displayName","tier":"use","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317\/e\/mcp-server-config-accepts-an-optional-displayname","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.317","markdown":"### MCP server settings accept an optional `displayName`\n\nAn MCP server's settings can now include a displayName, and a badly formed value is ignored instead of breaking the config\n\n**What**\n\nMCP servers are outside programs that give Claude Code extra tools. Their settings now accept an optional `displayName` text field. If the value is badly formed, Claude Code drops it rather than rejecting the whole server setting.\n\n**Why**\n\nIt gives a server a field for a friendlier label, and a mistake in it will not stop the server from loading.\n\n- Area: MCP\n- Names: `displayName`\n- Tier: Use it now\n- Useful: 4\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}