MCP Gateway
One endpoint for every MCP server your agent needs — fetch tool schemas on demand instead of loading everything upfront.
MCP Gateway aggregates multiple MCP servers behind a single headless HTTP/SSE endpoint. Its Code Mode exposes four meta-tools (listToolFiles, readToolFile, getToolDocs, executeToolCode) so agents discover signatures lazily and execute them in a hermetic Starlark sandbox.
- CLI:
mcp-gway(canonical) ormgw(alias) - Admin UI:
mcp-gway serve --transport http→ http://127.0.0.1:8080/
Why MCP Gateway
- Fewer wasted tokens — Agents fetch only the schemas they need, when they need them.
- One connection to manage — Add, remove, or refresh servers in a single registry; agents connect to one endpoint.
- Safe local-first defaults — Binds to
127.0.0.1by default, screens local commands via an allowlist, masks secrets, and CSRF-protects the admin dashboard.
Who It's For
- Agent developers wiring Pi, Antigravity, Claude Desktop, Cursor, or any MCP-compatible client to multiple MCP servers through one gateway.
- Operators running local-first infrastructure who want a CLI and dashboard with health probes, Prometheus metrics, and structured JSON logs.
Quick Start
- Install:
pip install mcp-gway - Add a server:
mcp-gway add files --type local --command "npx -y @modelcontextprotocol/server-filesystem /path/to/dir" - List servers:
mcp-gway list - Serve HTTP:
mcp-gway serve --transport http - Connect: Point your agent to
http://127.0.0.1:8080/mcp
For more examples and transports, see the CLI Reference and Integrations.
Features
- Multi-Server Aggregation — Connect to multiple MCP servers (local or remote) and expose them through a single endpoint. One URL for every agent; one registry to manage.
- Code Mode — Four meta-tools let LLMs discover schemas on demand and execute them in a hermetic sandbox, avoiding the need to load all tool definitions upfront.
- OAuth 2.0 Support — Built-in OAuth flow with Dynamic Client Registration (RFC 7591) and secure token storage.
- Hermetic Sandbox — Starlark-based sandbox for safe, constrained code execution.
- MCP Protocol Compliant — Implements the Model Context Protocol over HTTP, SSE, and stdio.
- Local-First Security — Local-first design with SSRF guards, command allow-lists, and CSRF protection.
- Built-In Observability — Structured JSON logs, Prometheus metrics, and health probes built in.
Documentation
- Configuration & Usage — add servers, transports, and OAuth
- CLI Reference — commands, options, and the admin dashboard
- Code Mode — lazy-discovery meta-tools and the sandbox
- Security — local-first controls and command allow-lists
- Observability — JSON logs, Prometheus metrics, health probes
- Integrations — Claude Desktop, Pi, Antigravity, OpenCode
- Architecture — system diagram and transports
- Development — tests, lint, and pre-commit
Development
uv sync --all-groups
uv run pytest -v # 647 tests
See docs/development.md for checks, probes, and pre-commit.
License
1 maintainer
Metadata
1 maintainer
Release files for mcp-gway 4.6.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| mcp_gway-4.6.3.tar.gz | 104.5 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| mcp_gway-4.6.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 227.1 kB
Release files / mcp_gway-4.6.3.tar.gz
| Download URL | mcp_gway-4.6.3.tar.gz |
|---|---|
| Size | 104.5 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
58cc276f7cc849da9ea0f1319f7ffd987275d5c0e161751322227275d58617a9
|
|
BLAKE2b-256 checksum How to use checksums |
c7d2290c9c476d0b07f3889ff24b397994ba1e8d8479d0058e324fb289a5fee3
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency logRelease files / mcp_gway-4.6.3-py3-none-any.whl
| Download URL | mcp_gway-4.6.3-py3-none-any.whl |
|---|---|
| Size | 122.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
842c823470385a705a378d7c29b434a3f80761a15ff82ad49a35db2769ccf501
|
|
BLAKE2b-256 checksum How to use checksums |
41d547c7be13174a8268a408ccba702e87ab2d6d5cf019e06456580f974fd6f4
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.7
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 10, 2026.
Transparency log
