Mcp Gateway

Name: Mcp Gateway
Author: Timandes

@Timandes

Repository

About Mcp Gateway

No overview available yet

#mcp-gateway #http-api #gateway

Basic information

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "mcp-gateway-timandes": {
      "command": "uv",
      "args": [
        "run",
        "mcp-gateway"
      ]
    }
  }
}

Tools

Tool name (Function name), which is provided to LLM.

Tool description through which LLM can understand what the tool could do.

Arguments of tool (Function arguments).

Request mapping to target HTTP API.

Response mapping for response of target HTTP API.

Boolean

HTTP method

Target HTTP API url template

HTTP headers

Header key

Header value template

Response body template

Overview

What is MCP Gateway?

MCP Gateway is a server that translates Model Context Protocol (MCP) tool callings into traditional HTTP API requests, providing a configurable bridge to expose existing HTTP APIs through MCP.

How to use MCP Gateway?

Copy the example config file (config.example.yaml) to config.yaml, then edit it to map HTTP APIs to MCP tools. Launch the server with SSE transport using uv run mcp-gateway (default port 3001). For stdio transport, use --transport=stdio and configure it in Cursor, Cline, or MCP Inspector with command uv run mcp-gateway --transport=stdio.

Key features of MCP Gateway

Translates MCP tool calls to HTTP API requests
Configurable via YAML mapping file
Supports SSE and stdio transport modes
Allows dynamic config references with {{.config.xxx}} templates
Customizable request and response templates
Easily changeable server port via --port parameter

Use cases of MCP Gateway

Expose legacy REST APIs to AI agents using MCP
Create MCP tools from any HTTP API without writing code
Integrate existing web services into LLM-driven workflows
Bridge internal microservices with MCP-compatible clients

FAQ from MCP Gateway

What runtime or dependencies are required?

MCP Gateway runs via uv, requiring Python and the uv package manager to execute uv run mcp-gateway.

What transport protocols does MCP Gateway support?

The server supports SSE (default, on port 3001) and stdio transport, selectable with the --transport parameter.

How do I define a tool-to-API mapping?

Edit the tools section of config.yaml with tool name, description, arguments, a request template (URL, method, headers), and a response template for the HTTP API response.

Where does configuration data live?

All configuration is stored in a local YAML file (config.yaml) that you create from config.example.yaml. No external database is used.

Can I reference secrets or dynamic values in requests?

Yes, use Go‑template expressions like {{.config.apiKey}} and {{.args.address}} in the request template URL and headers. Static config values are defined under server.config.