Connect Claude (MCP)

Ask Claude about your traffic, sessions, heatmaps and funnels, and let it manage your goals, ad pixels and conversions, with your own Klickbee permissions.

Klickbee Tracking has an MCP server. Once you connect it, Claude (claude.ai, Claude Desktop or Claude Code) can answer questions about your analytics in plain language: traffic, sessions, heatmaps, funnels, frustration signals, who is on your site right now. It can also create and change your goals, ad pixels and conversions for you. You connect with your own Klickbee account: Claude sees only the sites you are a member of, with the permissions you have on each.

The server address is:

https://tracking.klickbee.com/api/mcp

Pro sites only, and changes are logged

Claude can read and change Pro sites. On a Free site, or on a suspended site, it is refused with an explanation (the only exception is the list of your sites, which works on any plan). Changes are limited to owners and admins: a viewer can ask questions but cannot change anything. The changes made through your connection are logged, and the most recent ones are listed in Settings → Connections.

Connect

You find the address and the command below in the app, under Settings → Connections, in the Connect an assistant card.

From claude.ai or Claude Desktop

In Claude's settings, add a custom connector (the exact menu names depend on your Claude app and version).
Paste the URL https://tracking.klickbee.com/api/mcp.
Claude sends you to Klickbee. Sign in if you are not already.
On the authorization screen, check what the app is asking for and click Authorize.

The Klickbee connector then shows up in Claude with its tools. One connection covers every site you are a member of.

From Claude Code

claude mcp add --transport http klickbee https://tracking.klickbee.com/api/mcp

Then run /mcp in Claude Code to finish the connection (same sign-in page and authorization screen).

The authorization screen

When an app asks for access, Klickbee shows an authorization screen titled with the app's name followed by "wants access". It appears every time an app asks to be authorized, never silently skipped. It tells you what the app will be able to do:

list all your sites with their plan and status;
read analytics, sessions, heatmaps and live visitors on your Pro sites;
create, change and delete goals, ad pixels (Meta, Google Ads, LinkedIn) and conversions on sites where you are an owner or an admin.

It also states what the app cannot do: add custom code to your site, see sites you are not a member of, or change billing or team settings.

Only authorize an app you started yourself

The app name on this screen is supplied by the app itself, and Klickbee has not verified it. Check the destination shown under "Authorization will be sent to", and click Deny if you do not recognise it or did not just start the connection yourself.

What you can ask

Claude chains the tools by itself: it lists your sites, picks the right one, then runs the queries it needs. A few examples to adapt:

Questions

"Is the tracker installed on my site, and when did data last arrive?"
"How many visitors and sessions did we get in the last 30 days, and where did they come from?"
"Which pages have the most rage clicks or dead clicks?"
"Show me the sessions from mobile visitors that hit a frustration signal this week."
"Build a funnel from /pricing to the signup event and tell me where people drop off."
"Compare /landing-a and /landing-b for the 'Booked a call' goal."
"Where do visitors stop scrolling on /pricing?"
"Who is on the site right now, and from which countries?"

Changes (owners and admins)

"Create a goal for the /thank-you page."
"Create a goal for the signup_completed event and send it to Meta as a Lead."
"List my pixels and disable the LinkedIn one."
"Add a Meta pixel with this id: ..."

What Claude can read

You can name sites by their name; Claude finds the right one. Time ranges are 24 hours, 7 days, 30 days or 90 days (7 days by default).

Theme	What Claude can get
Your sites	The list of your sites with their plan and status, and, for a given site, a health check: is the tag installed, when did the last event arrive, is the SDK up to date. Handy for "why do I have no data?".
Traffic	Overview (pageviews, events, sessions, visitors, trend, top pages and events), acquisition (channels, sources, mediums, campaigns, terms, social networks) and the top pages.
Visitors and sessions	A filterable list of sessions (channel, country, device, frustration, duration, pages viewed, viewed page) and the detail of one session: journey, event timeline, location, device and frustration. Live visitors on the site right now.
Behavior	Click heatmaps and scroll/attention bands for a page, and frustration totals (rage clicks, dead clicks, quick backs, error clicks, rage scrolls).
Insights	Funnels (pageview or event steps), navigation paths, retention cohorts, and the comparison of two landing pages, optionally against a goal.
Your setup	Your goals, your ad pixels and your conversion mappings.

For the same questions in the dashboard, see Dashboard tour, Sessions and heatmaps and Funnels, paths and retention.

What Claude can change

Changes are limited to three things, on sites where you are an owner or an admin:

What	What Claude can do
Goals	Create, update (name, rule, description) and delete goals. It refuses to create a second goal with the same type and rule. A pageview goal needs a path starting with `/`.
Ad pixels	Create Meta, Google Ads and LinkedIn pixels (the identifier is checked), rename them, switch them on or off, change their identifier and delete them. A new pixel starts loading on the next page view.
Conversions	Send a goal to a pixel as a conversion (with optional value and currency), and stop sending it.

Two consequences to keep in mind:

Deleting a goal or a pixel also deletes its conversion mappings. It cannot be undone. Your recorded events are kept.
Changing a goal's rule changes past numbers too, because goal completions are recomputed from stored events.

Custom code pixels stay in the dashboard

Claude cannot create, change or delete a custom code pixel, and it cannot see the code. This is deliberate: custom code runs on your visitors' pages. Add and edit those from Optimize → Pixels yourself. Custom pixels appear in the list Claude reads, without their code.

A Google Ads conversion created from Claude is sent from Klickbee's servers, so it only takes effect once you have connected Google Ads on the Pixels page. See Conversions.

What Claude cannot do

Change billing or plans, manage your team or invitations, create, rename or delete a site, rotate its public key, or edit its allowed origins.
Connect or disconnect your Meta or Google Ads accounts.
Touch experiments or saved funnels, generate AI summaries, play back a session replay (it only gets the replay's id), or change the install snippet.
See a site you are not a member of, or read a Free or suspended site.

Roles, plans and suspended sites

Situation	What happens
Free site	Claude can list it, but any other request is refused with "MCP access is a Pro feature for this site", with a link to upgrade.
Suspended site	Refused with "This site is suspended", with a link to Settings → Billing. See Billing.
You are a viewer	Claude can read everything on that site, but every change is refused: ask an owner or admin of the site to make the change or to change your role. See Invite your team.
You are an owner or admin	Claude can read and make the changes above.
Site you are not a member of	Same answer as an unknown site: "Project not found or not accessible".

Connecting itself does not need Pro: the plan is checked on each request, so a Free user can connect and get an explanation rather than an error at sign-in.

Limits

Claude may hit these on large sites. When it does, the answer says what was cut or tells it to wait, and Claude usually explains it to you. The rate limits below are the current default settings.

Heavy queries are limited per account: funnels, paths, retention, page comparisons and the heatmap of a given page share a budget of 20 per minute, and at most 2 can run at the same time (a live-visitors query also takes one of those 2 places while it runs). If Claude asks too much at once, it is told to wait a minute and to run them one at a time.
Overall request rate: about 300 requests per minute per user. Past that, requests are refused for a short while before they are accepted again.
Lists are capped. By default a list returns up to 50 rows and at most 200. Session lists return at most 100 per page. Page lists cover at most 100 pages. The heatmap keeps the densest 200 cells of a page and lists at most 50 pages. A funnel takes 1 to 10 steps. Live visitors look at a window of 1 to 60 minutes, and list at most 50 visitors.
Cut results are flagged. When a result is truncated, Claude is told so, and whether the total is only a lower bound. Ask for a shorter time range or a narrower filter to get complete numbers.
Scroll and attention heatmaps cover all devices. Only click heatmaps can be filtered by desktop or mobile.
Goal lists show each goal's rule and mappings, not its completions. For a count, Claude compares pages against the goal or builds a funnel.

These values may change over time as Klickbee evolves.

Settings → Connections

Open Settings → Connections to see and control what your assistants did.

Connected apps: each app you authorized, with its name, an Active or Expired badge, where it sends you back to, the date it was first authorized and the date it last received a token. Click Revoke to cut an app off. It stops working at its next request; to use it again you connect it and approve it again.
Recent changes through MCP: the changes made through your own connections (not your teammates'), with the time (UTC), the site, the action, what it targeted and the result: Done, or Refused with the reason. It lists your 20 most recent entries and covers changes only, not questions. A change refused because the goal or pixel was not found, or already exists, is listed. A request refused because of the site's plan or your role (for example a viewer) is not listed: Claude simply tells you why. The log is kept 180 days.

To be sure an app has no access any more, revoke it here, even if you also removed the connector in Claude's own settings.

Staying signed in

Claude renews its access automatically in the background. After a long period without use (about a week), you may be asked to sign in and authorize again.

If something goes wrong

"MCP access is a Pro feature for this site": the site is on the Free plan. Upgrade it in Settings → Billing.
"This site is suspended": the site's subscription is not active. Reactivate it in Settings → Billing.
"Your role on this site is viewer (read-only)": you can ask questions but not change anything on this site. Ask an owner or admin.
"Project not found or not accessible": the site does not exist, or you are not a member of it. Ask Claude to list your sites.
"Heavy queries … are limited to 20 per minute" or "Another heavy query is still running": wait a minute and ask for one analysis at a time.
Claude answers "no data": ask it to check the site's health. See Troubleshooting.
The connector will not connect: check that the URL is exactly https://tracking.klickbee.com/api/mcp and that you are signed in to Klickbee with the right account.
A tool is missing or an app looks stuck: revoke the app under Settings → Connections and connect it again.

Still stuck? Contact us.

On this page