S
sunwen1983/mcpgate
MCP servers exist everywhere.
updated 2026-11-19
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · sunwen1983/mcpgate · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
sunwen1983/mcpgate;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# mcpgate
Excerpted from the repository README (abridged)
MCP servers exist everywhere. The production layer doesn't.
MCP (Model Context Protocol) servers are easy to write and easy to expose —
and that's the problem. A raw MCP server has no authentication, no rate
limiting, no caching, no circuit breaking, and no observability. Put one
behind your product and the first abusive client, the first slow backend,
or the first retry storm takes it down.
mcpgate is the production layer: a gateway that sits in front of your MCP
servers and adds auth, per-key rate limits, response caching, circuit
breakers, structured logs, and Prometheus metrics — without touching the
servers themselves.
┌─────────────────────────────────────────────┐
MCP client ──────▶│ mcpgate │
(any MCP client) │ │
│ ┌─────────┐ ┌──────────┐ ┌───────────┐ │
│ │ API key │─▶│ token │─▶│ cache │ │
│ │ auth │ │ bucket │ │ (TTL) │ │
│ └─────────┘ └──────────┘ └─────┬─────┘ │
│ ┌───────────┐ ┌───────────┐ │ │
│ │ circuit │─▶│ backend │◀────┘ │
│ │ breaker │ │ stdio / │ │
│ └───────────┘ │ HTTP │ │
│ /metrics /healthz /readyz └───────────┘ │
└─────────────────────────────────────────────┘
│ │
stdio child Streamable HTTP
MCP server MCP server
## Quickstart
bash
# Build
go build -o mcpgate ./cmd/mcpgate
go build -o echo-backend ./examples/echo-backend
# Run (examples/config.yaml uses the demo key "demo-key-123" — rotate it)
./mcpgate -config examples/config.yaml
List tools through the gateway:
bash
curl -X POST http://localhost:8080/mcp/echo \
-H 'Content-Type: application/json' \
-H 'X-API-Key: demo-key-123' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Call a tool:
bash
curl -X POST http://localhost:8080/mcp/echo \
-H 'Content-Type: application/json' \
-H 'X-API-Key: demo-key-123' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"add","arguments":{"a":2,"b":3}}}'
# {"jsonrpc":"2.0","id":2,"result":{"content":[{"type":"text","text":"5"}]}}
Or run the full guided demo (auth failure, cache MISS/HIT, rate-limit 429s,
health + metrics):
bash
bash demo/demo.sh
### Stdio mode
With -stdio, mcpgate itself runs as a stdio MCP server, aggregating
every configured backend behind one stdin/stdout stream — for
stdio-only clients (Claude Desktop, IDE extensions, MCP inspectors)
and server directories:
bash
./mcpgate -config examples/config.yaml -stdio
The gateway answers initialize/ping itself, merges all backends'
tool lists into one tools/list (a tool name claimed by more than
one backend is listed once — calls can only route to the first
owner, in sorted backend-name order), and routes each tools/call to the
backend that owns the tool. Per backend, the tool filter, circuit breaker, and
response cache apply exactly as on the HTTP path. Two HTTP concerns do
not apply: stdio is a local trust boundary, so there is no API-key auth
or rate limiting — whoever can spawn the process already controls it.
Logs go to stderr; stdout carries protocol traffic only.
## How it works
POST /mcp/{backend} runs one JSON-RPC 2.0 request through this pipeline:
1. Auth — X-API-Key header or Authorization: Bearer for API
keys; when oidc is configured, a Bearer JWT signed by the issuer is
also accepted (identity oidc: ); when oauth is configured, an
MCP (Model Context Protocol) servers are easy to write and easy to expose —
and that's the problem. A raw MCP server has no authentication, no rate
limiting, no caching, no circuit breaking, and no observability. Put one
behind your product and the first abusive client, the first slow backend,
or the first retry storm takes it down.
mcpgate is the production layer: a gateway that sits in front of your MCP
servers and adds auth, per-key rate limits, response caching, circuit
breakers, structured logs, and Prometheus metrics — without touching the
servers themselves.
┌─────────────────────────────────────────────┐
MCP client ──────▶│ mcpgate │
(any MCP client) │ │
│ ┌─────────┐ ┌──────────┐ ┌───────────┐ │
│ │ API key │─▶│ token │─▶│ cache │ │
│ │ auth │ │ bucket │ │ (TTL) │ │
│ └─────────┘ └──────────┘ └─────┬─────┘ │
│ ┌───────────┐ ┌───────────┐ │ │
│ │ circuit │─▶│ backend │◀────┘ │
│ │ breaker │ │ stdio / │ │
│ └───────────┘ │ HTTP │ │
│ /metrics /healthz /readyz └───────────┘ │
└─────────────────────────────────────────────┘
│ │
stdio child Streamable HTTP
MCP server MCP server
## Quickstart
bash
# Build
go build -o mcpgate ./cmd/mcpgate
go build -o echo-backend ./examples/echo-backend
# Run (examples/config.yaml uses the demo key "demo-key-123" — rotate it)
./mcpgate -config examples/config.yaml
List tools through the gateway:
bash
curl -X POST http://localhost:8080/mcp/echo \
-H 'Content-Type: application/json' \
-H 'X-API-Key: demo-key-123' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'
Call a tool:
bash
curl -X POST http://localhost:8080/mcp/echo \
-H 'Content-Type: application/json' \
-H 'X-API-Key: demo-key-123' \
-d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"add","arguments":{"a":2,"b":3}}}'
# {"jsonrpc":"2.0","id":2,"result":{"content":[{"type":"text","text":"5"}]}}
Or run the full guided demo (auth failure, cache MISS/HIT, rate-limit 429s,
health + metrics):
bash
bash demo/demo.sh
### Stdio mode
With -stdio, mcpgate itself runs as a stdio MCP server, aggregating
every configured backend behind one stdin/stdout stream — for
stdio-only clients (Claude Desktop, IDE extensions, MCP inspectors)
and server directories:
bash
./mcpgate -config examples/config.yaml -stdio
The gateway answers initialize/ping itself, merges all backends'
tool lists into one tools/list (a tool name claimed by more than
one backend is listed once — calls can only route to the first
owner, in sorted backend-name order), and routes each tools/call to the
backend that owns the tool. Per backend, the tool filter, circuit breaker, and
response cache apply exactly as on the HTTP path. Two HTTP concerns do
not apply: stdio is a local trust boundary, so there is no API-key auth
or rate limiting — whoever can spawn the process already controls it.
Logs go to stderr; stdout carries protocol traffic only.
## How it works
POST /mcp/{backend} runs one JSON-RPC 2.0 request through this pipeline:
1. Auth — X-API-Key header or Authorization: Bearer for API
keys; when oidc is configured, a Bearer JWT signed by the issuer is
also accepted (identity oidc: ); when oauth is configured, an
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/sunwen1983-mcpgate/)
- Source
- awesome · https://github.com/sunwen1983/mcpgate
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.