GitHub MCP Server supports the next MCP specification

**GitHub** said its **GitHub MCP Server** supports the next **MCP** specification ahead of the official release. The **MCP** protocol is set to go **stateless** on **28th July 2026**, according to the **GitHub Changelog**. That timing puts GitHub’s server on the upcoming protocol shape before the broader cutover date.

The change centers on a new **stateless** core for **MCP**. In practice, that means session and connection state stop being assumed as part of the protocol’s default model. **GitHub’s MCP Server** is already aligned with that model, so clients and tools talking to GitHub through MCP can target the next-spec behavior instead of waiting for the formal release window.

For engineers and builders wiring agents, IDEs, or automation into GitHub via **MCP**, early support reduces the risk of a hard break on **28th July 2026**. You can exercise the **stateless** path against a production GitHub surface now, surface compatibility gaps in your own clients, and avoid last-minute rewrites when the protocol default shifts.

In market terms, **MCP** is becoming a shared integration surface across AI tooling. GitHub shipping server support for the next spec early is a signal that major platform hosts are treating the **stateless** transition as a hard calendar event, not a soft recommendation. Anyone building multi-host MCP stacks will need to track which servers land the new core before that date and which still assume the older stateful model.

What to watch next: whether your MCP clients and middleware already work cleanly against the **stateless** core on **GitHub MCP Server**, and how you plan the cutover before **28th July 2026** so production agent workflows do not depend on pre-spec session behavior after the protocol change.