{"version":"2.1.321","anchor":"synced-plugin-mcp-servers-are-left-out-without-a-flag","canonical_anchor":"synced-plugin-mcp-servers-are-left-out-without-a-flag","heading":"Synced plugin MCP servers that cannot sign in are left out without a remote switch","tier":"notice","area":"MCP","scope":"individual","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321\/e\/synced-plugin-mcp-servers-are-left-out-without-a-flag","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.321","markdown":"### Synced plugin MCP servers that cannot sign in are left out without a remote switch\n\nClaude Code now skips synced plugin MCP servers that offer no way to register for sign-in, without needing a remote switch first\n\n**What**\n\nPlugins can be synced to Claude Code, and some bring MCP servers, outside services that give Claude Code extra tools. Some of these servers need you to sign in but offer no way to register Claude Code as an OAuth client, the step that lets an app sign in. Claude Code leaves such servers out. Before, this only happened when a remote switch was on, and that switch was off by default. The switch is gone, so the check now runs on its own. The log message now says the service offered no way to register Claude Code as an OAuth client, so it cannot sign in.\n\n**Why**\n\nA synced plugin server that could never sign in is skipped instead of showing up and failing. If one of your plugin's servers is missing, this may be the reason.\n\n- Area: MCP\n- Tier: You'll notice\n- Useful: 2\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: yes"}