{"version":"2.1.281","anchor":"claude-in-chrome-mcp-config-resolution-waits-on-a-dynamic-c","canonical_anchor":"claude-in-chrome-mcp-config-resolution-waits-on-a-dynamic-c","heading":"Claude in Chrome: MCP config resolution waits on a dynamic-config step","tier":null,"area":null,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/claude-in-chrome-mcp-config-resolution-waits-on-a-dynamic-c","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### Claude in Chrome: MCP config resolution waits on a dynamic-config step\n\nFor Claude in Chrome, working out the startup MCP settings now waits for a dynamic-config step first\n\n**Unclear.** The finding does not say what the dynamic-config step does or how it changes anything a user sees.\n\n**What**\n\nFor Claude in Chrome, Claude Code now runs a step flagged `hasDynamicMcpConfig` before it settles on which MCP servers (outside programs that give Claude extra tools) to start with.\n\n**Why**\n\nIn practice, the MCP setup at startup is decided only after that step finishes."}