GA4 tells you a landing page converts badly. It doesn't tell you that visitors are hammering a pricing toggle that doesn't respond, or bouncing back to the ad within seconds. Microsoft Clarity does. Clarity is now a live MCP integration in Cogny, so the agent that audits your funnel can also see where people struggle on the page.

One token, no OAuth app to approve.

TL;DR

Microsoft Clarity is live now. Connect it from Settings → Cogny Managed MCPs with a Data Export token.
What the agent can read: traffic (sessions, bot sessions, pages per session), engagement time, scroll depth, popular pages, referrers, and the friction signals: rage clicks, dead clicks, quickbacks, excessive scrolling, script errors and error clicks.
Broken down by up to 3 of: Browser, Device, Country/Region, OS, Source, Medium, Campaign, Channel, URL.
3 read-only tools: get_live_insights, get_insights_history, get_api_quota.
Clarity's API limits apply: the last 1–3 days, 10 requests per project per day, 1,000 rows per metric. Cogny stores every answer, so repeat questions within 6 hours cost no request, and the stored snapshots give you history past Clarity's 3-day window.
New report: UX Friction Signals (Microsoft Clarity) — finds the pages where visitors struggle and names a concrete fix for each.
Available on any paid Cogny plan (Solo $9/mo and above).

What you can ask

Tool	What it does
`get_live_insights`	Clarity's dashboard metrics for the last 24, 48 or 72 hours, optionally split by up to 3 dimensions. Filter to the metrics you care about and how many rows per metric.
`get_insights_history`	Every snapshot Cogny has stored for your project, newest first — trends beyond 3 days. Never spends a Clarity request.
`get_api_quota`	How many of today's 10 requests are left, and which breakdowns are already stored and free to re-read.

In practice: "Which pages had the most rage clicks in the last 3 days?" "Is the dead-click rate on mobile worse than on desktop?" "Which channel sends traffic that quickbacks the most — and which ads are behind it?" With Google Ads or Meta Ads connected too, the agent can tie a quickback-heavy landing page back to the campaigns sending the traffic.

Making 10 requests a day go further

Clarity's public API allows 10 requests per project per day and only covers the last 1–3 days. Cogny is built around that:

Every answer is stored. Asking the same breakdown again within 6 hours is answered from the stored copy, with its age shown. Asking for more rows or a different metric from a stored breakdown is free too.
The quota is counted for you. When today's requests are spent, the agent gets the newest stored answer for that breakdown, clearly marked with when it was fetched, instead of an error.
History accumulates. Clarity forgets after 3 days; your stored snapshots don't. Run the UX Friction report every few days and week-over-week comparisons become possible.

Requests made with the same token outside Cogny count against the same daily limit, so give Cogny its own token if other tools use the API.

The UX Friction Signals report

Enable UX Friction Signals (Microsoft Clarity) from the Reports page. Each run:

Pulls project totals and a per-page breakdown, then splits by device and by channel — at most 4 requests, reusing anything already stored.
Flags pages where rage clicks, dead clicks, quickbacks or error clicks run at 2× the site-wide rate or more (minimum 30 sessions), and any friction above average on pricing, signup, checkout or contact pages.
Opens each flagged page and names the probable cause — a button-styled element that isn't clickable, a slow control, a page that doesn't match the ad's promise — or says the cause isn't visible from the page.
Ranks fixes by sessions affected and page value, at most six.

The Landing Page & Conversion Funnel report also uses Clarity when it's connected, to explain why a page it flagged leaks.

What it can't do

No heatmaps or session recordings. Clarity's API doesn't expose them. When a finding needs a recording, the agent tells you which page to open in Clarity.
One project per token. Clarity tokens are per project; connect the project for the site you care about.
Read-only. Nothing in your Clarity project can be changed through Cogny.

How to connect it

In Microsoft Clarity, open your project and go to Settings → Data Export → Generate new API token. You need to be a project admin.
Name the token (4–32 characters, letters, numbers, -, _ or .), e.g. Cogny, and copy it.
In Cogny, go to Settings → Cogny Managed MCPs, click Connect on Microsoft Clarity, and paste the token.

Then ask your agent where visitors are struggling, or turn on the report and let it check every few days. Connect Clarity from your Cogny dashboard.