Follow Discord
Sweep 22 Oct 2026 · 21:04Z Build v2.1.309 528 read Stable v2.1.308 Latest v2.1.309 Next v2.1.309 Feeds RSS JSON llms.txt llms-full.txt Unofficial
HomeReleasesv2.1.309entry #2

Claude Code v2.1.309 ·

Organization connectors appear as their own kind of MCP server

Claude Code adds organization-provided MCP connectors with reserved org-connector names, new list and relay handlers and an orgConnectors scope

Group of 3 You'll notice Nothing to try yet In Development
JSON All of v2.1.309
You'll noticeTier: how much it should matter to you
4Useful: my rating, 1 to 5
4Signal: worth watching, 1 to 5
ConnectorsArea: what it touches
In DevelopmentKind: in v2.1.309,
What probably matters to youSection of the release

Unclear Nothing shows what calls these handlers, so it is unknown whether you can use organization connectors yet.

What

MCP servers are add-ons that give Claude extra tools. Claude Code now has groundwork for MCP servers provided by your organization, called org connectors:

  • 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.
  • 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.
  • Server and tool names starting with org-connector- or org_connector_ (after names are normalized) are now reserved and count as a name collision.
  • MCP server listing no longer filters out some names, and callerLogsSharedEvents now applies to all lists except plugin lists.

The 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."

Why

If 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.

How sure we are
Something disagreesSomething we can check disagrees with this entry, or the writer said they could not settle it.
The writer flagged doubtNothing shows what calls these handlers, so it is unknown whether you can use organization connectors yet.

See this entry in the whole of v2.1.309 →

Feedback