tbxark/mcp-proxy

What it solves

This project provides a way to consolidate multiple Model Context Protocol (MCP) servers into a single HTTP entry point. This simplifies the connection process for clients that cannot handle multiple server connections or need a unified interface for tools, prompts, and resources.

How it works

The proxy server acts as an aggregator. It connects to various downstream MCP servers using different transport methods—including stdio, sse, and streamable-http—and exposes them as a single unified endpoint. It also handles OAuth token management, allowing a user to authorize once against a server (like Notion) and letting the proxy manage token refreshes for all subsequent callers.

Who it’s for

Developers and users of MCP-compatible AI agents or clients that need to access tools and resources from multiple sources without managing multiple separate connections.

Highlights

• Unified Entrypoint: Aggregates tools, prompts, and resources from multiple servers.
• Transport Flexibility: Supports stdio, sse, and streamable-http client types.
• OAuth Management: Centralizes OAuth authorization and token refreshing for downstream servers.
• SSE and Streamable HTTP: Serves content via Server-Sent Events or streamable HTTP.