[DOCS] Document plugin MCP server suppression when duplicating an org-managed connector

Documentation Type

Missing documentation (feature not documented)

Documentation Location

https://code.claude.com/docs/en/mcp
https://code.claude.com/docs/en/plugins-reference

Section/Topic

"Plugin-provided MCP servers" section in the MCP page, and the "MCP servers" section in the Plugins reference page.

Current Documentation

From mcp.md, "Plugin-provided MCP servers" section:

How plugin MCP servers work: Plugins define MCP servers in .mcp.json at the plugin root or inline in plugin.json When a plugin is enabled, its MCP servers start automatically Plugin MCP tools appear alongside manually configured MCP tools Plugin servers are managed through plugin installation (not /mcp commands)

From plugins-reference.md, "Integration behavior":

Plugin MCP servers start automatically when the plugin is enabled Servers appear as standard MCP tools in Claude's toolkit Server capabilities integrate seamlessly with Claude's existing tools Plugin servers can be configured independently of user MCP servers

What's Wrong or Missing?

As of v2.1.83, plugin MCP servers that duplicate an org-managed connector (a connector configured by an admin via claude.ai/settings/connectors on Team or Enterprise plans) are now suppressed rather than establishing a second connection. This prevents duplicate tool sets and redundant connections.

Neither the MCP page nor the Plugins reference page documents this suppression behavior:

1. The docs say plugin MCP servers "start automatically when the plugin is enabled" with no mention of the suppression exception for org-managed connectors.
2. The term "org-managed connector" does not appear anywhere in the documentation.
3. There is no explanation of how or why a plugin MCP server might be suppressed, or where users can observe the suppression.
4. The /plugin menu reportedly shows suppression notices (per the v2.1.71 entry for manually-configured deduplication), but the docs do not mention this visibility mechanism for the org-managed connector case.

Users on Team or Enterprise plans who install a plugin bundling an MCP server that matches an org-deployed connector may be confused when the plugin's MCP server does not appear active, with no documentation explaining the expected behavior.

Suggested Improvement

Add a note in the "Plugin-provided MCP servers" section of mcp.md explaining the deduplication and suppression behavior:

Deduplication with org-managed connectors: If a plugin's MCP server duplicates an org-managed connector (a connector configured by your Team or Enterprise admin at claude.ai/settings/connectors), the plugin server is suppressed and the org-managed connector is used instead. This prevents duplicate connections and tool sets. Suppressed plugin servers are visible in the /plugin menu.

Similarly, update the "Integration behavior" list in the MCP servers section of plugins-reference.md to note the suppression behavior.

Optionally, add a brief mention in the "Use MCP servers from Claude.ai" section of mcp.md explaining that org-managed connectors take precedence over plugin-bundled servers that cover the same endpoint.

Impact

Medium - Makes feature difficult to understand

Additional Context

• Introduced in v2.1.83 (org-managed connector case).
• A related but distinct deduplication behavior for manually-configured servers (same command/URL) was introduced in v2.1.71 and is also undocumented in the feature docs (only in the changelog).
• Source: Claude Code changelog at https://code.claude.com/docs/en/changelog