Claude Microsoft Clarity connectorWhat Claude can do in your Microsoft Clarity account.
The Claude Microsoft Clarity connector exposes 3 tools: 3 read, 0 write, 0 undocumented. It is a desktop extension, not a web connector. Below: what Claude reads in your Clarity project, the token it needs, and where Microsoft's own files disagree.
Verified Trustpilot reviews · AI, automation & growth agency
What changes for your website analytics
Instead of clicking through Clarity's dashboard filters, you ask Claude a question in plain English about your site. It queries your Clarity project, pulls the numbers or the list of recordings that match, and answers in the chat. For a marketer who opens Clarity twice a month, that removes the hunt for the right screen.
Get a traffic answer without building a filter. The weekly report needs sessions by country for the last three days. query-analytics-data takes the question in natural language and returns the figures from your project's analytics.
Go straight to the sessions that matter. A checkout bug was reported on mobile. list-session-recordings returns the recordings timeline with a link to each session, its duration and the key interactions, so you pick the sessions worth watching.
Settle a how-to question on the spot. Someone asks how custom events work. query-documentation-data fetches snippets from Clarity's own documentation, screenshots included, without leaving the conversation.
What the directory sheet does not tell you: this is an extension that runs in Claude Desktop only, and it needs an API token you generate in your Clarity project. By default the sheet only exposes reading, which is a floor observed on a public page, not a guarantee. Clarity works best with one focused question at a time and a stated date range. Nothing runs on its own either: no tool reacts when traffic drops. For alerts on a schedule, that is an automation tool's job; the Integrations hub covers that side.
The vocabulary in one minute
Five words you will meet while setting up Clarity.
- Connector
- The link you set up once between Claude and an account you already have, so Claude can work in it while it answers you.
- Desktop extension
- A connector installed on your own computer inside Claude Desktop, rather than reached over the web from any Claude app.
- Tool
- One named thing a connector lets Claude do. Claude picks the ones it needs on its own; the directory lists them by name.
- Approval
- The confirmation Claude waits for before it goes ahead with an action, shown in the conversation at the moment it matters.
- MCP
- The shared standard connectors are built on: it is what lets an assistant like Claude talk to an outside service.
Set up Clarity in Claude Desktop in three steps
- 01
Open the extensions in Claude Desktop
This connector installs on your computer, so it lives in Claude Desktop and not in the web app. Microsoft's instructions go through File, then Settings, then Extensions, where you search for Microsoft Clarity.
- 02
Install the extension
Click Install on the Microsoft Clarity entry. There is no sign-in window at this point: a desktop extension does not open the service's login page the way a web connector does.
- 03
Paste your Clarity API token
Configure the extension with an API token from your Clarity project. That token decides which project Claude reads, and until it is in place the extension has no Clarity data to work with.
The 3 Clarity tools, grouped by what they do
Microsoft Clarity gives Claude 3 tools: 3 that read your account, 0 that change something in it.
All three read. Names below are the ones the directory sheet and the extension manifest use; Microsoft's README shows two of them under other names.
- 3 read
What Claude reads (3)
3 toolsThree tools that look at your Clarity project and its documentation without changing anything.
list-session-recordings
Returns the timeline of your project's session recordings: a link to each session, how long it lasted, and the notable user interactions inside it. Filters narrow it by page URL, device, browser, OS, country or city.
query-documentation-data
Pulls snippets from Microsoft Clarity's documentation to answer a question about setup, features, usage, troubleshooting or integrations, with step-by-step screenshots when they exist.
query-analytics-data
Answers a plain-language question with data from your Clarity project, such as traffic figures, browsers used or behaviour metrics, by running one retrieval or aggregation.
What Claude asks you before acting
By default, Claude stops and asks for your go-ahead before each action it takes on an account for you. No source describes a Clarity-specific confirmation, so that general rule is the one that applies here.
On a Team or Enterprise workspace, owners decide whether a member may let some actions through without being asked each time, and they can restrict what a connector may do for the whole organization, for example keeping reads open and closing anything else. That setting binds everyone, and nobody works around it from their own account. The token you paste also sets a hard edge: Claude reads the Clarity project that token opens, and nothing beyond it.
Which plans this is available on
Out of 819 directory sheets, not one shows availability by plan. The connector-by-connector answer is published nowhere: it is a real gap in the catalogue.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, while desktop extensions like this one install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner turns a connector on for the organization first. For this extension's current state, check its sheet in the official directory.
Where this connector stops
A connector is not an automation. Claude calls these tools while it answers you: nothing fires when your bounce rate jumps or a new recording lands.
Everything known here comes from Microsoft's GitHub repository and the directory sheet; Claude's help centre has no page on Clarity. The tool list is an observed floor, not a promise, and the verification badge is not a security audit: Anthropic states on every sheet that it does not choose the tools a publisher exposes, nor guarantee they behave as announced. For a connector that can also write, see the Claude airtable connector.
Under which names does Claude see the Clarity tools?
- Extension manifest in Microsoft's GitHub repository, matching the directory sheet ↗February 2026The extension declares list-session-recordings, query-documentation-data and query-analytics-data.
- README and server code of the same repository ↗February 2026The README and code name the analytics and documentation tools query-analytics-dashboard and query-documentation-resources.
What this page followsBoth come from Microsoft and describe the same three jobs; only two names differ. This page follows the manifest, because it matches the directory sheet. Check the tool list shown in the extension's settings on your own Claude Desktop.
Need help connecting Microsoft Clarity to Claude?
A person reads every message.
