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 Gatewaydisable the github tool"
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.
MCP Gateway

A compact non-production-ready MCP gateway.
Built with LLM-powered tools to befriend LLMs and the tools.
Use cases
You need to expose the MCP server beyond localhost (ie for a dockerized harness)
You want to use the MCP server, but disable some of its tools
You need to expose the MCP, using one protocol, to a harness using other protocol
It routes (proxies) tool calls to configured downstream MCP servers.
It currently supports downstream streamable-http and sse transports.
It also has a dashboard where you can enable or disable certain tools.
Related MCP server: MCPGate
Run
uv sync
cp gateway.example.json gateway.json
uv run mcp-gatewayUse the MCP Inspector or any MCP client against /http/mcp (or /sse/sse for a legacy client).
Configure upstream clients
Add http://localhost:64345/http/mcp as an endpoint to your client or harness.
Configure downstream servers
Edit gateway.json accordingly.
headers are optional and are never shown by the dashboard.
disabled_tools is optional per server. List downstream tool names (before any gateway renaming) to hide at startup.
Restart the gateway after changing this list.
Exposed tools
The gateway exposes only tools discovered from downstream servers. It copies each tool's name, description, schemas, annotations, and result without a gateway wrapper.
When two or more downstream servers expose the same tool name, every conflicting tool is exposed as
servername-toolname, for example github-search.
Tool discovery happens at gateway startup. Restart the gateway to pick up downstream inventory changes.
Disclaimer
This is a starter gateway, not an authorization boundary. Expect bugs. Never expose beyond localhost.
This server cannot be deployed
Maintenance
Related MCP Connectors
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
- gatewayOAuthai.sealgate
MCP gateway with runtime security policy, tool-call-level control, and audit of agent actions.
Zero-setup MCP gateway securely connecting AI to your tools with authentication and workflows
The OpenRouter for tools. One MCP connection gives any AI agent 254 hosted tools, pay per call.
Related MCP Servers
- FlicenseCqualityDmaintenanceA powerful gateway for the Model Context Protocol (MCP) that unifies AI toolchains by federating multiple MCP servers, wrapping REST APIs as MCP tools, and supporting multiple transport methods with an admin dashboard.1-
- AlicenseNot gradedqualityDmaintenanceMCPGate 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.6 npmApache 2.0
- FlicenseNot gradedqualityCmaintenanceA simple gateway that connects to multiple child MCP servers and forwards tool calls to them, enabling seamless client interactions with multiple tools.13 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.410 npm37MIT