mcp-foxxy-bridge 1.3.1

A MCP Forward Proxy Bridge designed to be a one-to-many bridge allowing you to use a single MCP server to communicate with many MCP servers transparently.

MCP Foxxy Bridge

Overview

MCP Foxxy Bridge is a one-to-many proxy for the Model Context Protocol (MCP). It lets you aggregate and route requests to multiple MCP servers through a single endpoint, so you can:

• Centralize configuration for all your MCP servers
• Expose all tools, resources, and prompts from connected servers
• Route requests transparently to the right backend
• Use a single MCP endpoint in your AI tools (Claude Desktop, VS Code, etc.)

---

🚀 Quickstart

See the Installation Guide for full details.

1. Choose one of the following installation methods

A. Install via uv (Recommended):

uv tool install mcp-foxxy-bridge

B. Install latest from GitHub:

uv tool install git+https://github.com/billyjbryant/mcp-foxxy-bridge

C. Run with Docker (from GHCR):

docker run --rm -p 8080:8080 ghcr.io/billyjbryant/mcp-foxxy-bridge:latest --bridge-config /app/config.json

---

2. Run the Bridge

With config file:

mcp-foxxy-bridge --bridge-config config.json

Or with named servers:

mcp-foxxy-bridge --port 8080 \
  --named-server fetch 'uvx mcp-server-fetch' \
  --named-server github 'npx -y @modelcontextprotocol/server-github' \
  --named-server filesystem 'npx -y @modelcontextprotocol/server-filesystem'

See Configuration Guide for config file examples.

---

3. Connect Your AI Tool

Point your MCP-compatible client to:

http://localhost:8080/sse

See API Reference for integration details.

---

📚 Documentation

• Overview & Features
• Installation Guide
• Configuration Guide
• Deployment Guide
• API Reference
• Architecture Overview
• Troubleshooting Guide
• Example Configurations

---

🛠️ Development

• Development Setup
• Contributing Guide

---

🤝 Contributing & Support

• Contributing Guide
• Issue Tracker
• Discussions

---

🔒 Security

MCP Foxxy Bridge follows security best practices:

Network Security

• Default binding: Bridge binds to 127.0.0.1:8080 (localhost-only) by default
• MCP server isolation: Individual MCP servers communicate via local stdio pipes, never network ports
• Configurable access: Host and port settings can be configured via config file or CLI arguments

Configuration Priority

1. Command-line arguments (--host, --port) - highest priority
2. Configuration file bridge settings (bridge.host, bridge.port)
3. Secure defaults (127.0.0.1:8080) - lowest priority

Security Recommendations

• Keep the default 127.0.0.1 binding unless external access is required
• If external access is needed, use proper firewall rules and authentication
• Regularly update MCP server dependencies
• Monitor server logs for unusual activity

---

⚖️ License

This project is licensed under the GNU Affero General Public License v3.0 or later (AGPLv3+). See the LICENSE file for details.

---