HTTP Proxy

About

The HTTP Proxy acts as a central hub, consolidating diverse tools from multiple independent MCP CLI servers into a unified, accessible interface. It simplifies the management and consumption of various backend services by providing a single HTTP/SSE endpoint, eliminating the need for clients to connect to each server individually. This aggregation capability enhances workflow efficiency and streamlines integrations, offering configurable settings for each connected MCP server, including command execution, environment variables, work directories, and granular tool filtering.

Key Features

• Aggregates tools from multiple external MCP CLI servers
• Exposes a unified HTTP/SSE endpoint for aggregated tools
• Highly configurable per-server settings including command, arguments, environment variables, and timeouts
• Supports tool filtering (allow/block lists) for fine-grained control over exposed tools
• Built-in Server-Sent Events (SSE) server for real-time communication
• 0 GitHub stars

Use Cases

• Consolidate access to various MCP tools (e.g., filesystem, GitHub, database) under a single network entry point
• Simplify client-side integration by providing a unified API for a suite of backend services
• Create a centralized hub for managing and interacting with distributed Model Context Protocol (MCP) tools