Our take
Activeregular commits and releases- Activity
- 81
- Community
- 91
- Issues
- 63
- Pull requests
- 72
+174 stars in the last 30 days
- Releases more often than 93% of the projects we track
- More contributors than 78% of the projects we track
This is an actively maintained, broadly contributed SDK for TypeScript teams building both sides of MCP, with a clear separation between its core packages and optional framework adapters.
Good fit if
- You are building an MCP client or server in TypeScript and want the official SDK for the protocol.
- You need stdio or Streamable HTTP transports, or an adapter for one of the listed web frameworks.
- You can work with a project receiving regular commits and releases, and review its stated licensing terms for your use.
Look elsewhere if
- You need an SDK for a language other than TypeScript.
- Your runtime is incompatible with the SDK's declared Node.js requirement and you cannot use its Bun or Deno support.
- You need a license arrangement other than the project's stated Apache 2.0 license for new contributions and MIT for existing code.
All health signals
| Last commit | 2026-10-23 (today) |
|---|---|
| Commits, last 90 days | 88 |
| Releases, last 12 months | 100+ (latest v2.4.0, 2026-10-23) |
| Contributors | 100+ (top contributor: 23% of commits) |
| Issues closed, last 90 days | 21+ (typically closed in 6 days) |
| Pull requests merged, last 90 days | 47 (typically merged in 0 days) |
| Project age | 2 years |
Checked on 2026-10-24 with the GitHub API.
Project history
Daily GitHub snapshots since Oct 7, 2026. History covers stars and forks; health signals are not tracked historically.
Stars
13,774Forks
2,394Change since Nov 16, 2026: +4 stars·+3 forks
Overview
The official TypeScript SDK for the Model Context Protocol (MCP) provides libraries for building MCP servers and clients. MCP standardizes how applications provide context to LLMs, separating context delivery from the LLM interaction itself.
The SDK runs on Node.js, Bun, and Deno. It is aimed at TypeScript developers integrating MCP into applications, whether they need to expose tools, resources, and prompts or connect to an MCP server. Optional adapters support Node.js HTTP, Express, Fastify, and Hono.
Key Features
- Build MCP servers that expose tools, resources, and prompts.
- Build clients with transport and OAuth helpers.
- Communicate over stdio or Streamable HTTP.
- Use Standard Schema-compatible libraries, including Zod v4, Valibot, and ArkType, for tool and prompt schemas.
- Add optional integrations for Node.js HTTP, Express, Fastify, and Hono.
- Follow tutorials and runnable client/server examples in the repository.
Use Cases
- TypeScript developers can expose application capabilities as MCP tools for compatible LLM applications.
- Teams can build MCP clients that discover and call tools on servers, including servers they develop themselves.
- Server authors can expose resources and prompts alongside tools through a common protocol.
- Node.js web teams using Express, Fastify, or Hono can connect MCP to an existing framework with the corresponding adapter.
What you need
Detected in the repository
- Node.js >=20 (from package.json)
- A test suite and automated checks on GitHub Actions
Getting Started
Install the server package with npm install @modelcontextprotocol/server, or the client package with npm install @modelcontextprotocol/client. See the README and v2 documentation for tutorials and setup details.
License in Plain Words
No standard license was detected. Without a license, the default copyright rules apply: you may read the code, but not reuse it. Check the repository or ask the authors.
Alternatives
- java-sdk: Provides MCP client and server libraries for Java rather than TypeScript, with synchronous and asynchronous communication.
- mcp-framework: Provides a Rust and Tokio-based framework for MCP clients, servers, and agents rather than a TypeScript SDK.
| Project | Language | License | Stars | Status |
|---|---|---|---|---|
| typescript-sdk | TypeScript | – | 13.6k | Active |
| java-sdk | Java | MIT | 3.7k | Active |
| mcp-framework | Rust | MIT | 25 | Quiet |
Considerations
- The repository's current main branch is v2 and implements the 2026-07-28 MCP specification. Teams on v1 should consult the migration guide; v1 source and fixes remain on the
v1.xbranch, with bug fixes and security updates promised for at least six months after the v2 release. - The package metadata declares Node.js 20 or newer. The README also lists Bun and Deno support, so check the relevant package and runtime documentation before choosing a deployment target.
- The repository is actively maintained, with regular commits and releases, and has contributions from at least 100 people. Its contributor share is not concentrated in one person. Issue closure is ongoing, but the measured median time to close is six days.
- The README states that new contributions are under Apache License 2.0 while existing code is under MIT. Review the
LICENSEfile and package terms for the components you plan to use.
Found this useful?
Share it with someone who would like typescript-sdk.