I just open‑sourced MCP Gateway, a flexible reverse‑proxy / management layer for Model Context Protocol servers, written in Go.
Why ?
- Centralize multiple MCP servers behind one endpoint
- Add OAuth2 / JWT auth, fine‑grained permissions and (soon) rate‑limiting
- Built‑in Prometheus metrics, structured logs and more
What it does ?
- Automatically discovers tools on each proxied server and namespaces them (server:tool_name) to avoid collisions.
- Keeps long‑running SSE / streamable‑HTTP connections alive with heartbeat monitoring and graceful restarts.
- Ships a ready‑to‑run Docker image for quick trials (soon k8s deployment).
Looking for feedback
The project is still early ( welcome!). I’d love reviews on:
- the permission model (scopes ↔ JWT claims)
- performance under heavy SSE load
- missing observability knobs
- anything that would make adoption easier
Thanks for reading!
— Matthis
razchn•6mo ago
Might be interesting for us, I’ll take a further look later
mholleville•6mo ago
First news for me ! :-)
I just open‑sourced MCP Gateway, a flexible reverse‑proxy / management layer for Model Context Protocol servers, written in Go.
Why ?
- Centralize multiple MCP servers behind one endpoint - Add OAuth2 / JWT auth, fine‑grained permissions and (soon) rate‑limiting - Built‑in Prometheus metrics, structured logs and more
What it does ?
- Automatically discovers tools on each proxied server and namespaces them (server:tool_name) to avoid collisions. - Keeps long‑running SSE / streamable‑HTTP connections alive with heartbeat monitoring and graceful restarts. - Ships a ready‑to‑run Docker image for quick trials (soon k8s deployment).
Looking for feedback
The project is still early ( welcome!). I’d love reviews on: - the permission model (scopes ↔ JWT claims) - performance under heavy SSE load - missing observability knobs - anything that would make adoption easier
Thanks for reading!
— Matthis