MCP Catalogs
Home

mcp-gateway

by MikkoParkkola·25·Score 46

Universal MCP Gateway that multiplexes tools with 95% token savings via Meta-MCP.

developer-toolsai-llmsecurity
9
Forks
1
Open issues
this month
Last commit
2d ago
Indexed

Overview

MCP Gateway is a sophisticated tool multiplexer that sits between AI clients and backend servers. Instead of loading hundreds of tool definitions into every request, it provides a compact Meta-MCP surface of just 14-17 tools that discover the right backend tool on demand. This approach dramatically reduces context window overhead from ~15,000 tokens (100 tools) to ~1,600 tokens, saving ~89% of token costs and enabling unlimited tool connections without context pressure.

Try asking AI

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

you:Connecting numerous MCP servers without burning context windows
you:Converting REST APIs to MCP capabilities with OpenAPI import
you:Securing AI tool access with centralized validation and hash-pinning
you:How does MCP Gateway save tokens?
you:Can I use it with existing MCP servers?
you:How does it handle security?

When to choose this

Choose MCP Gateway when you have multiple MCP servers and want to reduce context overhead, or when you need to connect REST APIs without building custom MCP servers.

When NOT to choose this

Don't choose MCP Gateway if you only have a small number of tools and servers, or if you need direct, low-latency connections to individual backend services without the gateway layer.

Tools this server exposes

12 tools extracted from the README
  • gateway_list_servers

    List all backend MCP servers connected to the gateway

  • gateway_list_tools

    List all tools available across all connected backend servers

  • gateway_search_tools

    Search for tools across all backends by name or description

  • gateway_invoke

    Invoke a specific tool from any connected backend server

  • gateway_stats

    Get usage statistics and performance metrics for the gateway

  • gateway_cost_report

    Generate a cost report showing token and financial savings

  • gateway_playbooks

    Show available playbooks for configuring and managing the gateway

  • gateway_profile_controls

    Access profile controls for managing tool usage and capabilities

  • gateway_reload

    Reload the gateway configuration without restarting the session

  • gateway_webhook_status

    Check the status of configured webhook endpoints

  • gateway_disabled_capabilities

    List any disabled capabilities or tools

  • gateway_doctor

    Run diagnostic checks on the gateway and its backends

Comparable tools

archestrakongportkeynexus

Installation

Installation Methods

**Homebrew (macOS/Linux, recommended)**

brew install MikkoParkkola/tap/mcp-gateway

**Cargo**

cargo install mcp-gateway

**Direct binary download**

# macOS Apple Silicon
curl -L https://github.com/MikkoParkkola/mcp-gateway/releases/latest/download/mcp-gateway-darwin-arm64 -o mcp-gateway && chmod +x mcp-gateway

**Docker**

docker run -v $(pwd)/gateway.yaml:/config.yaml ghcr.io/mikkoparkkola/mcp-gateway:latest --config /config.yaml

Setup

mcp-gateway setup wizard --configure-client
mcp-gateway serve
mcp-gateway doctor

FAQ

How does MCP Gateway save tokens?
Instead of loading every tool definition into each request, it uses a compact Meta-MCP surface of just 14-17 tools, reducing token overhead by ~89% compared to direct MCP connections.
Can I use it with existing MCP servers?
Yes, the gateway can import and route traffic to your existing MCP servers without requiring changes to them.
How does it handle security?
The gateway includes tool poisoning validators, SHA-256 capability hash-pinning, rug-pull detection, and provides a centralized audit surface for all capabilities.

Compare mcp-gateway with

GitHub →

Last updated · Auto-generated from public README + GitHub signals.