mcp-bridge-api

MCP Bridge API acts as a lightweight RESTful proxy that aggregates multiple MCP servers and exposes their capabilities through a unified API. It is designed to be compatible with any MCP-compliant backend and supports a flexible workflow for discovering and invoking tools across connected MCP servers. The server is intended to be run with Node.js and serves as the central gateway that clients (such as the Python MCP-Gemini Agent or the React Native MCP Agent) connect to, enabling multi-step tool execution, result aggregation, and security workflows across diverse MCP backends.

Prerequisites:

• Node.js 18+ installed on the host
• Access to run npm/yarn and start Node.js applications

Step-by-step installation:

1. Clone or download the MCP Bridge API repository.
2. Install dependencies (if a package.json is provided):

npm install

3. Start the MCP Bridge API server:

node mcp-bridge.js

4. Confirm the server is running by querying its base URL (default localhost and port as configured in the application). If needed, adjust configuration to bind to a specific host/port via environment variables or config files as documented in the repository.

Prerequisites recap:

• Node.js 18+ (or compatible version used by the project)
• Network access to any MCP backends you plan to expose via the bridge

Optional: If you plan to run in production, consider a process manager (e.g., PM2) and reverse proxy setup (e.g., Nginx) to handle restarts and TLS.

Tips and considerations:

• Ensure the MCP backends you want to bridge are reachable from the host running mcp-bridge.js.
• When integrating with the Python MCP-Gemini Agent or the React Native MCP Agent, verify the MCP Bridge URLs (default http://localhost:3000) match your deployment.
• Monitor the bridge for authentication or security policy requirements, especially if enabling risk-based execution levels.
• If you scale to multiple MCP servers, assign meaningful server names in the mcp_config to simplify monitoring and tooling.
• Check logs for connection issues with individual MCP servers and adjust timeouts or retry logic as needed.
• Keep Node.js and dependencies up to date to avoid incompatibilities with MCP server transports.