Microsoft Clarity

MCP Server for Microsoft Clarity

Category: Developer Tools
Primary Subcategory: Pending

Integration details

Description

This extension enables integration between AI systems and Microsoft Clarity, providing access to project analytics, documentation, and session recordings.

Integration type: Connector
Verification status: Verified connector
Platform: Claude
Category: Developer Tools
Primary Subcategory: Pending
Secondary Subcategories: None listed
Brand: Microsoft
Access: Unknown
First tracked: 2025-10-27
Tool count: 3
Geography: US

Claude Discoverability Score

Microsoft Clarity isn’t discoverable through Claude’s Connector picker

It runs as a local Claude Desktop Extension, so Claude cannot surface or score it there today.

No spam. Unsubscribe any time.

What the current score measures

Claude showing a list of relevant Connectors in a conversation

Remote Connectors Claude can surface from the Connector picker.

How this score is measured

Primary Subcategory

Competitive lineup

No Primary Subcategory assigned yetOnce Microsoft Clarity has a Primary Subcategory, the Plugins and Connectors it competes with will appear here with their scores.

Tools

3 tools agents can invoke

List Microsoft Clarity session recordings timeline information. Returns metadata including session link, duration, and a timeline of relevant user interactions.
Fetch Microsoft Clarity analytics data using a simplified natural language search query. The query should be focused on one specific data retrieval or aggregation task. Avoid complex multi-purpose queries. Time ranges should be explicitly specified when possible. If no time range is provided, prompt the user to specify one.
Fetch Microsoft Clarity documentation snippets for finding answers to user questions including step-by-step screenshots for setup guides, features, usage, troubleshooting, and integration instructions. The query should be focused on one specific documentation topic or question. Avoid complex multi-purpose queries.

Microsoft Clarity FAQ

How do I improve a Verified connector's discoverability?

The levers are the listing surface agents actually read: names, descriptions, keywords, tool metadata, and registry health. Which lever matters depends on where discovery breaks, which is what continuous measurement shows.

Where is this profile measured?

This profile uses the geography attached to the latest public registry snapshot: US. Locale tags are intentionally omitted.

Get alerts for Microsoft Clarity

Microsoft Clarity isn’t discoverable through Claude’s Connector picker

Competitive lineup

3 tools agents can invoke