Model Context Protocol Blog

Today we’re excited to publish an updated roadmap for the Model Context Protocol (MCP), covering the next specification release and beyond. It sets the direction for protocol work over the coming months and was developed by the Core Maintainers together with our community of maintainers and Working Groups. Explore the roadmap → Priority areas The roadmap is organized into five priority areas. Several of them pick up work that the previous roadmap listed as on the horizon, including server-initiated events, result type improvements, and agent identity, which have since matured enough to become priorities in their own right. Each area has a set of Core Maintainers responsible for it and one or more Working Groups. ...

Since our last November release MCP continued to grow at an astonishing rate. Across our Tier 1 SDKs, we’re seeing close to half-a-billion downloads a month, with both TypeScript and Python SDKs crossing the 1 billion total downloads threshold. In just a few months, the protocol continued to grow as the data and interactivity substrate for agentic workflows. Today, we’re officially pushing the release button on the next version of the MCP specification, 2026-07-28, along with the SDKs that will allow you to start building clients and servers right away. ...

Version 1.0.0 of the official Ruby SDK for the Model Context Protocol is now available. This is the first stable release of the mcp gem: the public API is now stable, and breaking changes ship only in major releases, following the Semantic Versioning policy documented in VERSIONING.md. Alongside the release, the Ruby SDK now meets every Tier 2 requirement of the SDK tiering system, as recorded in the Tier 2 assessment, and development toward Tier 1 is ongoing. ...