Claude✓ ReviewedAnnounced 28 July 2026Reviewed 11 October 2026MCP grew up: stateless, versioned and wired for enterprise identity.
Reviewed editorial Update
MCP grew up: stateless, versioned and wired for enterprise identity.
The MCP 2026-07-28 update moves the protocol to a stateless request-response core, versions its extensions, and aligns auth with OAuth 2.0 and OIDC so connectors can be provisioned through Entra or Okta.
What changed
Anthropic brought the MCP 2026-07-28 revision to Claude. The protocol's core became stateless request-response, which suits serverless and edge deployment; MCP Apps and Tasks moved under a versioned extensions framework for interactive UI and long-running work; and authorisation now follows production OAuth 2.0 and OIDC, connecting to enterprise identity systems. Claude's connector directory already lists more than 950 MCP servers.
Why it matters
The connection standard affects which apps an AI tool can reach and whose permissions it uses. Check how access is authenticated before connecting work systems. The announced identity controls still need to be configured by your organisation.
Bit’s takeaway
The human take
A person still decides which connectors the organisation trusts; the protocol only makes that decision enforceable.
Turn this into a workflow
Bring your task to Bit.
Bit reevaluates the recorded facts when you ask. Historical recommendations do not approve a current action.
Ask Bit about my taskSource-backed facts
- Anthropic brought the MCP 2026-07-28 revision to Claude: a stateless request-response core, versioned Apps and Tasks extensions, and authorisation aligned with OAuth 2.0 and OIDC for enterprise identity systems.Reviewed
Technical record
[claude-mcp-update-fact; official_fact; product_fact; reviewed 2026-10-11; sources: Anthropic blog — bringing MCP 2026-07-28 to Claude (https://claude.com/blog/bringing-mcp-2026-07-28-to-claude)] Anthropic brought the MCP 2026-07-28 revision to Claude: a stateless request-response core, versioned Apps and Tasks extensions, and authorisation aligned with OAuth 2.0 and OIDC for enterprise identity systems.
Sources and method