{"version":"2.1.281","anchor":"new-config-warning-mcp-server-defined-in-multiple-scopes-wi","canonical_anchor":"new-config-warning-mcp-server-defined-in-multiple-scopes-wi","heading":"New config warning: MCP server defined in multiple scopes with different endpoints","tier":"notice","area":"MCP","url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281\/e\/new-config-warning-mcp-server-defined-in-multiple-scopes-wi","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.281","markdown":"### New config warning: MCP server defined in multiple scopes with different endpoints\n\nClaude Code warns when an MCP server name is defined in several scopes with different endpoints, since sign-ins don't carry over\n\n**What**\n\nAn MCP server is an outside service that gives Claude extra tools. The same server name can be configured in more than one scope, meaning more than one place where configuration lives. A check flags a name defined in several scopes that point at different endpoints, which are the addresses the server is reached at.\n\nThat check now compares addresses exactly. Before, it first tidied them up in a way that could make different addresses look the same. The warning explains that OAuth tokens (saved sign-ins) are stored per endpoint, so signing in under one scope will not carry over to another. It also suggests `mcp remove` commands to clean up the duplicates.\n\n**Why**\n\nIf a server keeps asking you to sign in again, this warning can show that two definitions point at different addresses, and it tells you how to remove the extra one.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 1\/5"}