Other clients
Connect any MCP client to Helipod, with the local server (stdio) or the hosted server (Streamable HTTP).
Any client that supports the Model Context Protocol can use Helipod. You need one of these two:
Local server (stdio)
| Setting | Value |
|---|---|
| Command | npx |
| Arguments | -y helipod-mcp |
| Environment | HELIPOD_API_KEY=hel_…, optionally HELIPOD_EMAIL_API_KEY=… |
Or install it once with npm install -g helipod-mcp and use helipod-mcp as the command with no arguments; it starts faster.
Optional environment variables: HELIPOD_API_URL (default https://api.helipod.io/api) and HELIPOD_EMAIL_API_URL (default https://mail.helipod.io/api/email).
Hosted server (Streamable HTTP)
| Setting | Value |
|---|---|
| URL | https://api.helipod.io/mcp |
| Header | Authorization: Bearer hel_… |
| Email tools | add X-Helipod-Email-Key: … |
The hosted server is stateless and answers POST only (no server-sent event stream, no sessions). A request without a key answers 401.
Test it with curl:
curl https://api.helipod.io/mcp \
-H "Authorization: Bearer $HELIPOD_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'Skills
Agents that read SKILL.md files can use the skills/ folder as it is. The skills installer knows many agents (Amp, Augment, Goose, Junie, Kiro, Qwen Code, Trae, Warp, Zed and others):
npx skills add helipodapp/mcp -gCheck it works
Ask the agent: "List my Helipod projects." It should call list_projects. If it cannot see the tool, check the client's MCP status view; if it says NO_API_KEY, the key did not reach the server's environment.