ZeroMCP v0.1.0 is here. v0.2.0 coming soon.
Node.js

91 packages installed
for a hello world.

zeromcp vs @modelcontextprotocol/sdk — side by side.

Dependencies
0 ZeroMCP
vs.
91 Official SDK
Throughput
4,539 req/s
vs.
2,610 req/s
Memory
26 MB
vs.
174 MB

This is a hello world

3 imports. A server class. A Zod schema. A transport. 12 lines before your tool does anything.

@modelcontextprotocol/sdk 12 lines
import { McpServer } from "@modelcontextprotocol/sdk/server/mcp.js";
import { StdioServerTransport } from "@modelcontextprotocol/sdk/server/stdio.js";
import { z } from "zod";

const server = new McpServer({ name: "test", version: "1.0.0" });

server.tool("hello", { name: z.string() }, async ({ name }) => ({
  content: [{ type: "text", text: `Hello, ${name}!` }],
}));

const transport = new StdioServerTransport();
await server.connect(transport);

This is the whole server

No server class. No schema library. No transport setup.
Drop it in a folder and run zeromcp serve.

ZeroMCP 9 lines
// tools/hello.js
export default {
  description: "Say hello to someone",
  input: {
    name: 'string',
  },
  execute: async ({ name }) => {
    return `Hello, ${name}!`;
  },
};

HTTP Performance — Head to Head

Same hello tool. Same methodology. 5-minute sustained load in Docker. bare http for ZeroMCP, stdio proxy for the official SDK.

req/s CPU Memory Ratio
ZeroMCP (bare http) 4,539 0.02% 26 MB 1.7x
Official SDK 2,610 0.02% 174 MB

ZeroMCP HTTP Frameworks

ZeroMCP embedded natively in Node.js frameworks. No proxy. No subprocess. 300-second sustained load.

req/s p99 CPU load Memory
bare-http 8,699 0.26ms 27% 78 MB
Fastify 8,282 0.32ms 34% 125 MB
Hono 7,309 0.49ms 39% 157 MB
Express 6,814 0.60ms 48% 120 MB
bare-http Fastify Hono Express

What's different

  • SandboxEnforced. Not advisory.
  • CredentialsPer-directory. Not process.env.
  • ProcessesOne. Not N.
  • Hot reloadBuilt-in. Not restart.
  • ComposabilityConnect remote MCP servers. Official SDK can't.
  • TransportStreamable HTTP by default. Stdio too.

When to use the official SDK

ZeroMCP makes trade-offs. Here's what you give up.

Resources and prompts

ZeroMCP implements tools only. If you need MCP resources, prompts, or sampling, use the official SDK.

Zod schemas

ZeroMCP uses a simplified input format. If your team standardizes on Zod for runtime type checking, the official SDK uses it natively.

Spec parity

The official SDK tracks every spec change immediately. ZeroMCP prioritizes stability over spec completeness.

Enterprise support

The official SDK is maintained by the MCP specification team at Anthropic. ZeroMCP is maintained by the antidrift team (Reloop Labs, LLC).

Drop a .js file. It's an MCP tool.