Skip to main content
This page defines the three SDK tiers, what each requires, how an SDK moves between them, and the issue labels SDK repositories must use. The tiers were adopted by SEP-1730, a Specification Enhancement Proposal (SEP), and are changed by a Process SEP. The SDK Working Group operates them, and each SDK’s current tier is shown on the SDKs page.

Tier requirements

Tier 1 SDKs are fully supported and implement every non-experimental feature, including optional capabilities such as sampling and elicitation. SDKs in Tier 2 are actively maintained and working toward full specification support, and those in Tier 3 are experimental, partially implemented, or specialized. Experimental features and protocol extensions (such as Tasks and MCP Apps) are not required for any tier. Issue Triage means labeling an issue and determining whether it is valid, not resolving it. Critical Bug means a P0 issue as defined under Priority labels. Stable Release means a published version explicitly marked as production-ready, for example version 1.0.0 or higher without a pre-release identifier such as -alpha, -beta, or -rc. Clear Versioning means following idiomatic versioning patterns with a documented breaking-change policy. Roadmap means a published set of concrete steps and work items tracking implementation of the required specification components (non-experimental features and optional capabilities, as scoped under Conformance testing).

Conformance testing

Conformance is measured with the conformance test suite. Each official SDK runs the suite against its default branch and publishes the results. The pass rates in the matrix are calculated against applicable required tests only:
  • Tests for the specification version the SDK targets
  • Excluding tests marked as pending or skipped
  • Excluding tests for experimental features
  • Excluding legacy backward-compatibility tests (unless the SDK claims legacy support)
  • Excluding tests labeled disputed in the conformance repository, until the dispute is resolved
Sustained test failures are handled under Tier relegation.

Tier advancement

To request a higher tier, an SDK’s maintainers:
  1. Self-assess the SDK against the tier requirements.
  2. Open an issue in the modelcontextprotocol/modelcontextprotocol repository with the supporting evidence.
  3. Pass the conformance threshold for the requested tier on the latest stable release.
  4. Obtain approval from the SDK Working Group.
The SDK Working Group makes the final tier assignment and records the decision and rationale as set out in its charter.

Tier relegation

An SDK may be moved to a lower tier if existing conformance tests on its latest stable release fail continuously for 4 weeks:
  • Tier 1 to Tier 2: any conformance test fails.
  • Tier 2 to Tier 3: more than 20% of conformance tests fail.
An SDK may also be relegated if issues remain unaddressed for two months. The SDK Working Group may likewise relegate a Tier 1 SDK that consistently fails to surface specification deprecations as required by Tier 1 SDK Obligations. The group decides each relegation and records it with its rationale.

Issue triage labels

SDK repositories must use the labels below. Two tier metrics are computed from them: triage response time (issue creation to first label) and critical bug resolution time (P0 label to close).

Type (pick one)

Repositories using GitHub’s native issue types satisfy this requirement without type labels.

Status (pick one)

Use these exact label names in every repository.

Priority (only if actionable)

A P0 issue is either:
  • A security vulnerability with a CVSS score of 7.0 or higher (High or Critical severity)
  • A core functionality failure that prevents basic MCP operations: connection establishment, message exchange, or use of the core primitives (tools, resources, prompts)