MCP Gateway
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MCP Gatewaylist available tools"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
The gateway never knows the capabilities ahead of time. A provider โ typically a browser app โ connects, publishes its own MCP tools, resources, prompts and more, and executes them when an MCP client calls them. The gateway only registers, publishes and routes, staying completely domain agnostic.
It is a small, installable library. You build a real application by subclassing Gateway and
overriding hooks. The handlers themselves are written in JavaScript. This library never prescribes a
specific frontend โ the Provider SDK guide teaches the JS side generically.
๐ฆ Install
pip install mcp-gtw
# or
uv add mcp-gtwRelated MCP server: OpenClaw MCP Proxy
๐ The smallest gateway
from mcp_gtw.gateway import Gateway
app = Gateway().create_app()uv run python -m mcp_gtw.mainThis publishes a real MCP endpoint at /mcp, a private provider WebSocket at /provider and a health
check at /health. It exposes whatever capabilities the connected provider registers.
โ๏ธ One-click deploy
The image runs production-ready as a non-root process. Deploy it to any host that keeps a persistent
server (the /provider WebSocket needs one โ serverless like Vercel does not work):
Render, Railway and Fly.io run the Dockerfile as-is (they inject PORT, which the
gateway reads); on a VPS (Hostinger, โฆ) use Docker Compose. Full guide, including reverse proxy and
TLS: deployment.
๐งฉ Extending it
Subclass Gateway and override the hooks to attach your own domain logic:
from mcp_gtw.channel import Channel
from mcp_gtw.gateway import Gateway
class MyGateway(Gateway):
mcp_server_name = "my-app"
async def on_provider_connected(self, channel: Channel) -> None:
... # a provider session just came online
def register_routes(self, app) -> None:
super().register_routes(app)
... # add your own HTTP and WebSocket routes
app = MyGateway().create_app()Every behaviour is a swappable strategy with a secure default โ authentication, tokens, origins,
expiry and the wire codec. Change one by setting a *_class attribute or injecting an instance,
without touching the transport. See the Gateway library guide for every
override point, Extensibility for the strategy contracts, and
Auth recipes for token, username/password and client-supplied-token models.
๐ Documentation
Guide | What it covers |
Components, transports and request flows. | |
Install, run and connect an MCP client. | |
The | |
The swappable strategies, their contracts and the invariants. | |
Token, username/password and client-supplied-token models. | |
Every setting and environment variable. | |
The private gateway โ provider message protocol. | |
Writing the JavaScript provider and registering tools. | |
Turn any open page into a provider from DevTools. | |
Connecting Claude Code, generic clients and the Inspector. | |
The optional monitoring dashboard and its stats API. | |
The security model, tokens, origins and hardening. | |
Running the suite and the 100% coverage gate. | |
Docker, reverse proxies and scaling. |
๐๏ธ Layout
.
โโโ src/mcp_gtw/ # the library
โโโ tests/ # unit and integration tests (100% coverage)
โโโ docs/ # the guides linked aboveโ Requirements
Python 3.12+ โ tested on 3.12, 3.13 and 3.14 in CI (3.12 is the pinned local and Docker version)
Any MCP client (Claude Code, Cursor, the MCP Inspector, โฆ)
๐ Support
If this project saved you time, consider supporting it: GitHub Sponsors ยท Ko-fi.
Made with care by Paulo Coutinho.
Licensed under MIT.
This server cannot be deployed
Maintenance
Related MCP Connectors
MCP Gateway: wrap any MCP server with cold-start retries, uptime SLA, and per-execution MPP billing.
Remote MCP server exposing SMI Aware tools, resources, and skills over Streamable HTTP.
Hosted MCP server for task-first delegation to remote workstations and workers.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP Gateway that aggregates multiple upstream MCP servers into a single endpoint with persistent connections, tool registry, and authentication.20 npm2MIT
- FlicenseNot gradedqualityDmaintenanceExposes app-registered tools as an MCP server for OpenClaw, forwarding actual tool execution back to the app over a WebSocket bridge.-
- FlicenseNot gradedqualityDmaintenanceA simple gateway that connects to multiple child MCP servers and forwards tool calls to them, enabling seamless client interactions with multiple tools.9 npm-
- AlicenseAqualityAmaintenanceA zero-dependency MCP gateway: host your own tools, forward and curate tools from other MCP servers, expose them leanly to cut agent token cost, and gate every call through your own policy hooks before it runs.413 npm37MIT