Skip to main content
Horizon runs a Model Context Protocol server alongside the REST API. It exposes the same 11 billed 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

The Streamable HTTP MCP endpoint is:
Authenticate with the same Bearer API key you use for REST — 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/mcp and set an Authorization: Bearer YOUR_KEY header. Consult your client’s docs for where it wants the URL and custom header configured — the values are the same regardless of client. 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 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 on each underlying endpoint. Tool results are returned as JSON text content. A failed call (invalid arguments, insufficient credits, vendor error, etc.) comes back as an MCP tool error carrying the same error body a REST call would return — see Errors & Rate Limits.