MCP Gateway
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
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: MCP-Gateway
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.
Related MCP Connectors
Single-connection MCP gateway discovering and executing 490+ verified MCP & A2A tools.
Governed MCP gateway: one endpoint for your tools, with credential custody and audit log.
Toolstile is a managed MCP gateway that connects remote MCP servers behind one endpoint, with per-agent permissions, shared accounts and activity logs. Connect at https://mcp.toolstile.com/mcp over Streamable HTTP with OAuth; sign in at https://toolstile.com, select a workspace and connect your upstream servers. Available tools, resources and prompts depend on that workspace and the agent's granted access.
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
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 gradedqualityDmaintenanceA simple gateway that connects to multiple child MCP servers and forwards tool calls to them, enabling seamless client interactions with multiple tools.36 npmISC
- 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.418 npm38MIT
- FlicenseNot gradedqualityDmaintenanceA configurable MCP gateway that runs multiple Streamable HTTP MCP servers and exposes all their tools through a single endpoint, enabling tool aggregation and routing for MCP clients.1-