Skip to main content
Glama

MCP Gateway

MCP Gateway dashboard

A compact non-production-ready MCP gateway.

Built with LLM-powered tools to befriend LLMs and the tools.

Use cases

  1. You need to expose the MCP server beyond localhost (ie for a dockerized harness)

  2. You want to use the MCP server, but disable some of its tools

  3. 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-gateway

Use 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.

A
license - permissive license
-
quality - not tested
C
maintenance

Maintenance

Maintainers
Response time
Release cycle
Releases (12mo)
Commit activity

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Servers

  • F
    license
    C
    quality
    D
    maintenance
    A 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.
    Last updated
    1
  • A
    license
    -
    quality
    C
    maintenance
    MCPGate 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.
    Last updated
    10
    Apache 2.0
  • F
    license
    -
    quality
    C
    maintenance
    A simple gateway that connects to multiple child MCP servers and forwards tool calls to them, enabling seamless client interactions with multiple tools.
    Last updated
    52

View all related MCP servers

Related MCP Connectors

  • Hosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup.

  • Self-hosted MCP gateway: turn any API, database or MCP server into AI connectors — no code.

  • 327 tools, 92 providers. Pay per call via x402 + MPP. One MCP endpoint.

View all MCP Connectors

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nikita-tomilov/mcp-gateway'

If you have feedback or need assistance with the MCP directory API, please join our Discord server