Skip to main content
These docs are published with a built-in Model Context Protocol server. Connect it to an AI assistant and it can search this documentation directly instead of guessing from training data.
This server exposes the documentation. It does not read your workspace, contacts, campaigns, or any account data. To work with your own data programmatically, use the API.

​
Server URL

The transport is HTTP. No API key or account is required — the docs are public.

​
Connect it

​
What it can do

​
Worth asking it

Once connected, questions that used to mean digging through reference tables work directly:
  • “What columns are on contact_360, and which are nullable?”
  • “Write me a SQL query for high-value wallets that have gone quiet.”
  • “Which automation trigger fires on a first mint, and what filter does it use?”
  • “Show me how to send a custom event with an idempotency key.”
  • “Why would deliveredNow be false on an in-app push?”
Because the assistant reads the actual reference tables, it won’t invent column names or trigger types — the failure mode these docs exist to prevent.

​
Reading a single page

Every page can also be pulled directly without MCP. Use the contextual menu at the top of any page to copy it as Markdown, open it in an assistant, or copy the MCP server URL. You can also append .md to any docs URL to get the raw Markdown source:
That’s often the fastest way to hand one specific page to an assistant without configuring anything.

​
The Onchain Suite API is not an MCP server

Worth stating plainly, because the naming invites confusion:
  • These docs publish an MCP server, at the URL above.
  • The Onchain Suite API is a REST API. It does not expose an MCP endpoint. See API Overview and Authentication.
If you want an AI agent to act on your data, point it at the REST API with a secret key — the same surface described throughout the developer docs.