Your store’s numbers,
inside your AI.
heatmap’s hosted MCP server connects your account to Claude, ChatGPT, Cursor and Codex. Ask a question in plain English and get live answers back, per-element revenue included.
No dashboards,
no exports, no SQL.
The Model Context Protocol is how an AI assistant reaches the tools you use. Connect heatmap to yours, ask “What were my top converting pages last month?”, and the answer comes straight from your account.
- Skip the dashboard
- No logging in, no exporting a report, no rebuilding the view every Monday.
- Describe it, don’t build it
- Say what you want to know. Your assistant works out the query.
- Data you can’t get anywhere else
- Per-element revenue, funnels and journeys, live from heatmap.
Ask about anything heatmap measures.
Performance, behavior, experiments and what to fix next, in the words you would use with a colleague.
Ask about performance
- Revenue, sessions and conversions
- Any metric, in plain English.
- Page performance
- Top pages by revenue, conversion rate, scroll depth and time on page.
- Comparisons
- Week over week, month over month, before and after a change.
- Device and channel splits
- Mobile against desktop, paid against organic, by country.
Analyze behavior
- Per-element revenue
- Which buttons and links drive revenue, not just clicks.
- Funnels
- Exactly where visitors drop out of checkout.
- User journeys
- Where visitors go next, and where they came from.
- Custom events
- Any interaction you have tagged.
Run experiments
- A/B test results
- Conversion rate, revenue per visitor and statistical significance.
- By device
- How each variant does on mobile and on desktop.
- Every test
- Every active and past experiment, by name.
Get CRO guidance
- Health checks
- A site audit, on demand.
- Prioritized recommendations
- What to test next, scored with ICE.
- Full CRO reports
- Structured and shareable, built from your live data.
One URL, every client.
The server is hosted, so there is nothing to download or run. Every client connects to the same address and signs in with your heatmap account. It takes about two minutes.
- A heatmap account
- Active, with at least one tracked site.
- An AI client
- Claude, Claude Code, Cursor, ChatGPT or Codex.
- The right AI plan
- Some clients need a paid plan to add a custom connector.
Server URL
https://mcp.heatmapcore.com/mcp
Choose your client
- Open Settings, then Connectors.
- Click Add custom connector.
- Name it Heatmap MCP and paste the server URL.
- Click Add, then Connect.
- Log in to heatmap and approve. You land back in Claude.
Needs a Claude plan with Connectors: Pro, Team or Enterprise.
To check it worked, ask your assistant “List my Heatmap sites.”
There’s no wrong way to ask.
Paste one of these into your assistant to start, then just talk to it. Context carries over, so a follow-up is one sentence.
- Be specific about dates
- “Last 30 days” or “June 2026”, not “recently”.
- Name the page
- “How is my checkout page doing?” beats “How are my pages doing?”
- Ask for a comparison
- “How did last month compare to the month before?”
- Ask for a report
- “Generate a complete CRO report” pulls it into one summary.
- What is my revenue per session for the last 30 days?
- Which pages have the highest conversion rate this month?
- Where are visitors dropping off in my checkout funnel?
- Which elements on my homepage are driving the most revenue?
- How did last week compare to the week before?
- What is my conversion rate on mobile vs desktop?
- What are my top exit pages this month?
- Summarize the results of my current split tests.
A thin, read-only bridge.
Your AI client hands the question to heatmap’s server, which fetches the answer from your account and hands it back. It never stores or changes your data.
1. Ask a question
In plain English, in the AI tool you have open.
2. AI picks the tool
It chooses the right one, so you never have to.
3. heatmap answers
Live from your account, never a nightly snapshot.
4. AI explains it
The real numbers, in words, ready for a follow-up.
- Read-only
- It can’t change your account or its settings.
- Scoped
- Only the sites you authorized when you connected.
- Per-user
- Everyone connects with their own heatmap login.
- Persistent
- It stays connected between sessions.
Questions, and quick fixes.
The usual hiccups and how to clear them. Still stuck? Book a demo and ask a person, or search the knowledge base.
Do I need to reconnect every session?
Does it work with Cursor and other AI tools?
What can it see? Is my data safe?
Do I need to know which tool to ask for?
Which plans include it?
Something isn’t working. What do I try?
- Can’t find your data. Ask “list my Heatmap sites” first. If none appear, re-authorize in your client’s connectors.
- Connector disconnected. Click Reconnect in the connectors panel and log in again.
- Not sent to heatmap to log in. Turn off pop-up blocking and try again.
- The wrong account’s data. Disconnect, reconnect, and log in with the right heatmap account.
- Results look out of date. Ask again with an exact date range.
