Local npx Bridge
@zingasuite/mcp is a tiny stdio bridge for MCP clients that can launch a local command but can't talk to a remote server directly (e.g. some Claude Desktop configs). It relays your client's stdio to the remote Streamable-HTTP server and injects your API key.
If your client supports remote MCP servers (Claude Code, Cursor), you don't need this — connect to
https://mcp.zingasuite.com/mcpdirectly.
Run it
ZINGASUITE_API_KEY=zk_live_YOUR_KEY npx -y @zingasuite/mcp
Environment variables
| Variable | Default | Notes |
|---|---|---|
ZINGASUITE_API_KEY |
(required) | Your zk_ key |
ZINGASUITE_MCP_URL |
https://mcp.zingasuite.com/mcp |
Override the server endpoint (e.g. for testing) |
How it works
The bridge launches the community mcp-remote proxy pointed at the Zingasuite endpoint and forwards the Authorization header. Because every tool, schema, and permission check lives on the server, the bridge never has to be updated as the tool surface grows — it's a dumb, stable pipe.
Requirements
- Node.js 18+.
Why a bridge exists at all
Remote MCP is the modern default, but not every client speaks it yet. The bridge closes that gap without asking you to run or maintain any server of your own.