Connect Your Heatmaps to Claude via MCP (1 Minute, One Command)
- how-to
- mcp
- claude
- ai
- integration
TL;DR
- HeatMapX speaks MCP (the open standard for plugging tools into AI assistants). Free on every plan
- Setup is two steps โ issue an API key, run one command โ about a minute
- Once connected, Claude can query your heatmaps, page stats and A/B test results inside the conversation
"Open the dashboard โ copy the numbers โ paste them into the AI" โ that round-trip gets old fast. With MCP, Claude fetches your HeatMapX data itself, and the whole analysis happens in one conversation.
What is MCP?
MCP (Model Context Protocol) is the standard for connecting external tools to AI assistants like Claude. Think of it as a universal power socket: plug in once, and the AI grabs the data it needs, whenever it needs it.
Setup (2 steps)
1. Issue an API key
In your HeatMapX dashboard, go to Settings โ API keys and click "Issue new key". The key is shown only once โ copy it right away.
2. Run one command
In your terminal (replace YOUR_API_KEY with the key you copied):
claude mcp add --transport http heatmapx https://heatmapx.com/api/mcp --header "Authorization: Bearer YOUR_API_KEY"
Done. Restart Claude Code (or start a new conversation) and the HeatMapX tools are available.
What you can do
Once connected, questions like these just work:
- "Show me my sites" โ your registered sites and URLs
- "Which page on kpop-ticket.com has the worst scroll depth?" โ found from per-page stats
- "Summarize the heatmap for /pricing" โ click hotspots and scroll reach
- "How's my A/B test doing? Can I call a winner yet?" โ variant metrics plus a statistically grounded winner suggestion
HeatMapX supplies the numbers; Claude does the interpreting. Each side doing what it's best at.
Available tools (read-only)
| Tool | What it returns |
|---|---|
| list_sites | Your registered sites |
| get_page_stats | Per-page sessions, clicks, average scroll depth |
| get_heatmap_summary | Heatmap aggregates for one page (with time window) |
| list_experiments | Your A/B experiments |
| get_experiment_results | Variant metrics, uplift, winner suggestion |
There are no write tools โ everything is read-only, so the AI can never accidentally change your data.
If it doesn't connect โ checklist
- Key pasted wrong? Make sure you pasted the whole string starting with
hmx_live_ - Client support: you need an MCP client that supports custom headers (Claude Code, Cursor, etc.). Claude Desktop custom connectors (OAuth) are on our roadmap
- Key revoked? Check Settings โ API keys for an active key
Pricing
MCP access is free on every plan (with a sensible burst limit only). Heatmaps and A/B tests, straight from Claude โ give it a try.