OpenClaw's ACP bridge silently drops MCP servers. We patched it. openclaw acp now routes them correctly.
If you've tried to mount MCP servers through openclaw acp in Zed or another IDE client, you've already hit it: "ignoring ${params.mcpServers.length} MCP servers". It's hard-coded. There's no config flag.
The APX MCP Bridge restores MCP server support cleanly, without forking the gateway.
A drop-in module that wraps OpenClaw's ACP translator, advertises MCP capabilities correctly, and routes MCP server registrations to the gateway instead of dropping them. Tested against Zed and the reference ACP client. Includes a working example, a README that actually walks you through it, and an install script that runs in under 60 seconds.
Every APX bridge is reviewed and tested by a human before it ships. After ClawHavoc, you shouldn't be installing unaudited skills into your gateway. We test on real OpenClaw versions, document the exact behavior, and tell you what we changed and why.
The $19/month tier means: when OpenClaw ships a new version, we test the bridge against it within 48 hours. Breaking change? You get a fixed version before it bites you. Security advisory in the OpenClaw ecosystem? You hear from us. New bridges in the APX catalog? You get them included.
Most operators start with the one-time install and add support if they go to production.