Foxxy Bridge

MCP Foxxy Bridge

Overview

MCP Foxxy Bridge is a secure one-to-many proxy for the Model Context Protocol (MCP). Connect multiple MCP servers through a single endpoint with enterprise-grade security.

✨ Key Benefits

🔌 Single Endpoint: Access all your MCP servers through one connection point
🛡️ Enterprise Security: OAuth 2.0 + PKCE authentication with configurable SSL verification
⚡ Easy Setup: Simple configuration with environment variable support
🔀 Smart Routing: Automatic request routing to the right backend server
🏠 Secure by Default: Localhost-only binding, SSL verification enabled, and comprehensive input validation
🚀 HTTP/2 Support: Automatic protocol upgrade for improved performance

🎯 Perfect For

Connecting multiple MCP servers to Claude Desktop, VS Code, or other AI tools
Centralizing credential management with secure command substitution
Production deployments requiring OAuth authentication
Development environments with multiple data sources

🚀 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'

# With security features
mcp-foxxy-bridge --bridge-config config.json \
  --allow-command-substitution  # Enable secure command substitution

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

🚀 Getting Started

📖 Documentation Overview - Start here for a complete guide
⬇️ Installation Guide - Multiple installation methods
⚙️ Configuration Guide - Configure your setup
🎯 Example Configurations - Ready-to-use config files

🔧 Advanced Usage

🚀 Deployment Guide - Docker, production deployments
🔌 API Reference - Programmatic integration
🏗️ Architecture Overview - Technical deep dive

📡 REST API Endpoints

The bridge provides REST endpoints for operational management, monitoring, and tool discovery:

Server Discovery & Status:

# Global bridge health and status
curl http://localhost:9000/status

# List all configured servers and their endpoints
curl http://localhost:9000/sse/servers

# List all available tags and their associated servers
curl http://localhost:9000/sse/tags

# Individual server status and health metrics
curl http://localhost:9000/sse/mcp/filesystem/status

Tool Discovery:

# List all available tools from all servers
curl http://localhost:9000/sse/list_tools

# List tools for a specific server
curl http://localhost:9000/sse/mcp/filesystem/list_tools

# List tools filtered by tags (supports union and intersection)
curl http://localhost:9000/sse/tag/development/list_tools      # Single tag
curl http://localhost:9000/sse/tag/dev+local/list_tools        # Intersection (AND)
curl http://localhost:9000/sse/tag/web,api/list_tools          # Union (OR)

Server Management:

# Force reconnection of a specific server
curl -X POST http://localhost:9000/sse/mcp/filesystem/reconnect

# Refresh tool capabilities across all servers
curl -X POST http://localhost:9000/sse/tools/rescan

OAuth Status (for OAuth-enabled servers):

# Check OAuth authentication status
curl http://localhost:9000/oauth/filesystem/status

These endpoints are ideal for monitoring, debugging, and operational management of your MCP bridge deployment.

🛡️ Security & Production

🔒 Security Guide - Comprehensive security practices
🔐 OAuth Authentication - Enterprise authentication setup

🆘 Support

🔧 Troubleshooting Guide - Common issues and solutions
🤝 Contributing Guide - Development setup and guidelines

🛠️ Development

🤝 Contributing & Support

⚖️ License

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

This server cannot be installed

security - not tested

license - not found

quality - not tested

How are these scores calculated?

hybrid server

The server is able to function both locally and remotely, depending on the configuration or use case.

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.

Related MCP Servers

APISIX-MCP
api7
A
security
A
license
A
quality
The APISIX Model Context Protocol (MCP) server bridges large language models (LLMs) with the APISIX Admin API.
Last updated -
32
301
25
Apache 2.0
mcprouter
chatmcp
-
security
A
license
-
quality
A proxy service that connects MCP clients to remote MCP servers, allowing users to use server keys from MCP.so to access remote resources without running their own server.
Last updated -
20
3
MIT License
Atrax
metcalfc
-
security
F
license
-
quality
Proxy that aggregates multiple MCP servers and presents them as a unified interface, allowing clients to access resources from multiple servers transparently.
Last updated -
5
Enkrypt AI Secure MCP Gatewayofficial
enkryptai
-
security
A
license
-
quality
A proxy server that sits between MCP clients and servers, providing authentication, tool discovery, caching, and guardrail enforcement to protect MCP servers from malicious inputs.
Last updated -
25
MIT License

View all related MCP servers