← News

Agents & MCPSources: blog.modelcontextprotocol.io · 30 Oct 2026

Ruby SDK for MCP reaches Tier 1 status

The Model Context Protocol project has promoted its official Ruby SDK to the top tier, citing full spec coverage, a perfect conformance record, and fast issue handling.

In plain words

The Model Context Protocol (MCP) is a standard that lets AI applications talk to external tools and data. Its maintainers rank official software development kits in three tiers, and the Ruby kit has now reached the top one. That means Ruby developers building MCP servers or clients get complete feature support and quick fixes, according to the announcement.

What was announced

The MCP blog says Tier 1 status is reserved for SDKs with the highest feature support, responsiveness to bugs and security issues, and alignment with ecosystem priorities. Ruby now sits alongside the TypeScript, Python, C#, Go, and Rust SDKs. The maintainers report a 100% pass rate on scored server and client conformance scenarios for both the 2025-11-25 and 2026-07-28 spec versions, issue triage within two business days, and critical bug fixes within seven days. Version 1.2.0 of the mcp gem added full support for the 2026-07-28 spec, including a stateless lifecycle, multi round-trip requests, and cache hints, while the server can serve both old and new lifecycle styles at once.

The path was quick: the SDK was rated Tier 3 in March 2026, reached Tier 2 in July, and was confirmed at Tier 1 in September. The blog credits better documentation, moved to a dedicated site with version 1.3.0, and a perfect triage record with no P0 issues. Upgraders should note that several 1.x releases reject input that earlier versions accepted, so the maintainers advise reading the changelog first. The team has also committed to supporting the next spec, targeted for late March 2027, by its release date.

What it does not show

  • All conformance and triage figures come from the MCP project's own assessment and blog post; no independent verification beyond the named reviewers is reported.
  • The legacy SSE transport is intentionally not implemented, so coverage of that transport is absent.
  • The source does not state whether the two undocumented features beyond the SSE transport affect conformance scoring.

For security and IT teams

Status
Teams running Ruby MCP servers on 1.x can upgrade to serve 2026-07-28 clients alongside existing ones, but should review the changelog first because some releases reject previously accepted input.

Sources

Source-support review completed 15 Nov 2026. This story was drafted with AI assistance and checked against retained source passages. Automated checking is not independent verification.

Updates and corrections

No corrections so far.

First published 15 Nov 2026

New to the subject? AI from the Ground Up starts from the beginning.