MCP Gateway logo

MCP Gateway

by minovap

The MCP Gateway aggregates multiple MCP resource servers through a single interface. It provides a unified endpoint for accessing and managing these servers.

View on GitHub

Last updated: N/A

What is MCP Gateway?

The MCP Gateway is a proxy server that consolidates access to multiple MCP (Model Context Protocol) resource servers. It simplifies interaction with these servers by providing a single entry point.

How to use MCP Gateway?

Configuration is done through environment variables, Claude desktop configuration, or a default config.json file. The gateway can merge configurations with Claude desktop config. Server configuration options include command, args, env, url, and toolOverrides. Use npm install, npm run dev, and npm run build for development.

Key features of MCP Gateway

  • MCP Proxy (single endpoint)

  • Batch Request Tool (optimized parallel execution)

  • Configuration Merging (with Claude desktop configuration)

  • Tool Overrides (customization)

Use cases of MCP Gateway

  • Centralized access to multiple MCP servers

  • Optimizing performance through batch requests

  • Integrating with Claude desktop environment

  • Customizing tool behavior for specific needs

FAQ from MCP Gateway

What is an MCP server?

Based on the context, it's likely a resource server adhering to the Model Context Protocol.

Where does the gateway look for configuration files?

It checks the MCP_CONFIG_PATH environment variable, Claude desktop config, and a config.json file in the current directory, in that order.

How can I override tool descriptions?

Use the toolOverrides section in the server configuration to provide a custom description for a specific tool.

Can I disable tools?

Yes, you can disable tools using the enabled or disabled options within the toolOverrides section.

What is the purpose of batch requests?

Batch requests allow for optimized parallel execution of multiple tool calls, improving performance when interacting with multiple MCP servers.