// the take
The official TypeScript SDK for the Model Context Protocol, covering both server and client implementations. It's the reference implementation other language SDKs and MCP tooling get compared against, and it's the obvious starting point for anyone building an MCP server or client in TypeScript/JavaScript.
Runs on Node, Bun, and Deno rather than assuming one runtime. Splits server and client into separate packages instead of one fat SDK, and keeps framework glue (Express, Fastify, Hono, raw Node HTTP) as thin optional adapters rather than baking framework assumptions into core. Schema validation goes through Standard Schema, so you're not locked into Zod — Valibot or ArkType work too. Backed directly by the people writing the spec, so it tracks protocol changes immediately rather than lagging behind.
v2 is a breaking rewrite of the package names and API surface (@modelcontextprotocol/sdk becomes separate server/client packages) — anyone upgrading from v1 has real migration work, and v1 only gets security fixes for six months post-release. The protocol itself is still young and versioned by date (2026-07-28 spec), so expect continued breaking changes as MCP matures, not API stability in the traditional semver sense. Auth (OAuth flows, Host header validation middleware) is clearly an area still being hardened — worth scrutinizing closely if you're exposing a server publicly rather than running it locally over stdio. Session state and scaling across multiple server instances is called out as its own doc topic, which usually means it's a rough edge in practice, not a solved problem.
We read the README, the directory tree and a key source file in November 2026. Nobody pays to be listed. How we judge →