Product
Solutions
Retail & CommerceB2B & Lead GenHealthcare
Resources
BlogCompareMCP serverGlossaryROI calculator
Pricing
Sign inStart free trial
MCP · Model Context Protocol

Run your personalization from Claude.

AXO exposes 130+ MCP tools covering the whole personalization loop — analytics, segments, variants, placements, triggers, profiles. Connect any MCP client to the hosted endpoint with a scoped token, and your agent operates the same system your team drives in the app. No local install required.

Start free →Read the developer docs
130+ toolsHosted endpoint · no installScoped, role-gated tokensREST parity
THE TOOL SURFACE

Everything the app can do, a tool can do.

The tools aren't a demo subset. They span the operations the product actually runs on, granular enough to chain: read a segment, draft a variant, stage a placement, check the lift.

Analytics & lift
Read segment performance, funnel metrics, and holdout-proven lift reports.
Segments
Query behavioral cohorts, inspect membership, and check how each converts.
Variants & briefs
Draft copy and experiences from a campaign brief, staged for human review.
Placements & zones
Wire variants into page zones, reorder, publish, and roll back.
Triggers
Create and tune behavioral triggers — who fires what, when, on which signal.
Profiles & sessions
Look up visitor profiles, session history, and identity-merge state.
WHAT YOU'D ACTUALLY SAY

Prompts, not point-and-click.

› Which segments underperformed their 30-day baseline last week, and why?
› Draft three hero variants for the Comparison Shopper cohort and stage them for my review.
› What is the holdout lift on the pricing-page test, and is it significant yet?
› Audit every active placement and flag any variant that has not been touched in 90 days.

The agent answers from live data, drafts against your real zones and segments, and stages anything destructive for review. The human stays in the loop, not out of it.

CONNECTING

Three steps, no install.

01
Generate a token
In the AXO dashboard: Settings → MCP Tokens. Tokens are scoped per site and role-gated, so an agent only holds the permissions you give it.
02
Point your client at the endpoint
Add AXO's hosted MCP endpoint to Claude or any MCP-capable client. Prefer self-hosting? The MCP server also ships as a package.
03
Ask for something real
Start with reads — segments, lift, placements — then graduate the agent to drafting and staging once you've set the review gates.
QUESTIONS PEOPLE ASK

How do I connect Claude to AXO?

Point any MCP-capable client at AXO's hosted MCP endpoint and authenticate with an MCP token generated from Settings → MCP Tokens in the dashboard. There is nothing to install; a local server package is also available if you prefer to run it yourself.

What can an AI agent actually do through AXO's MCP server?

The tool surface spans the full personalization loop: reading analytics and holdout lift, querying segments, drafting variants from campaign briefs, modifying placements, firing triggers, and managing profiles. The same operations a person performs in the AXO app, an agent performs as tool calls — 130+ of them.

What stops an agent from breaking my site?

Scoping and review gates. MCP tokens are issued per-site with role-gated permissions, sensitive write paths require elevated roles, and drafted experiences can be staged for human review before anything is published. You decide where the agent acts autonomously and where it asks first — and the live decision path stays deterministic regardless of what the agent does upstream.

Is there a REST API too?

Yes. Every capability exposed over MCP is also reachable over REST with API keys, so scripted integrations and agents share one surface. MCP is the natural fit for conversational agents like Claude; REST fits pipelines and custom code.

New to the vocabulary? Start with what agent tooling is or what makes software agentic.

Give your agent something real to drive.

One tag, live in about 15 minutes — then hand your agent the keys you choose.

Start free trial →See the whole product