mcp-proxy and my-cool-proxy
These are competitors offering different architectural approaches to MCP server aggregation: one uses a Lua-driven gateway pattern optimized for context efficiency, while the other provides HTTP-based proxy aggregation, so you would choose based on whether you prioritize minimal context usage or HTTP protocol compatibility.
About mcp-proxy
tbxark/mcp-proxy
An MCP proxy server that aggregates and serves multiple MCP resource servers through a single HTTP server.
Supports multiple MCP client transport types (stdio, SSE, streamable-http) and exposes aggregated tools, prompts, and resources via Server-Sent Events or streamable HTTP endpoints. Built in Go with Docker support for launching Node.js and Python-based MCP servers via `npx` and `uvx`. Includes a web-based Claude configuration converter for simplified client setup.
About my-cool-proxy
karashiiro/my-cool-proxy
Use as many MCP servers as you want while minimizing context usage. A code mode MCP server gateway driven with Lua 🌙
Implements progressive disclosure through Lua-driven tool chaining, loading tool descriptions incrementally rather than upfront to reduce context bloat. Acts as a unified gateway for multiple MCP servers with granular tool filtering and access control, replacing scattered per-application configurations. Supports advanced MCP protocol features including resources and skills, with a web dashboard for monitoring Lua script execution across all connected servers.
Related comparisons
Scores updated daily from GitHub, PyPI, and npm data. How scores work