MCP Protocol News - August 1, 2026

Week of: August 1, 2026

Overview

GitHub shipped MCP Server 1.8.0 with tool response filtering to cut context usage, while the MCP specification repo finalized its 2026-07-28 release cut, updating the versioning page and release post. Spec documentation now treats Final SEP pages as historical records, with an error code corrected in SEP-2663.

Stories

1. GitHub MCP Server 1.8.0 adds response filtering and batched project updates

Source: GitHub MCP Server Link: https://github.com/github/github-mcp-server/releases/tag/v1.8.0

GitHub released MCP Server v1.8.0, headlined by a new fields parameter on selected tools that lets models request only the fields they need, shrinking tool response size and optimizing context usage. The release also adds batched update_project_items writes via GraphQL, upgrades the go-sdk dependency to v1.7.0, and picks up SearchType support in go-github.

Tool responses are a major source of context bloat in MCP workflows, and letting models declare which fields they need is a server-side fix that requires no client changes. Batched GraphQL writes likewise reduce round trips for agents doing project-management operations at scale.

Impact Analysis: GitHub MCP server operators get a drop-in upgrade that trims token usage and cuts round trips for bulk project updates.

2. MCP specification names 2026-07-28 as current protocol version

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

The MCP specification repo updated its versioning page to name 2026-07-28 as the current protocol version, replacing the stale 2025-11-25 label (fixes #3169). Supporting release-cut commits stamped the version into the dated docs tree via CI and dated 13 remaining draft-tier links in the promoted 2026-07-28 spec snapshot so the release is self-consistent.

A stale "current version" label is a real hazard for implementers pinning SDKs and clients to a protocol snapshot. The coordinated docs and CI fixes indicate the 2026-07-28 release cut was treated as a proper publish, not just a docs edit.

Impact Analysis: Builders can rely on 2026-07-28 as the documented current protocol baseline, with tooling in place to keep future cuts accurate.

3. Final SEP pages now marked as historical records in MCP spec

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

Final SEP pages in the MCP spec repo are now marked as historical records, with the generator injecting a notice on every page pointing readers to the current specification. The change follows drift in SEP-2322, which still documents tasks/result and tasks/input_response even though SEP-2663 removed those features; SEP guidelines now state Final SEPs are not updated after finalization.

As the protocol evolves, finalized proposals can contradict the normative spec, which misleads builders who treat SEP pages as reference documentation. This change makes the current specification the explicit source of truth and frames SEPs as design history.

Impact Analysis: Treat SEP pages as point-in-time design records — the live specification is now the sole authoritative reference.

4. Error code corrected in SEP-2663

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

A merged fix corrects the MISSING_REQUIRED_CLIENT_CAPABILITY error code as documented in SEP-2663. The correction comes via PR #3116, landing in the proposal document implementers reference for the updated protocol.

SEP-2663 is the proposal that removed the tasks/ interfaces from the protocol, so error-code accuracy in that document matters for clients and servers coordinating on capability negotiation during the migration.

Impact Analysis: Implementers following SEP-2663 should use the corrected MISSING_REQUIRED_CLIENT_CAPABILITY code in capability checks.

5. Runlayer and Stacklok quotes added to MCP 2026-07-28 release post

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

The spec repo added quotes from Runlayer and Stacklok to the 2026-07-28 release post. The change was merged via PR #3162 alongside the release's documentation updates.

Third-party quotes in the release post signal real-world usage of the latest protocol snapshot; the release post itself is the source for what the companies said.

Impact Analysis: See source for the quoted companies' specific remarks on the 2026-07-28 protocol baseline.

Source Links

• GitHub MCP Server - GitHub MCP Server 1.8.0 adds response filtering and batched project updates
• MCP Specification - MCP specification names 2026-07-28 as current protocol version
• MCP Specification - Final SEP pages now marked as historical records in MCP spec
• MCP Specification - Error code corrected in SEP-2663
• MCP Specification - Runlayer and Stacklok quotes added to MCP 2026-07-28 release post