Source: MCP SDKs and Python SDK v2
The official MCP SDK list with tier ratings, plus the Python SDK v2 'What's new' page (FastMCP renamed MCPServer, 2026-07-28 support, legacy compatibility).
Contents
- What: the SDKs page on modelcontextprotocol.io and the Python SDK documentation’s “What’s new in v2”
- Author/publisher: Model Context Protocol project
- Date: living documents; read 2026-11-14
- Original: SDKs · Python SDK v2: What’s new · python-sdk repo
Summary
Official SDKs are tiered by completeness and maintenance. All support servers with tools/resources/prompts, clients, and local plus remote transports, but each adopts new protocol revisions on its own schedule. The Python SDK’s 2.x line implements the stateless 2026-07-28 revision while still serving 2025-era clients from the same app.
Key claims
- Tier 1 (as of 2026-11-14): TypeScript, Python, C#, Go, Rust, Ruby. Tier 2: Java. Tier 3: Swift, PHP, Kotlin.
- Python v2:
FastMCPis nowMCPServer(from mcp.server import MCPServer);@mcp.tool()on a type-hinted function, docstring as description;@mcp.resource("greeting://{name}")for URI templates. - Python v2 requires Python 3.11+;
uv run mcp dev server.pyopens the MCP Inspector;mcp run server.py --transport streamable-httpserves over HTTP. - On 2026-07-28 connections
ctx.elicit()and sampling raiseNoBackChannelError(they still work for legacy clients), reflecting the MRTR redesign. - Without sessions, any replica can answer a modern Streamable HTTP request; 2025-era clients still open sessions and need the same stickiness as v1. MRTR
request_stateuses a per-process key by default, so scaled deployments should passRequestStateSecurity(keys=[...]). - Tests:
Client(mcp)negotiates 2026-07-28 by default, so v1 tests relying on elicitation/sampling can fail;mode="legacy"keeps push behaviour. - The 3.11+ requirement and the
mcp runcommand come from the repo README; the What’s new page coversmcp dev/mcp install. - WebSocket transport removed; host/port options move to
run(); mount the ASGI app to serve under a prefix. - Client auth validates
iss, sendsapplication_type, refuses to replay credentials against a different AS, and adds an enterprise identity-assertion flow (SEP-990).