MM

mcpzero/mcpzero

开发工具

本页由 AI 翻译,技术细节请以原文为准。 查看原文

31 stars 0 forks 质量 67 趋势 15MIT

从笔记本电脑到生产客户端,公开、保护并监控MCP服务器。

概览

几分钟内发布、聚合、保护并共享本地MCP服务器。 MCPZERO 是模型上下文协议(Model Context Protocol)的代表。它发布、聚合并保护本地 MCP 服务器,支持一个零信任网关 URL,使代理能够按需发现工具,而无需事先加载所有模式。 将多个本地MCP服务器合并到一个端点后。每台服务器保持自己的公共路径;端点根节点成为将工具调用路由到正确后端的路径。 AI客户端按需发现工具,而不是事先加载所有模式。元服务器暴露meta_search和meta_call_tool,使代理能够将意图与具体工具匹配,而无需浪费上下文令牌。 除了传输和认证外,MCPZERO还在边缘检查并协调MCP流量: - (Enterprise ·路线图)——一个内容感知型防火墙,能够理解 JSON-RPC 和工具模式。检查所有工具/调用,以识别恶意参数、不安全路径和数据外泄模式。

概述(AI 翻译)

MCPZERO

几分钟内发布、聚合、保护并共享本地MCP服务器。

网站 · 文档 · 仪表盘

MCPZERO 是一个安全的 MCP 聚合网关 模型上下文协议。它发布, 聚合并保护本地MCP服务器,支持一个零信任网关URL,因此 代理可以按需发现工具,而不是一开始就加载所有模式。

为什么是MCPZERO

柱子 它的含义
零配置 读取你现有的mcp.json,并通过一个加密隧道复用所有本地标准服务器——无需管理域名、TLS或托管。
零信任 每个公共端点都被边缘强制执行。客户端通过Authorization: Bearer进行认证;认证在5毫秒内完成,且你的工具协议表面永远不会暴露在互联网上。
零泄漏 网关转发内存内,仅保留元数据(工具、延迟、状态)。请求/响应体默认不会存储——在付费层上,完整审计日志会流向您自己的S3/R2/OSS。
零摩擦 工具的语义渐进式发现减少了代币使用和“上下文膨胀”

语义聚合

本页由 AI 翻译,技术细节请以原文为准。

README

以下为原文 README 节选,完整内容请查看原文。

MCPZERO

Publish, aggregate, secure and share local MCP servers in minutes.

Website · Docs · Dashboard

MCPZERO is a secure MCP aggregation gateway for the Model Context Protocol. It publishes, aggregates, and secures local MCP servers behind one zero-trust gateway URL so agents can discover tools on demand instead of loading every schema upfront.

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’

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.
在 GitHub 查看完整 README

安装

This server does not publish a one-line install command.

Open the repository installation guide 新手?先看 mcpskill.org 教程 →