MCPGate

MCPGate

MCPGate aggregates multiple MCP servers into a single unified endpoint, enabling centralized tool management with granular filtering, automatic namespacing, and observability. Features a real-time web dashboard and optional PostgreSQL-backed audit trails for monitoring and controlling AI tool access across local and remote deployments.

Category
访问服务器

README

MCPGate

Lightweight MCP gateway — aggregate, filter, and observe your MCP tools.

MCPGate sits between your MCP client (Claude Desktop, Claude Code, Cursor, VS Code) and multiple MCP servers. It presents a single unified MCP endpoint while giving you granular control over which tools are exposed.

Features

  • Tool Aggregation — Connect multiple MCP servers, expose all tools through one endpoint
  • Tool Filtering — Allow/block specific tools per server via simple YAML config
  • Tool Prefixing — Automatic namespacing (github.create_issue) to avoid collisions
  • Web Dashboard — Real-time status page showing servers, tools, and request logs
  • Dual Transport — Stdio (Claude Desktop) or HTTP/SSE (remote clients)
  • Audit Trail — Every tool call logged with timing; optional PostgreSQL persistence
  • Self-Hosted — Deploy on Railway, Docker, or run locally

Quick Start

Local (stdio — for Claude Desktop)

npx mcp-gate start --config mcpgate.yaml

Add to your claude_desktop_config.json:

{
  "mcpServers": {
    "mcpgate": {
      "command": "npx",
      "args": ["-y", "mcp-gate", "start", "--config", "/path/to/mcpgate.yaml"]
    }
  }
}

Local (HTTP — with dashboard)

npx mcp-gate start --config mcpgate.yaml
# Dashboard at http://localhost:3000
# MCP endpoint at http://localhost:3000/mcp

Docker

docker compose up
# Dashboard at http://localhost:3000
# Includes PostgreSQL for persistent audit trail

Or standalone:

docker run -p 3000:3000 \
  -e MCPGATE_CONFIG=$(cat mcpgate.yaml | base64 -w 0) \
  -e GITHUB_TOKEN=$GITHUB_TOKEN \
  ghcr.io/mprezz/mcpgate

Railway

Deploy on Railway

Add a PostgreSQL plugin for persistent audit trail — MCPGate detects DATABASE_URL automatically.

Configuration

Create a mcpgate.yaml:

gateway:
  name: "my-gateway"
  transport: "stdio" # stdio | http | both
  port: 3000
  toolPrefix: true # prefix tools with server name

servers:
  - name: "github"
    transport: "stdio"
    command: "npx"
    args: ["-y", "@modelcontextprotocol/server-github"]
    env:
      GITHUB_TOKEN: "${GITHUB_TOKEN}"
    tools:
      allow:
        - "create_issue"
        - "search_repos"

  - name: "filesystem"
    transport: "stdio"
    command: "npx"
    args: ["-y", "@modelcontextprotocol/server-filesystem", "/home/user"]
    tools:
      block:
        - "write_file"
        - "delete_file"

logging:
  level: "info"

See mcpgate.example.yaml for the full reference.

Tool Filtering

Each server supports allow or block (mutually exclusive):

  • allow — Only these tools are exposed (whitelist)
  • block — All tools EXCEPT these are exposed (blacklist)
  • Neither — All tools are exposed

Authentication

Add a bearer token to protect the HTTP transport:

gateway:
  auth:
    token: "${MCPGATE_AUTH_TOKEN}"

When auth is configured:

  • All endpoints require Authorization: Bearer <token> header
  • /health remains public (for Railway/Docker health checks)
  • MCP clients pass the token via custom headers in their transport config

Without auth configured, all endpoints are open (for local/private use).

Environment Variable Interpolation

Use ${VAR} or ${VAR:-default} in YAML to reference environment variables:

env:
  GITHUB_TOKEN: "${GITHUB_TOKEN}"
  API_URL: "${API_URL:-https://api.example.com}"

Dashboard

When running in HTTP mode, MCPGate serves a web dashboard at the root URL:

  • / — Status page with upstream servers, tools, and request logs
  • /api/status — JSON API for programmatic access
  • /health — Health check endpoint (for Railway/Docker)
  • /mcp — MCP protocol endpoint (Streamable HTTP)

Storage

MCPGate logs every tool call with timing and error information.

  • Default — In-memory (no setup required, lost on restart)
  • PostgreSQL — Set DATABASE_URL environment variable (tables created automatically)
# Local development with Docker Compose
docker compose up postgres -d
export DATABASE_URL=postgresql://mcpgate:mcpgate@localhost:5432/mcpgate
npx mcp-gate start --config mcpgate.yaml

Environment Variables

Variable Required Default Description
PORT No 3000 HTTP port (Railway sets this automatically)
MCPGATE_CONFIG No Base64-encoded YAML config (for Railway/Docker)
DATABASE_URL No PostgreSQL connection string (enables persistent audit trail)
LOG_LEVEL No info debug / info / warn / error
MCPGATE_AUTH_TOKEN No Bearer token for HTTP auth (reference in YAML via ${MCPGATE_AUTH_TOKEN})

Development

git clone https://github.com/mprezz/mcpgate.git
cd mcpgate
npm install

npm run dev          # development with hot reload
npm run build        # compile TypeScript
npm run test         # run tests (vitest)
npm run lint         # eslint
npm run typecheck    # tsc --noEmit

Architecture

Client (Claude, Cursor)
    │
    ▼ stdio or HTTP/SSE
┌──────────────────────────────┐
│         MCPGate              │
│                              │
│  ┌─────────────────────┐     │
│  │   Tool Registry     │     │  ← filters + namespaces tools
│  └─────────────────────┘     │
│  ┌─────────────────────┐     │
│  │   Tool Router       │     │  ← routes calls to correct server
│  └─────────────────────┘     │
│  ┌─────────────────────┐     │
│  │  Upstream Manager   │     │  ← manages server connections
│  └─────────────────────┘     │
│  ┌─────────────────────┐     │
│  │   Storage           │     │  ← memory or PostgreSQL
│  └─────────────────────┘     │
└──────────────────────────────┘
    │           │           │
    ▼           ▼           ▼
 Server A    Server B    Server C
 (GitHub)  (Filesystem)  (Custom)

License

Apache 2.0 — see LICENSE

推荐服务器

Baidu Map

Baidu Map

百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。

官方
精选
JavaScript
Playwright MCP Server

Playwright MCP Server

一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。

官方
精选
TypeScript
Magic Component Platform (MCP)

Magic Component Platform (MCP)

一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。

官方
精选
本地
TypeScript
Audiense Insights MCP Server

Audiense Insights MCP Server

通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。

官方
精选
本地
TypeScript
VeyraX

VeyraX

一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。

官方
精选
本地
graphlit-mcp-server

graphlit-mcp-server

模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。

官方
精选
TypeScript
Kagi MCP Server

Kagi MCP Server

一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。

官方
精选
Python
e2b-mcp-server

e2b-mcp-server

使用 MCP 通过 e2b 运行代码。

官方
精选
Neon MCP Server

Neon MCP Server

用于与 Neon 管理 API 和数据库交互的 MCP 服务器

官方
精选
Exa MCP Server

Exa MCP Server

模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。

官方
精选