{"version":"2.1.296","anchor":"mcp-plugin-config-error-check-handles-dotted-keys","canonical_anchor":"mcp-plugin-config-error-check-handles-dotted-keys","heading":"Check for missing MCP server settings looks values up differently","tier":"internal","area":"MCP","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296\/e\/mcp-plugin-config-error-check-handles-dotted-keys","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.296","markdown":"### Check for missing MCP server settings looks values up differently\n\nWhen an MCP server needs configuration, Claude Code now finds the required values through a lookup step instead of reading them directly\n\n**Unclear.** Whether this stops values with dots in their names being wrongly reported as missing is not stated.\n\n**What**\n\nAn MCP server is a connector that gives Claude Code extra tools. Some need configuration before they can start, and Claude Code checks that the required values are present, showing a message that the server \"needs configuration before it can start\" when they are not. That check now finds each value through a lookup step instead of reading it directly.\n\n**Why**\n\nThe way Claude Code decides a required value is missing has changed.\n\n- Area: MCP\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 0\/5\n- Scope: individual\n- Heads-up: no"}