cherry-mcp
por bitbrujo
Coding Agents & IDEsResumen
HTTP bridge that keeps MCP servers alive and exposes them via REST.
Descripción
Qué hace esta skill
HTTP bridge that spawns MCP servers as persistent child processes and exposes their tools via REST endpoints. Designed for agents that lack native MCP support, where exec-based spawning kills servers when they go idle. Includes auto-restart on crash, rate limiting, IP allowlisting, and audit logging.
Solves the stdio persistence problem that kills MCP servers when spawned via exec, without requiring native MCP client support in the consuming agent.
Cuándo usarla
- Calling GitHub MCP tools from an agent that only supports HTTP
- Keeping MCP servers alive across long-running automation sessions
- Bridging multiple MCP servers under a single HTTP interface
- Auto-restarting a crashed MCP server during an overnight batch job
- Restricting MCP tool access to specific IPs on a shared machine
Flujo de trabajo de ejemplo
User asks: use the GitHub MCP server's search tool from an OpenClaw agent
- 1
Register the server:
node cli.js add-server github npx @anthropic/mcp-github - 2
Set credentials:
node cli.js set-env github GITHUB_TOKEN ghp_xxx - 3
Start the bridge:
pm2 start bridge.js --name cherry-mcp - 4
POST to
http://localhost:3456/github/callwith the tool name and arguments - 5
Receive the MCP tool response as JSON over HTTP
GitHub MCP tools are callable via HTTP REST from any agent or script
Requisitos
- API keys or credentials required by each MCP server being bridged (e.g., GITHUB_TOKEN for GitHub MCP)
Instalación
clawhub install bitbrujo/cherry-mcpEjecuta el comando de la CLI o pega el prompt en Claude Code, Cursor, Codex o el agente de programación que uses.