iflow-mcp-sitepic

# MCP Gateway MCP (Model Context Protocol) Gateway can translate MCP tool callings to traditional HTTP API requests. It can provide a configurable way to get existing HTTP API to MCP territory. ## Getting Started Create config file from `config.example.yaml`: ```shell $ cp config.example.yaml config.yaml ``` Edit `config.yaml` file, map all APIs to MCP tools. Then start launch it with SSE transport: ```shell $ uv run mcp-gateway INFO: Started server process [15400] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:3001 (Press CTRL+C to quit) ``` Default is 3001. ## Server Control ### Change Port Provide parameter `--port=<port_no>` in command line will change the port to SSE transport. Launch gateway with port 3002: ```shell $ uv run mcp-gateway --port=3002 INFO: Started server process [15400] INFO: Waiting for application startup. INFO: Application startup complete. INFO: Uvicorn running on http://0.0.0.0:3002 (Press CTRL+C to quit) ``` ### stdio Transport Provide parameter `--transport=stdio` in command line will change the transport to stdio. E.G.: ```shell $ uv run mcp-gateway --transport=stdio ``` It's meaningless to **manually** launch gateway in stdio transport. You can configure in Cursor or Cline like: ```json { "mcpServers": { "mcp-gateway": { "command": "uv", "args": ["run", "mcp-gateway", "--transport=stdio"] } } } ``` Or MCP Inspector with form values: | Item | Value | | -------------- | --------------------------------- | | Transport Type | STDIO | | Command | uv | | Arguments | run mcp-gateway --transport=stdio | ## Configuration File There is two parts in configuration YAML, `server` and `tools`. `server` defines the basic info for gateway server use. `tools` defines the mapping…