Skip to main content
Helium runs a Model Context Protocol server alongside the REST API, exposing the same capabilities as MCP tools — same validation, same credit pipeline, same prices — so an agent can call them directly without you writing any HTTP glue.

​
Endpoint

Note the -helium in the path — this is a separate MCP server from Horizon’s (/api/mcp/mcp), though the same Bearer API key authenticates both. See Authentication.

​
Add to Claude Code

​
Other MCP clients

Any client that supports a remote Streamable HTTP MCP server (Cursor, and others) can connect the same way: point it at https://lite.gravitygtm.com/api/mcp-helium/mcp and set an Authorization: Bearer YOUR_KEY header. A session with a missing or invalid key is rejected before any tool is reachable, same as a REST call with a bad key.

​
Available tools

Each tool’s inputs mirror its REST equivalent’s request body, and each billed call debits credits the same way a REST call would — see Credits & Pricing for exact costs, and the API Reference section in the sidebar for full parameter details.
start_sequence schedules the sequence and drafts each touch on the same cadence described in Using Helium in Slack, but a sequence started via MCP or REST (rather than Slack) has nowhere to post its Approve/Edit/Skip card — there’s no dashboard review UI yet. Until one exists, only start sequences from Slack, where every touch gets a real approval card before anything sends.
Tool results are returned as JSON text content. A failed call comes back as an MCP tool error carrying the same error body a REST call would return — see Errors & Rate Limits.