SDKs

Official SDKs for building with the Model Context Protocol.

Adapted from SDKs. Tier details: SDK Tiering System.

Source: modelcontextprotocol/docs (hero-dark.svg).

Executive summary

Prefer Tier 1 SDKs (TypeScript, Python, C#, Go) for production. All official SDKs aim to support servers, clients, local and remote transports, and typed protocol compliance — but tiers differ in completeness and maintenance commitment.

Available SDKs

SDK	Repository	Tier
TypeScript	typescript-sdk	Tier 1
Python	python-sdk	Tier 1
C#	csharp-sdk	Tier 1
Go	go-sdk	Tier 1
Java	java-sdk	Tier 2
Rust	rust-sdk	Tier 2
Swift	swift-sdk	Tier 3
Ruby	ruby-sdk	Tier 3
PHP	php-sdk	Tier 3
Kotlin	kotlin-sdk	Tier 3

What every SDK should support

• Creating servers that expose tools, resources and prompts
• Building clients that connect to any compliant server
• Local (stdio) and remote (Streamable HTTP) transports
• Protocol compliance with type safety

Visit the SDK docs for installation, idioms and examples for your language.

Getting started paths

• Build an MCP server
• Build an MCP client
• Example servers

Key takeaways

• Tier 1 SDKs are the default enterprise choice.
• Do not reimplement the protocol unless you are contributing to an SDK.
• Track tier and protocol version in your architecture decision record.

What to do next

Pick a language SDK and follow Build an MCP server.