Mcp Gateway

Created By
Timandesa year ago
Overview

what is MCP Gateway?

MCP Gateway is a tool that translates Model Context Protocol (MCP) tool calls into traditional HTTP API requests, allowing for a configurable interface between existing HTTP APIs and MCP tools.

how to use MCP Gateway?

To use MCP Gateway, create a configuration file from config.example.yaml, edit it to map your APIs to MCP tools, and then launch the gateway using the command uv run mcp-gateway.

key features of MCP Gateway?

  • Translates MCP tool calls to HTTP API requests.
  • Configurable server settings and tool mappings.
  • Supports different transport methods (SSE and stdio).

use cases of MCP Gateway?

  1. Integrating legacy HTTP APIs with modern MCP tools.
  2. Facilitating communication between different software components using MCP.
  3. Enabling developers to create custom API mappings easily.

FAQ from MCP Gateway?

  • What is the default port for MCP Gateway?

The default port is 3001, but it can be changed using the --port=<port_no> parameter.

  • Can I use MCP Gateway with any HTTP API?

Yes, as long as you configure the mappings correctly in the config.yaml file.

  • Is there a way to run MCP Gateway in stdio transport?

Yes, you can launch it with the parameter --transport=stdio.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Timandes
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago