MCP · Model Context Protocol

MCP server

Operate AXO from Claude or any MCP client through 130+ tools. Hosted endpoint, scoped tokens, streamable HTTP — the same operations your team runs in the app, as tool calls.

The endpoint

The hosted MCP server speaks streamable HTTP (stateless JSON-RPC) at a single URL:

Endpoint

POST https://axoapp.ai/api/mcp

1. Generate a token

In the AXO dashboard, open Settings → MCP Tokens and create a token. Tokens are scoped per site and role-gated — you pick how much the agent can do. The plaintext mcpt_… value is shown once; store it in your client's secret config. Owners and admins can mint tokens.

Scopes

Every token carries one scope. The server derives the scope each tool requires from its operation and rejects calls that exceed the token's scope with a structured insufficient_scope error — so a read token can never mutate your site.

Token scopes

Scope	Type	Description
read optional	scope	Read-only tools: analytics, lift, segments, profiles, zones, content — anything that only queries.
write optional	scope	Everything in read, plus create/update tools: draft variants, create segments, wire placements, create triggers.
admin optional	scope	Everything in write, plus destructive/sensitive tools: delete content, publish site overrides, force variant allocation, GDPR profile erasure.

2. Point your client at the endpoint

Add AXO to your MCP client config. Most remote-capable clients (Claude Desktop, custom connectors) take an HTTP server with a bearer header; if you prefer to run it locally, the server also ships as an npx package.

{
  "mcpServers": {
    "axo": {
      "type": "http",
      "url": "https://axoapp.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer mcpt_YOUR_TOKEN"
      }
    }
  }
}

3. List the tools

Confirm the connection by listing tools over JSON-RPC. Every tool ships a rich, agent-readable description and a JSON Schema for its inputs — browse them all in the tool reference, or fetch the machine-readable manifest.

curl

curl -sS https://axoapp.ai/api/mcp \
  -H "Authorization: Bearer mcpt_YOUR_TOKEN" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

QUESTIONS PEOPLE ASK

Do I need to install anything?

No. AXO hosts the MCP server at https://axoapp.ai/api/mcp over streamable HTTP — point any MCP-capable client at it with a bearer token. A local stdio package (npx axo-mcp) is also available if you prefer to run it yourself.

What stops an agent from breaking my site?

Scoping. MCP tokens are minted per-site with a read, write, or admin scope; the server returns an insufficient_scope error when a tool needs more than the token carries. Start an agent on a read token and graduate it deliberately.

Is every tool also available over REST?

The read surface is available over the Pulse REST API for profiles and segments. MCP is the broadest surface and the natural fit for conversational agents; REST fits pipelines and custom code.