MCP Protocol News - July 10, 2026

Week of: July 10, 2026

---

Overview

The MCP TypeScript SDK shipped a coordinated batch of 2.0.0-beta.3 releases across core, client, server, and framework adapter packages, introducing runtime-neutral OAuth and Bearer authentication, restoring v1 parse tolerance for legacy tool results, and adding Standard Schema support for input elicitation. The MCP specification repository saw updates to documentation and contribution policies, while the servers repository published a new release with updated packages.

Stories

1. MCP TypeScript SDK Ships 2.0.0-beta.3 with OAuth and Bearer Auth

Source: MCP TypeScript SDK Link: https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol%2Fserver%402.0.0-beta.3

The MCP TypeScript SDK released coordinated beta.3 updates for @modelcontextprotocol/server, @modelcontextprotocol/client, @modelcontextprotocol/core, @modelcontextprotocol/node, and framework adapters for Express, Fastify, and Hono. Key additions include runtime-neutral Bearer authentication via requireBearerAuth and OAuth discovery serving via oauthMetadataResponse following RFC 9728.

These changes bring standardized authentication patterns to MCP server implementations across runtimes including Cloudflare Workers. The @modelcontextprotocol/express package re-exports OAuthTokenVerifier for backward compatibility, while the Fastify and Hono adapters inherit the new server capabilities.

Impact Analysis: Server authors can now implement OAuth and Bearer authentication using runtime-neutral primitives, reducing boilerplate and improving interoperability across deployment targets.

2. SDK Restores v1 Parse Tolerance for Legacy Tool Results

Source: MCP TypeScript SDK Link: https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol%2Fcore%402.0.0-beta.3

The @modelcontextprotocol/core@2.0.0-beta.3 patch restores v1 parse tolerance for CallToolResult.content: inbound legacy-era tools/call results without content now default to [] instead of failing validation. The strict parse had caused INVALID_RESULT errors for deployed servers that return structuredContent-only results, which had been accepted by SDK v1 for years.

The fix preserves the silent-empty-success hazard guard where it matters — the 2025-era wire-seam schema still refuses to default content for a body carrying no content field. The @modelcontextprotocol/client package receives the same tolerance fix.

Impact Analysis: Teams running legacy MCP servers that omit the content field will no longer see spurious validation failures after upgrading to the v2 beta SDK.

3. SDK Adds Standard Schema Support for Input Elicitation

Source: MCP TypeScript SDK Link: https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol%2Fserver%402.0.0-beta.3

The @modelcontextprotocol/server@2.0.0-beta.3 minor release allows inputRequired.elicit() to accept a Standard Schema such as a Zod object for requestedSchema. The builder converts it to MCP's restricted form-elicitation JSON Schema, while the same schema can validate and type the response through acceptedContent() on handler re-entry. Zod formats mapping to email, uri, date, and date-time are supported.

Schemas that the restricted form cannot express — nested objects, .regex() patterns, exclusive number bounds, literal unions — are rejected before anything is sent. This gives developers a type-safe path from schema definition to runtime validation.

Impact Analysis: Builders can now use familiar Zod schemas for MCP input elicitation, reducing manual JSON Schema authoring and improving type safety across the request-response cycle.

4. Codemod Tool Updated for v2 Migration

Source: MCP TypeScript SDK Link: https://github.com/modelcontextprotocol/typescript-sdk/releases/tag/%40modelcontextprotocol%2Fcodemod%402.0.0-beta.3

The @modelcontextprotocol/codemod@2.0.0-beta.3 patch fixes a staleness issue where committed generated versions.ts files went stale after every release. The codemod now reads v2 package versions directly from workspace manifests at build time, ensuring migrated package.json files receive correct version numbers.

This change addresses a practical pain point for teams using the automated migration tool to upgrade from SDK v1 to v2 — previously, source builds could write outdated versions into migrated projects.

Impact Analysis: Teams using the codemod for v2 migration will get accurate version numbers without manual correction after each SDK release.

5. MCP Servers Repository Publishes v2026.7.10 Release

Source: MCP Servers Link: https://github.com/modelcontextprotocol/servers/releases/tag/2026.7.10

The MCP Servers repository published release v2026.7.10, updating packages including @modelcontextprotocol/server-filesystem, mcp-server-time, mcp-server-fetch, and mcp-server-git to matching versions. The release bundles updated server implementations for common MCP use cases.

These reference servers provide ready-to-deploy implementations for file system access, time queries, web fetching, and Git operations — core capabilities that MCP clients commonly consume.

Impact Analysis: Teams deploying MCP reference servers can update to the latest package versions for compatibility with the v2 SDK beta series.

6. Specification Repository Adds AI Agent Contribution Policy

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/02dd8f615a4aa6bc6f2671c1151bcd0a9d0ddfd5

The MCP specification repository added an AI agent contribution policy to AGENTS.md, establishing guidelines for automated contributions. The commit also includes a "Remote-Dev: homespace" annotation, suggesting infrastructure for agent-driven development workflows.

This policy formalizes how AI agents can participate in the MCP specification's development process, reflecting the protocol's own domain of AI-tool interaction.

Impact Analysis: Contributors using AI coding agents now have clear guidelines for submitting changes to the MCP specification repository.

7. Goose Documentation Links Updated in Specification

Source: MCP Specification Link: https://github.com/modelcontextprotocol/modelcontextprotocol/commit/ccbf06255a7ad298eb1cca4b1689a294cf424800

The MCP specification repository updated documentation links for Goose, an AI agent tool, formatting the links into a table structure. This suggests ongoing integration and documentation alignment between the MCP ecosystem and the Goose project.

Goose is one of several AI agent frameworks that implement the Model Context Protocol for tool access.

Impact Analysis: MCP documentation now points to current Goose resources, helping developers using that agent framework find relevant integration guidance.

Source Links

• MCP Servers - Release 2026.7.10
• MCP TypeScript SDK - @modelcontextprotocol/codemod@2.0.0-beta.3
• MCP TypeScript SDK - @modelcontextprotocol/core@2.0.0-beta.3
• MCP TypeScript SDK - @modelcontextprotocol/server@2.0.0-beta.3
• MCP TypeScript SDK - @modelcontextprotocol/client@2.0.0-beta.3
• MCP Specification - Add AI agent contribution policy to AGENTS.md (#3009)
• MCP Specification - docs: update Goose documentation links (#3019)