Loading…
An always-on MCP gateway for AI agents such as Cursor, Claude Desktop, and Kiro. It intelligently routes tool calls, launches downstream servers only when needed, handles authentication, and automatically removes idle connections—reducing resource usage, keeping systems lightweight, and preserving valuable context-window space.
mux-mcp-gateway is an MCP server entry in ChatHome Skills, sourced from GitHub MCP Search and scored 26/100. An always-on MCP gateway for AI agents such as Cursor, Claude Desktop, and Kiro. It intelligently routes tool calls, launches downstream servers only when neede. As a Model Context Protocol server, it exposes tools that MCP-compatible LLM clients such as Claude, Cursor, and Copilot can call directly, extending an agent's reach beyond its built-in capabilities. ChatHome Skills discovered this entry through its daily ingest of official registries and GitHub discovery queries, and re-verifies repository facts, freshness signals, and install metadata on every run. The quality score weighs official-registry presence, a working install command, license clarity, GitHub star trajectory, and repository freshness — the full formula is on the Sources page. The install command above is ready to copy. Review the last-pushed date and repository status before adding mux-mcp-gateway to a production agent workflow; the snapshot facts below are point-in-time values from the most recent ingest.
git clone https://github.com/BhavanPatel/mux-mcp-gateway.gitReview the upstream source before running this command.
Downloads a script and pipes it straight into a shell, executing remote code with no review.
curl -sL https://mux-gateway.vercel.app/install.sh | bashDispute this flag?Scan coverage: Install metadata and repository README.
Automated signals from install metadata and a bounded skill body — not a full code security audit and not a recursive source or dependency review.
{
"fullName": "BhavanPatel/mux-mcp-gateway"
}An always-on MCP gateway for AI agents such as Cursor, Claude Desktop, and Kiro. It intelligently routes tool calls, launches downstream servers only when needed, handles authentication, and automatically removes idle connections—reducing resource usage, keeping systems lightweight, and preserving valuable context-window space.