Connect Claude to Microsoft Clarity

Read session recordings, dashboard analytics, and behaviour insights for a Clarity project. Toolspoke puts 3 of its actions behind one MCP endpoint that Claude, Cursor, and Codex all speak.

Connect View pricing

Connection: Sandboxed MCP server
Authentication: Data Export API token
Actions exposed: 3
Cost per call (typical): 5 credits
Adapter: Maintained by Toolspoke

Connected in three steps

1
Install Microsoft Clarity
Open the marketplace in your workspace, add Microsoft Clarity to the project your agents work in, and it appears on the gateway immediately.
2
Connect the credential
Authenticate with data export api token. Where to get one, and what it has to be able to reach, is the next section.
3
Point your agent at the gateway
Give your client one address, https://toolspoke.com/mcp. Claude Code takes it as a command, Claude and Claude Desktop add it as a custom connector, and Cursor, Codex and VS Code each read it from a config file of their own.

.mcp.json

{
  "mcpServers": {
    "toolspoke": {
      "type": "http",
      "url": "https://toolspoke.com/mcp"
    }
  }
}

One block covers every tool you have installed. Microsoft Clarity shows up in the client as soon as your policy allows it, and so does everything else you install later.

Where the address goes, per client

Claude Code: Run it in your project, then /mcp to sign in
claude mcp add --transport http toolspoke https://toolspoke.com/mcp
Claude and Claude Desktop: Settings, then Connectors, then Add custom connector
https://toolspoke.com/mcp
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json for one project
{ "mcpServers": { "toolspoke": { "url": "https://toolspoke.com/mcp" } } }
Codex: ~/.codex/config.toml
[mcp_servers.toolspoke] url = "https://toolspoke.com/mcp"
VS Code: .vscode/mcp.json, or the MCP: Add Server command
{ "servers": { "toolspoke": { "type": "http", "url": "https://toolspoke.com/mcp" } } }

What Microsoft Clarity asks for

Data Export API token. You provide it once, when you install the connector. Toolspoke encrypts it at rest and decrypts it only for the length of a single call, and the gateway attaches it to the outbound request itself, so it is never part of the arguments an agent sends.

Data Export API tokenRequired: Clarity → Settings → Data Export → Generate new API token. Requires project admin. A token reaches only the project that issued it, so install this tool once per Clarity project.; eyJhbGciOi…

What Claude can do in Microsoft Clarity

3 actions, each one declared and named by the connector rather than discovered at runtime. A workspace policy grants a person all of them, a hand-picked selection, everything on the read side, everything on the write side, or none.

Reads: 3Reads
Writes: 0Writes
Destructive: 0Destructive

Reads

Fetches data and changes nothing.

query_analytics_dashboard
Ask for Clarity dashboard metrics in plain English and get the matching rows back. Handles traffic, popular pages, dead and rage clicks, script errors, scroll depth, engagement time, and breakdowns by browser, device, OS, country, source or URL. Ask one thing per call and always name the time range, for example 'dead clicks by URL over the last 3 days'. This reads the project the installed credential belongs to; it takes no project argument.
list_session_recordings
List session recordings with playback links, filtered by behaviour, device, geography or URL. Use this when you need to watch what a user actually did - dead clicks, rage clicks and quickbacks are only diagnosable from a recording. filters.date is required and is UTC ISO 8601.
query_documentation
Search Microsoft Clarity's own documentation for setup, feature, troubleshooting and integration guidance. Use it to answer how Clarity itself works rather than to read any project's data.

What it will not do

Enforced by the gateway rather than left to convention, which is why each of these can be stated flatly.

It cannot call anything else: The 3 actions above are the whole of it. A call to any other name is refused before it reaches Microsoft Clarity rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time.
It only reads: Every action here reads. Nothing this connector can do changes anything in Microsoft Clarity.
It reaches no further than your credential: Toolspoke holds no access to Microsoft Clarity of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either.
It never hears from Microsoft Clarity: Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Microsoft Clarity. An agent has to ask.
It does not smooth over provider limits: Toolspoke does not retry, queue or back off around Microsoft Clarity's own rate limits. A call that Microsoft Clarity refuses comes back to the agent as a failed call.

Before you connect it

What can Claude do in Microsoft Clarity?

3 named actions: 3 that only read. They include query_analytics_dashboard, list_session_recordings and query_documentation. Nothing outside that list is reachable: the connector declares each operation by name rather than proxying whatever an agent asks for.

What credentials does the Microsoft Clarity connector need?

Data Export API token. The connector asks for data export api token. Values are encrypted at rest and attached to the outbound request by the gateway, so they are never part of the arguments an agent sends and never reach the audit log.

Does the Microsoft Clarity connector work with Cursor and Codex, or only Claude?

Any client that speaks MCP, and every one of them gets the same 3 actions. There is a single address, https://toolspoke.com/mcp. Claude Code adds it with claude mcp add --transport http, Claude and Claude Desktop take it as a custom connector in settings, Cursor reads it from .cursor/mcp.json, Codex from ~/.codex/config.toml, and VS Code from .vscode/mcp.json. Each of them signs in to the gateway itself, so there is no key to paste.

What does the Microsoft Clarity connector not do?

The 3 actions above are the whole of it. A call to any other name is refused before it reaches Microsoft Clarity rather than forwarded on, and connecting your account does not add to the list: it is fixed by the connector, not discovered at run time. Every action here reads. Nothing this connector can do changes anything in Microsoft Clarity. Toolspoke holds no access to Microsoft Clarity of its own. Every call carries the credential you stored and nothing besides, so whatever that credential cannot reach, this connector cannot reach either. Nothing is pushed to it. There is no webhook, no subscription and no polling, so this connector cannot notice by itself that something changed in Microsoft Clarity. An agent has to ask. Toolspoke does not retry, queue or back off around Microsoft Clarity's own rate limits. A call that Microsoft Clarity refuses comes back to the agent as a failed call.

Can I limit which actions an agent can call?

Yes, in two places. The project switches Microsoft Clarity's actions on and off one at a time, for everyone in the project at once, and the screen groups them by read, write and destructive so turning off everything that deletes is one click. An individual agent key can then be narrowed further, to particular toolkits in a project and to particular actions in a toolkit. Whatever it was granted, a key never reaches a project its owner cannot.

What gets recorded when an agent calls Microsoft Clarity?

Every attempt, with the agent that made it and the person that agent belongs to, the full request payload, the response payload, the status, the duration, and the credits spent. Values whose key names a secret are masked out before the record is shown to anyone. An operation the connector marks as not retained never has its response body written at all, so the gateway keeps no second copy of what was read.

More analytics connectors

Browse all of them