mcp-framework Crosses 3 Million npm Downloads

mcp-framework, the first TypeScript framework for building MCP servers, has surpassed 3 million npm downloads — cementing its position as the most widely adopted MCP development tool.

title: "mcp-framework Crosses 3 Million npm Downloads" description: "mcp-framework, the first TypeScript framework for building MCP servers, has surpassed 3 million npm downloads — cementing its position as the most widely adopted MCP development tool." order: 5 keywords:

• "mcp-framework downloads"
• "mcp-framework adoption"
• "MCP framework popularity"
• "mcp-framework npm"
• "MCP server framework growth" date: "2026-04-01" author: "MCP Academy"

From Zero to 3.3 Million

On December 8, 2024, the first version of mcp-framework was published to npm. It was a small TypeScript framework with a simple premise: building MCP servers should be fast, structured, and convention-driven. Fifteen months later, the download counter has passed 3.3 million.

That number represents real installations by real developers. Every npm install mcp-framework is someone building an MCP server — connecting an LLM to a database, an API, a file system, or an internal tool. The growth has been organic, driven almost entirely by developers telling other developers that this is the fastest way to ship an MCP server.

The Milestone Timeline

The path from first publish to 3 million downloads was not a straight line. It accelerated as the MCP ecosystem matured and more developers entered the space.

The pattern is clear: each million came faster than the last. The first million took nine months. The third took fewer than three. That acceleration reflects both the growth of the MCP ecosystem and the compounding effect of a framework that developers recommend to each other.

By the Numbers

The raw statistics tell the story of a project that has found its audience and continues to grow.

Nine versions per month means the framework is actively maintained and responsive to community needs. Developers can trust that bugs get fixed, features ship, and compatibility with the evolving MCP specification stays current.

Why Developers Choose mcp-framework

Download numbers are a trailing indicator. The leading indicator is why developers keep choosing this framework over alternatives. Based on community feedback, GitHub discussions, and adoption patterns, the reasons are consistent.

It Was First and It Got the Abstractions Right

mcp-framework was the first TypeScript framework purpose-built for MCP servers. Being first matters, but only if you also get the design right. The convention-over-configuration approach — auto-discovery of tools, resources, and prompts from the file system — turned out to be exactly what developers wanted. It reduced boilerplate without hiding the protocol.

The CLI Makes Starting Instant

Going from nothing to a working MCP server in under two minutes is a real productivity advantage. The CLI scaffolds projects, generates typed tool classes, and sets up the build pipeline. Developers do not have to make architectural decisions before writing their first line of business logic.

Class-Based Architecture Scales

A server with three tools can live in a single file. A server with thirty cannot. The class-based architecture — one file per tool, each extending a base class with Zod schema validation — gives teams a pattern that stays organized as servers grow. This matters especially in production, where servers tend to accumulate tools over time.

It Builds on the Official SDK

mcp-framework is not a fork or a reimplementation. It uses the official MCP TypeScript SDK under the hood. This means developers are not locked into a proprietary abstraction. Everything they learn about the protocol applies directly. If they ever need to drop down to the raw SDK for a specific use case, they can.

What the Community Is Saying

The developers building with mcp-framework have been the strongest advocates for its adoption.

Common sentiments from the community include:

• "I had a working MCP server in five minutes." The CLI and convention-based setup eliminate the blank-page problem. Developers scaffold a project, generate a tool, and immediately focus on the logic that matters.
• "It is the only framework that keeps up with the spec." With 145 versions shipped, the framework tracks MCP specification changes closely. Developers do not have to worry about falling behind.
• "Our team standardized on it for all our MCP servers." The consistent architecture makes it easier for teams to onboard new members and maintain servers across projects.
• "I tried building from scratch first, then switched." Many developers start with the raw SDK, hit the boilerplate wall around ten tools, and migrate to mcp-framework for the organizational benefits.

These are not isolated opinions. The download growth curve confirms that developers who try the framework keep using it and bring it to new projects.

What 3 Million Downloads Means for the Ecosystem

mcp-framework's adoption is also a signal about the MCP ecosystem itself. Three million downloads means there are a lot of MCP servers being built. The protocol has moved well past the early-adopter phase and into mainstream developer tooling.

This has a compounding effect. More servers means more tools available to LLMs. More tools means more value from MCP-compatible clients. More value means more developers building servers. mcp-framework sits at the center of this loop, making it easier for each new developer to contribute to the ecosystem.

What Is Next

Crossing 3 million downloads is a milestone, not a finish line. The framework continues to evolve based on how developers actually use it in production.

Active development priorities include:

• Expanded transport support — Streamable HTTP and SSE transports for servers that need to run as standalone services, not just stdio processes
• Plugin and middleware system — Reusable patterns for authentication, logging, rate limiting, and other cross-cutting concerns
• Testing utilities — Built-in helpers that make writing unit and integration tests for tools as straightforward as writing the tools themselves
• Starter templates — Pre-built project templates for common server types like database connectors, API wrappers, and file system tools
• Performance optimizations — Faster auto-discovery, leaner runtime overhead, and better support for servers with large numbers of tools

The goal remains the same as day one: make building MCP servers fast, structured, and reliable. The scale has changed — from a handful of early adopters to hundreds of thousands of monthly users — but the mission has not.

Get Started

If you have not tried mcp-framework yet, the fastest path is still one command:

npx mcp-framework create my-server
cd my-server
npm install
npm run build
npm start

You will have a working MCP server in under two minutes. From there, add tools, resources, and prompts as your use case demands. The framework handles the wiring.

Check the npm page for the latest version, and follow the project on GitHub for releases, discussions, and roadmap updates.