{"version":"2.1.307","anchor":"plugin-sync-leaves-out-mcp-servers-when-a-terminal-cant-reg","canonical_anchor":"plugin-sync-leaves-out-mcp-servers-when-a-terminal-cant-reg","heading":"Plugin sync has one more reason to leave out an MCP server","tier":"internal","area":"Plugins","scope":"individual","heads_up":false,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307\/e\/plugin-sync-leaves-out-mcp-servers-when-a-terminal-cant-reg","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.307","markdown":"### Plugin sync has one more reason to leave out an MCP server\n\nWhen syncing plugins, Claude Code now has an extra condition under which it leaves a plugin's MCP server out\n\n**Unclear.** The two extra checks that cause a server to be left out are not identified.\n\n**What**\n\nWhen Claude Code syncs your plugins (add-ons that bundle extra commands, skills or tools), it decides which of their MCP servers to bring along. An MCP server is a separate program that gives Claude extra tools. Before, a server was left out only because of where it came from or because of a setting. Now, when a sign-in related setting is on, Claude Code also leaves a server out when two further checks both hold.\n\n**Why**\n\nThis may change which MCP servers from synced plugins actually load for you.\n\n- Area: Plugins\n- Tier: Under the hood\n- Useful: 1\/5\n- Signal: 2\/5\n- Scope: individual\n- Heads-up: no"}