home / mcp / mcp foxxy bridge mcp server

MCP Foxxy Bridge MCP Server

A one-to-many MCP Bridge.

Installation

Add the following to your MCP client configuration file.

Configuration

{
  "mcpServers": {
    "billyjbryant-mcp-foxxy-bridge": {
      "command": "npx",
      "args": [
        "-y",
        "@modelcontextprotocol/server-github"
      ]
    }
  }
}

MCP Foxxy Bridge provides a secure, single endpoint proxy that connects multiple MCP servers. It enables you to manage and route MCP traffic from a central gateway with enterprise-grade security features like OAuth 2.0, PKCE, HTTP/2, and a REST API, making it easier to operate multiple MCP services from one place.

How to use

You set up MCP Foxxy Bridge to aggregate several MCP servers behind one endpoint. Point your MCP client to the bridge’s endpoint and use the integrated CLI and REST API to manage connections, authentication, and server lifecycle.

Typical workflow after installation is to initialize the bridge configuration, add the MCP servers you want to proxy, start the bridge, and monitor its status.

To connect your MCP client, direct it to the bridge’s HTTP stream endpoint at http://localhost:8080/sse where the MCP traffic is exposed securely.

How to install

Prerequisites: you need the UV tool to install and run the bridge.

Install via UV (recommended) and then proceed with local configuration and startup commands.

uv tool install mcp-foxxy-bridge

foxxy-bridge config init

foxxy-bridge mcp add github "npx -y @modelcontextprotocol/server-github"
foxxy-bridge mcp add filesystem "npx -y @modelcontextprotocol/server-filesystem" --path ./

foxxy-bridge server start

foxxy-bridge server status

Configuration and operation notes

MCP Foxxy Bridge supports a secure, single endpoint for multiple MCP servers. It includes OAuth 2.0 with PKCE authentication, an enhanced CLI with daemon management, a REST API for operational control, secure command substitution, and HTTP/2 support.

The bridge can proxy local MCP servers declared at runtime. For each MCP server you add, you run it as a stdio-based process (for example, using npx) and supply the necessary arguments so the bridge can start and manage the upstream MCP server.

Security and integration notes

Use OAuth 2.0 with PKCE to authenticate clients and protect access to the bridge. The REST API is available for operational control, enabling you to manage MCP server connections, monitor status, and perform administrative tasks.

All traffic between the bridge and MCP servers is routed through the single endpoint, simplifying firewall rules and monitoring while preserving secure, authenticated access for each upstream MCP server.

Available tools

config init

Initialize bridge configuration to prepare for adding MCP servers.

mcp add

Add an MCP server by providing a name and the command to start the upstream MCP server (stdio type).

server start

Start the bridge daemon to begin proxying MCP traffic.

server status

Check the current status of the bridge and connected MCP servers.