{"version":"2.1.283","anchor":"mcp-oauth-sign-in-refuses-to-start-when-the-server-url-is-mi","canonical_anchor":"mcp-oauth-sign-in-refuses-to-start-when-the-server-url-is-mi","heading":"MCP sign-in stops early with a clear message when the server URL is bad","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283\/e\/mcp-oauth-sign-in-refuses-to-start-when-the-server-url-is-mi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.283","markdown":"### MCP sign-in stops early with a clear message when the server URL is bad\n\nMCP OAuth sign-in now refuses to start when the server URL is missing or invalid, and tells you to fix it\n\n**What**\n\nMCP servers are outside tools and data sources that Claude Code can connect to, and some ask you to sign in with OAuth, a standard sign-in flow. Before starting that sign-in, Claude Code now checks that the server's URL is valid. If it is missing or not a valid URL, sign-in does not start. You see the server's own configuration error if it has one, or otherwise a message saying the URL is missing or invalid and that you should fix it in the server's MCP config, or set the environment variable it uses, and try again. Before, sign-in went ahead with the bad URL.\n\n**Why**\n\nAn MCP config whose URL depends on an environment variable you have not set now gets a clear message instead of an obscure sign-in failure.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}