MCP Protocol News - July 8, 2026

Week of: July 8, 2026

Overview

The MCP TypeScript SDK shipped a coordinated beta.2 release across all packages, adding CommonJS support alongside ESM and fixing HTTP error handling. The MCP Servers repository published a new release (2026.7.4) updating four reference server packages, while the specification repository added an AI agent contribution policy and updated documentation links.

Stories

1. MCP TypeScript SDK Ships CommonJS Support Across All Beta.2 Packages

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

The MCP TypeScript SDK released version 2.0.0-beta.2 for all packages — core, client, server, node, express, fastify, hono, codemod, and server-legacy. Each package now emits both .mjs/.d.mts and .cjs/.d.cts builds, and the exports map includes a require condition so require('@modelcontextprotocol/…') works from CommonJS consumers.

This change addresses a long-standing compatibility gap for Node.js projects still using CommonJS. The @modelcontextprotocol/server package additionally returns HTTP 400 for MissingRequiredClientCapabilityError errors produced after dispatch, aligning with the spec requirement. The codemod package includes v1-to-v2 migration fixes from continued real-world migrations.

Impact Analysis: Teams using MCP in mixed ESM/CJS environments can now adopt the SDK without module system friction, and the HTTP error fix ensures spec-compliant server behavior.

2. MCP Servers Release 2026.7.4 Updates Four Reference Servers

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

The MCP Servers repository published release v2026.7.4, updating four reference server packages: @modelcontextprotocol/server-everything, server-filesystem, server-sequential-thinking, and server-memory, all to version 2026.7.4.

These reference servers serve as canonical implementations for the MCP specification. The coordinated version bump suggests maintenance updates or spec alignment fixes across the core server set.

Impact Analysis: Developers building on MCP reference servers should update to the latest versions to stay aligned with spec changes and bug fixes.

3. MCP Specification 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 via commit #3009. The policy establishes guidelines for AI-assisted contributions to the specification.

As MCP itself is a protocol for AI-tool interaction, formalizing how AI agents contribute to the spec is a meta-level development. This signals the project's commitment to managing AI-generated contributions as the ecosystem grows.

Impact Analysis: Contributors using AI tools to submit changes to the MCP spec now have clear guidelines, reducing friction in the review process.

4. MCP Specification Updates Goose Documentation Links

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

The MCP specification repository updated documentation links for Goose, an AI agent tool, including formatting the Goose links table. This is a documentation maintenance change within the spec repo.

Goose is an open-source AI agent that uses MCP for tool integration. Keeping documentation links current helps developers using Goose with MCP find the right resources.

Impact Analysis: Developers integrating Goose with MCP should reference the updated documentation links for accurate setup guidance.

5. MCP Specification Adds Code of Conduct Appeals Channel

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

The MCP specification repository merged a pull request adding a Code of Conduct appeals channel at appeals@modelcontextprotocol.io. This establishes a formal process for addressing conduct concerns in the community.

As the MCP ecosystem grows, governance infrastructure like appeals channels becomes important for maintaining a healthy contributor community.

Impact Analysis: Community members now have a clear escalation path for Code of Conduct issues, supporting long-term project sustainability.

Source Links

• MCP TypeScript SDK - @modelcontextprotocol/server-legacy@2.0.0-beta.2
• MCP Servers - Release 2026.7.4
• MCP Specification - Add AI agent contribution policy to AGENTS.md (#3009)
• MCP Specification - docs: update Goose documentation links (#3019)
• MCP Specification - Merge pull request #2993 from tadasant/docs/coc-appeals-channel