Zero overhead.
20 of 21 chaos attacks survived.

zeromcp vs ModelContextProtocol — side by side.

Dependencies

0 ZeroMCP

vs.

41 Official SDK

Throughput

4,421 req/s

vs.

2,517 req/s

Memory

314 MB

vs.

78 MB

This is a hello world

A builder pattern, anonymous types for schema, and transport setup. 8 lines of ceremony before your tool does anything.

ModelContextProtocol 8 lines

var server = new McpServerBuilder()
    .WithName("test")
    .WithTool("hello", "Say hello",
        new { name = new { type = "string" } },
        async (args) =>
            $"Hello, {args["name"]}!")
    .Build();
await server.RunStdioAsync();

This is the whole server

No builder pattern. No anonymous types. No McpServerBuilder.
Register a lambda and serve.

ZeroMCP 8 lines

var server = new Server();
server.Tool("hello", new Tool {
    Description = "Say hello",
    Input = new Input()
        .Required("name", "string"),
    Execute = (args, ctx) =>
        $"Hello, {args["name"]}!"
});
await server.ServeStdioAsync();

HTTP Performance — Head to Head

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

ZeroMCP (ASP.NET) 4,421 1.47% 314 MB 1.8x

Official SDK 2,517 0.05% 78 MB

ZeroMCP on ASP.NET uses more CPU (1.47% vs 0.05%) due to the .NET runtime. But it serves 1.8x more requests.

ZeroMCP HTTP Frameworks

ZeroMCP embedded natively in C# frameworks. No proxy. No subprocess. 30-second sustained load.

ASP.NET 3,468 1.03ms — 226 MB

What's different

SandboxEnforced. Not advisory.
CredentialsPer-directory. Not Environment.GetEnvironmentVariable.
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.

Attribute-based tools

ZeroMCP uses a simplified registration API. If you prefer attribute-based tool definitions with typed parameters, use the official SDK.

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).

Register a function. It's an MCP tool.

Get started See all benchmarks →

Other languages

Node.js Python Go Rust Java Kotlin Swift C# Ruby PHP

Zero overhead.20 of 21 chaos attacks survived.