Illustration for: Anthropic's Claude Adopts New MCP 2026-07-28 Spec

Anthropic's Claude Adopts New MCP 2026-07-28 Spec

Anthropic expanded Claude's support for the new MCP 2026-07-28 specification, adding a stateless core, stronger OAuth and OIDC authorization, and versioned extensions for enterprise Apps and Tasks integrations.

TC
By the AI Desk
Edited by Trace Cohen · Early-stage VC & angel · Founder, New York Venture Partners
1 min read
ShareXLinkedInEmail

THE RUNDOWN

1

The MCP 2026-07-28 spec update introduces a stateless core architecture along with stronger OAuth and OIDC authorization support, addressing enterprise security requirements that have been a gating factor for broader MCP adoption

2

New connector features include embedded UI, enterprise-managed authentication, observability, and private network tunnels -- all aimed squarely at enterprise IT teams evaluating agent connectivity standards rather than individual developers

3

MCP has become the closest thing to a shared standard for connecting AI agents to external tools and data since Anthropic open-sourced the protocol, and this update signals the standard maturing toward enterprise-grade requirements rather than just developer convenience

TC

The VC Read · Trace's Take

Trace Cohen

A cross-lab standard maturing toward enterprise-grade auth is genuinely underrated news this week compared to the earnings and chip headlines. If MCP holds as the shared connectivity layer across OpenAI, Google, and Anthropic's agents, that's the rails infrastructure founders can build durable companies on top of without betting the business on a single lab staying dominant.

Analysis

Anthropic expanded Claude's support for the newly published MCP 2026-07-28 specification, the latest revision to the Model Context Protocol that Anthropic open-sourced as a standard for connecting AI models and agents to external tools and data sources. The update introduces a stateless core architecture, stronger OAuth and OIDC-based authorization, and versioned extensions covering enterprise use cases like embedded UI, enterprise-managed authentication, observability, and private network tunnels.

The enterprise-security focus of this revision is the notable shift. Earlier MCP versions prioritized developer ergonomics and quick tool integration; this spec update is explicitly aimed at the authentication, auditability, and network-isolation requirements that enterprise security and compliance teams have been citing as blockers to broader agent-connectivity adoption. That's a maturity signal for the protocol as a category-defining standard rather than just a convenient integration layer.

The enterprise-security focus of this revision is the notable shift.

MCP's adoption curve matters beyond Anthropic's own ecosystem: OpenAI, Google, and a wide range of tooling vendors have adopted or built compatibility layers for the protocol since its release, making it a rare instance of cross-lab technical standardization in a market otherwise defined by competing proprietary ecosystems. For infrastructure and dev-tools founders, a maturing MCP spec with enterprise-grade auth lowers the barrier to building agent-connectivity products that work across multiple frontier labs' agents rather than locking into a single vendor's proprietary tool-calling format -- a meaningful de-risking of a category that looked more fragmented a year ago.

ShareXLinkedInEmail

Key Sources

2 sources

Reported by Anthropic · Analysis by Value Add Pulse.

← Back to Pulse

THE WIRE in your inbox— Tech, startup & VC news with Trace's take. Free, no spam.