Mcpzero

mcpzero31stars

Expose, secure, and observe MCP servers — from your laptop to production clients.

1# Mcpzero

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 31
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Mcpzero?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Mcpzero need an API key?

No required environment variable is listed on this record.

What transport does Mcpzero use?

Mcpzero runs locally over stdio.

When was Mcpzero last checked?

Last checked 2026-10-28. Expose, secure, and observe MCP servers — from your laptop to production clients.

From the publisher

Documentation

your MCP servers (no auth) ──tunnel──▶ gw.mcpzero.io ──▶ aggregation gateway ──▶ Cursor / Claude / Codex
                                  │                    (auth · aggregate · audit)
                              dashboard: endpoints, API keys, call ledger

Why MCPZERO

Pillar	What it means
Zero-Config	Reads your existing `mcp.json` and multiplexes every local stdio server through one encrypted tunnel — no domains, TLS, or hosting to manage.
Zero-Trust	Every public endpoint is enforced at the edge. Clients authenticate with `Authorization: Bearer`; auth resolves in under 5ms and the protocol surface of your tools is never exposed to the internet.
Zero-Leak	The gateway forwards in-memory and persists metadata only (tool, latency, status). Request/response bodies are never stored by default — stream full audit logs to your own S3 / R2 / OSS on paid tiers.
Zero-Friction	The Semantic progressive discovery of tools reduces token usage and 'context bloat'

Architecture

Semantic aggregation

Combine many local MCP servers behind one endpoint. Each server keeps its own public path; the endpoint root becomes a meta server that routes tool calls to the correct backend.

mcpzero tunnel start --endpoint ep_abc123 --mcp-config ./mcp.json
# reads mcp.json → postgres, filesystem, puppeteer — one tunnel, many servers

See example mcp.json file

See Semantic aggregation.

Progressive discovery

AI clients discover tools on demand instead of loading every schema upfront. The meta server exposes meta_search and meta_call_tool so agents match intent to concrete tools without wasting context tokens.

See Progressive discovery.

Gateway intelligence

Beyond transport and auth, MCPZERO inspects and orchestrates MCP traffic at the edge:

Semantic WAF (Enterprise · Roadmap) — a content-aware firewall that understands JSON-RPC and tool schemas. Inspects every tools/call for malicious arguments, unsafe paths, and data-exfiltration patterns.
Tool Hijacking Defense (Enterprise · Roadmap) — scans tool arguments and returned content for injection and jailbreak payloads, neutralizing compromised tools.
Team sharing & audit — share endpoints across members, visualize traffic, and retain searchable audit logs; NDJSON export and webhook alerts on Personal+ (Team adds higher caps and team-scoped alerts).

Get started

Tunnel a local server with the CLI:

curl -fsSL https://mcpzero.io/install-cli.sh | sh`
# or: brew install mcpzero/tap/mcpzero-cli
# or: npm install -g mcpzero-cli
# or: pipx install mcpzero-cli
mcpzero version
mcpzero login
mcpzero init

The CLI source lives in cli/; see its README for building from source and the full command reference.

Repositories

Repo	What	License
`mcpzero`	This repo — docs, examples, install script, protocol spec, and the CLI	MIT
`homebrew-tap`	`brew install mcpzero/tap/mcpzero-cli`	—

Documentation

Product docs: https://mcpzero.io/docs (source of truth lives in docs/)
Tunnel wire protocol: PROTOCOL.md
Runnable examples: examples/

License

Content in this repository (docs, examples, install script) is MIT — see LICENSE.

Mcpzero

mcpzero31stars

Expose, secure, and observe MCP servers — from your laptop to production clients.

Install Run on PlugMCP

GitHub Website

Run on PlugMCP

1# Mcpzero

README.mdMCP server

Transport: stdio
Status: Local

Power your agent

Add this server

Install from the publisher. Not a PlugMCP endpoint.

Run on PlugMCP

Host a copy with our keys and logs.

No packaged release in the registry yet. Follow the repository README.

RepositoryPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

Run on PlugMCP

Host a copy with our keys and logs.

A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.

Launch

Server facts

Local

Transport: stdio
License: MIT
Last checked: 2026-10-28

Stars: 31
Tools: —
Uptime: —

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

How do I install Mcpzero?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does Mcpzero need an API key?

No required environment variable is listed on this record.

What transport does Mcpzero use?

Mcpzero runs locally over stdio.

When was Mcpzero last checked?

Last checked 2026-10-28. Expose, secure, and observe MCP servers — from your laptop to production clients.

From the publisher

Documentation

your MCP servers (no auth) ──tunnel──▶ gw.mcpzero.io ──▶ aggregation gateway ──▶ Cursor / Claude / Codex
                                  │                    (auth · aggregate · audit)
                              dashboard: endpoints, API keys, call ledger

Why MCPZERO

Pillar	What it means
Zero-Config	Reads your existing `mcp.json` and multiplexes every local stdio server through one encrypted tunnel — no domains, TLS, or hosting to manage.
Zero-Trust	Every public endpoint is enforced at the edge. Clients authenticate with `Authorization: Bearer`; auth resolves in under 5ms and the protocol surface of your tools is never exposed to the internet.
Zero-Leak	The gateway forwards in-memory and persists metadata only (tool, latency, status). Request/response bodies are never stored by default — stream full audit logs to your own S3 / R2 / OSS on paid tiers.
Zero-Friction	The Semantic progressive discovery of tools reduces token usage and 'context bloat'

Architecture

Semantic aggregation

Combine many local MCP servers behind one endpoint. Each server keeps its own public path; the endpoint root becomes a meta server that routes tool calls to the correct backend.

mcpzero tunnel start --endpoint ep_abc123 --mcp-config ./mcp.json
# reads mcp.json → postgres, filesystem, puppeteer — one tunnel, many servers

See example mcp.json file

See Semantic aggregation.

Progressive discovery

See Progressive discovery.

Gateway intelligence

Beyond transport and auth, MCPZERO inspects and orchestrates MCP traffic at the edge:

Semantic WAF (Enterprise · Roadmap) — a content-aware firewall that understands JSON-RPC and tool schemas. Inspects every tools/call for malicious arguments, unsafe paths, and data-exfiltration patterns.
Tool Hijacking Defense (Enterprise · Roadmap) — scans tool arguments and returned content for injection and jailbreak payloads, neutralizing compromised tools.
Team sharing & audit — share endpoints across members, visualize traffic, and retain searchable audit logs; NDJSON export and webhook alerts on Personal+ (Team adds higher caps and team-scoped alerts).

Get started

Tunnel a local server with the CLI:

curl -fsSL https://mcpzero.io/install-cli.sh | sh`
# or: brew install mcpzero/tap/mcpzero-cli
# or: npm install -g mcpzero-cli
# or: pipx install mcpzero-cli
mcpzero version
mcpzero login
mcpzero init

The CLI source lives in cli/; see its README for building from source and the full command reference.

Repositories

Repo	What	License
`mcpzero`	This repo — docs, examples, install script, protocol spec, and the CLI	MIT
`homebrew-tap`	`brew install mcpzero/tap/mcpzero-cli`	—

Documentation

Product docs: https://mcpzero.io/docs (source of truth lives in docs/)
Tunnel wire protocol: PROTOCOL.md
Runnable examples: examples/

License

Content in this repository (docs, examples, install script) is MIT — see LICENSE.