{"version":"2.1.309","anchor":"org-connector-mcp-listrelay-handlers-listorgconnectormcpse","canonical_anchor":"org-connector-mcp-listrelay-handlers-listorgconnectormcpse","heading":"Organization connectors appear as their own kind of MCP server","tier":"notice","area":"Connectors","scope":"both","heads_up":true,"url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309\/e\/org-connector-mcp-listrelay-handlers-listorgconnectormcpse","release_url":"https:\/\/changelogs.core-directive.com\/v\/2.1.309","markdown":"### Organization connectors appear as their own kind of MCP server\n\nClaude Code adds organization-provided MCP connectors with reserved org-connector names, new list and relay handlers and an orgConnectors scope\n\n**Unclear.** Nothing shows what calls these handlers, so it is unknown whether you can use organization connectors yet.\n\n**What**\n\nMCP servers are add-ons that give Claude extra tools. Claude Code now has groundwork for MCP servers provided by your organization, called org connectors:\n\n- The listing of plugins and MCP servers gains an `orgConnectors` group next to the existing project and plugin groups, and listing it runs under its own `orgConnectors` scope.\n\n- New handlers, `ListOrgConnectorMcpServers` and `RelayOrgConnectorMcpMessage`, accept `servers` only as http or sse entries with https addresses and names starting with `org-connector-`. Only their definitions are visible.\n\n- Server and tool names starting with `org-connector-` or `org_connector_` (after names are normalized) are now reserved and count as a name collision.\n\n- MCP server listing no longer filters out some names, and `callerLogsSharedEvents` now applies to all lists except plugin lists.\n\nThe same change adds a separate message for an upload that was not run because it needs a person's approval that cannot be given here yet: \"Nothing was uploaded, and nothing else in this call ran.\"\n\n**Why**\n\nIf you named one of your own MCP servers or tools with an `org-connector-` or `org_connector_` prefix, it will now be treated as a collision. Otherwise this prepares for connectors managed by an organization rather than configured by you.\n\n- Area: Connectors\n- Tier: You'll notice\n- Useful: 4\/5\n- Signal: 4\/5\n- Scope: both\n- Heads-up: yes\n- Present in the build but not switched on"}