{"version":"2.1.315","anchor":"auto-connect-of-a-dynamic-mcp-server-after-login-completes","canonical_anchor":"auto-connect-of-a-dynamic-mcp-server-after-login-completes","heading":"An MCP server can be connected automatically after you sign in","tier":"notice","area":"MCP","scope":"both","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315\/e\/auto-connect-of-a-dynamic-mcp-server-after-login-completes","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.315","markdown":"### An MCP server can be connected automatically after you sign in\n\nAfter sign-in, Claude Code can now load a dynamic MCP setup and add a server, unless strict or managed MCP settings apply\n\n**Unclear.** It is not clear which server gets added or what decides whether one is added.\n\n**What**\n\nMCP servers are add-on services that give Claude Code extra tools. Claude Code now waits for sign-in to finish, then loads a dynamic MCP setup and may add a server from it. It does nothing while that setup is still loading. It respects strict MCP configuration and managed MCP configuration, so these can stop the server being added.\n\n**Why**\n\nAn MCP server may now appear automatically after you sign in, without you adding it yourself.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 3\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: no"}