mcp-gateway

Overview

MCP Gateway is a production-ready infrastructure component that enables organizations to expose existing systems as MCP servers. Built in Rust, it provides both an adapter for wrapping HTTP APIs and stdio MCP servers, and a gateway for multi-tenant management with authentication, policies, and transformations. The solution supports aggregating multiple tool sources, allowing teams to create focused tool surfaces per use case with proper isolation between environments.

Try asking AI

After installing, here are 4 things you can ask your AI assistant:

• create_invoice

  Create an invoice for a customer and return the created invoice JSON.

  Try:Create an invoice for customer123 with amount 1000 in USDTry:Generate a new invoice for client ABC with dry run mode
• billing_api:create_invoice

  Create an invoice for a customer (with collision prefix).

  Try:Create an invoice using the billing APITry:Generate a new invoice for billing purposes

Note: Tool names and descriptions were extracted from the HTTP tools DSL example in the README. This appears to be the only section that explicitly defines MCP tools, though the actual tools exposed depend on the configuration provided to the ada

Comparable tools

Installation

# Download the compose file
curl -fsSL -o mcp-gateway-compose.yml \
  https://raw.githubusercontent.com/unrelated-ai/mcp-gateway/main/docker-compose.quickstart.yml

# Start the stack
GATEWAY_VERSION=0.12.3 UI_VERSION=0.8.2 \
  docker compose -f mcp-gateway-compose.yml up -d

{
  "mcpServers": {
    "gateway-server": {
      "command": "docker",
      "args": ["run", "--rm", "ghcr.io/unrelated-ai/mcp-gateway:latest"],
      "env": {
        "PROFILE_ID": "your-profile-id"
      }
    }
  }
}

FAQ

What protocols does the gateway support?

The gateway supports HTTP MCP protocol with streaming capabilities and integrates with OpenAPI specifications to convert REST endpoints into MCP tools.

How does tenant isolation work?

Tenants are isolated through a PostgreSQL database backend where each tenant has separate secrets, API keys, and tool configurations accessible only through their profile endpoints.

Compare mcp-gateway with