Skip to content
PluginStats

@modelcontextprotocol/node weekly downloads statistics

By modelcontextprotocol (8 listings) · npm · MCP servers

Model Context Protocol implementation for TypeScript - Node.js middleware

View on npm Stale · Oct 18, 2026

@modelcontextprotocol/node has 2,059,121 recorded weekly downloads on npm, an increase of 26.3% over the past 30 days, ranking #163 of 2,391 tracked listings.

Weekly downloads
2,059,121
Official API · Oct 18, 2026
7-day growth
-37.2%
-1.2M weekly downloads
30-day growth
+26.3%
+428.3K weekly downloads
90-day growth
+8047%
+2M weekly downloads
Rank
#163
Among tracked npm listings

About @modelcontextprotocol/node

@modelcontextprotocol/node

Node.js adapters for the MCP TypeScript server SDK.

This package is a thin Node.js integration layer for @modelcontextprotocol/server. It provides a Streamable HTTP transport that works with Node’s IncomingMessage / ServerResponse.

For web‑standard runtimes (Cloudflare Workers, Deno, Bun, etc.), use WebStandardStreamableHTTPServerTransport from @modelcontextprotocol/server directly.

Install

npm install @modelcontextprotocol/server @modelcontextprotocol/node

Exports

  • NodeStreamableHTTPServerTransport
  • StreamableHTTPServerTransportOptions (type alias for WebStandardStreamableHTTPServerTransportOptions)
  • toNodeHandler(handler, opts?) — adapt a web-standard { fetch } MCP handler to a Node (req, res, parsedBody?) handler
  • hostHeaderValidation(allowedHostnames) / localhostHostValidation() — Host header guards for hand-wired node:http servers
  • originValidation(allowedOriginHostnames) / localhostOriginValidation() — Origin header guards for hand-wired node:http servers
  • ToNodeHandlerOptions, FetchLikeMcpHandler, NodeMcpRequestHandler (types for toNodeHandler)
  • toWebRequest(req, parsedBody?, opts?) — the Node IncomingMessage → web-standard Request conversion toNodeHandler performs internally, exported on its own (for example to feed isLegacyRequest() from a hand-wired (req, res) handler)
  • ToWebRequestOptions (options type for toWebRequest)
  • NodeIncomingMessageLike, NodeServerResponseLike (structural Node request/response shapes)

Usage

Express + Streamable HTTP
import { createMcpExpressApp } from '@modelcontextprotocol/express';
import { NodeStreamableHTTPServerTransport } from '@modelcontextprotocol/node';
import { McpServer } from '@modelcontextprotocol/server';

const app = createMcpExpressApp();

app.post('/mcp', async (req, res) => {
    // Stateless example: create a server and a transport per request.
    const server = new McpServer({ name: 'my-server', version: '1.0.0' });
    const transport = new NodeStreamableHTTPServerTransport({ sessionIdGenerator: undefined });
    await server.connect(transport);

    // If you use Express JSON parsing, pass the pre-parsed body to avoid re-reading the stream.
    await transport.handleRequest(req, res, req.body);
});
Node.js http server

Plain node:http has no middleware chain, so bind loopback explicitly and compose the Host/Origin guards in front of the transport — matching the defaults the framework app factories (createMcpExpressApp, createMcpHonoApp, createMcpFastifyApp) apply for you. The guards answer rejected requests with 403 themselves and return false, so the handler must not touch the request further.

import { createServer } from 'node:http';
import { localhostHostValidation, localhostOriginValidation, NodeStreamableHTTPServerTransport } from '@modelcontextprotocol/node';
import { McpServer } from '@modelcontextprotocol/server';

const validateHost = localhostHostValidation();
const validateOrigin = localhostOriginValidation();

createServer(async (req, res) => {
    if (!validateHost(req, res) || !validateOrigin(req, res)) return;
    const server = new McpServer({ name: 'my-server', version: '1.0.0' });
    const transport = new NodeStreamableHTTPServerTransport({ sessionIdGenerator: undefined });
    await server.connect(transport);
    await transport.handleRequest(req, res);
}).listen(3000, '127.0.0.1');

Description from the npm listing.

  • modelcontextprotocol
  • mcp
  • node.js
  • middleware

README badge

Show your rank in a README or on your website. The badge updates automatically.

Charts

Images: 30d · 1y · all time · 1600×900 dark

Adoption over time

@modelcontextprotocol/node weekly downloads on npm, last 90 days: 2,059,121 weekly downloads as of Oct 18, 2026, +8047% over 90 days.@modelcontextprotocol/nodeWeekly downloads on npm · Last 90 days2,059,121downloads / week+8047% over 90 days0500K1M1.5M2M2.5M3M3.5MJul 20Aug 4Aug 19Sep 3Sep 18Oct 3Oct 18downloads / weekobservedarchived (Internet Archive)no observationsJul 23, 2026 – Oct 18, 2026 · 88 observations · Updated Oc…pluginstats.com
@modelcontextprotocol/node weekly downloads on npm, last 90 days: 2,059,121 weekly downloads as of Oct 18, 2026, +8047% over 90 days.

7/30/90-day growth

@modelcontextprotocol/node weekly downloads growth on npm: -37.2% over 7 days, +26.3% over 30 days, +8047% over 90 days.@modelcontextprotocol/nodeWeekly downloads growth on npm2,059,121downloads / week now7-day growth-1,218,841 weekly downlo…-37.2%30-day growth+428,283 weekly downloads+26.3%90-day growth+2,033,846 weekly downlo…+8047%Growth vs. nearest observation to each baseline date · Updated Oct 18, 2026pluginstats.com
@modelcontextprotocol/node weekly downloads growth on npm: -37.2% over 7 days, +26.3% over 30 days, +8047% over 90 days.

Ranking history

@modelcontextprotocol/node npm ranking history: currently #163 (by weekly downloads).@modelcontextprotocol/nodenpm ranking · by weekly downloads · Last 90 days#163current rank#40#60#80#100#120#140#160#180Jul 23Aug 7Aug 22Sep 6Sep 21Oct 6Oct 21rankOct 17, 2026 – Oct 21, 2026 · 5 observations · Updated Oct 18, 2026pluginstats.com
@modelcontextprotocol/node npm ranking history: currently #163 (by weekly downloads).

Listing placement

All npm2,389 listings · 120 pages · 1,195 shown · page 9, #3 (overall #163)
All npm: every listing in weekly downloads order

Listing placement

MCP servers300 listings · 15 pages · page 1, #8 (overall #8)
MCP servers: every listing in weekly downloads order

Filled points are observed values; hollow points come from Internet Archive snapshots of the listing page. Dashed segments span periods with no observations — values between points are not interpolated.

Each band is one page of 20. Weekly downloads on a linear scale. Placement is projected from weekly downloads, so it can differ from the marketplace's own sort order. Hover a dot to see the listing.

Recent observations

Full history (544)
Recent weekly downloads observations for @modelcontextprotocol/node
Date (UTC)Weekly downloadsChange vs. previous
2,059,121+451.6K
1,607,550-383.7K
1,991,291+66.4K
1,924,910-712.9K
2,637,848-742.3K
3,380,1000
3,380,100+102.1K
3,277,962+92.7K
3,185,280+92.1K
3,093,203+129.8K
2,963,370+257.8K
2,705,555+309.9K
2,395,675-447.5K
2,843,144—

Data source

Weekly downloads (trailing 7 complete days) come from the official npm downloads API. Downloads include CI and mirrors and are not equivalent to installs or users. npm publishes no ratings.

Listing: https://www.npmjs.com/package/@modelcontextprotocol/node. First seen Oct 16, 2026; last successful collection Oct 21, 2026. See the methodology.