.Microsoft Clarity MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DO_NOT_TRACK | No | Set to 1 to opt out of anonymous usage telemetry. | |
| CLARITY_API_TOKEN | Yes | Microsoft Clarity Data Export API token. Generate it in Microsoft Clarity under Settings -> Data Export -> Generate new API token. | |
| CLARITY_CACHE_TTL | No | Configurable TTL for the local response cache at ~/.clarity_mcp/cache.json. Default is 1 hour. | |
| CLARITY_TELEMETRY | No | Set to false to opt out of anonymous usage telemetry. | |
| DISABLE_TELEMETRY | No | Set to 1 to opt out of anonymous usage telemetry. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_ux_insightsA | Retrieve high-level UX insights, frustration rates, and technical health for a Clarity project. Args: project_id: Microsoft Clarity Project ID (e.g., 'yz5idaioq2'). num_of_days: Lookback window in days (1, 2, or 3 days; defaults to 3). token: Optional Clarity API token. If omitted, uses CLARITY_API_TOKEN environment variable. Returns: Structured JSON summary of session overview, rage clicks, dead clicks, quick backs, excessive scrolling, JS errors, and quota status. |
| get_frustration_breakdownA | Break down user frustration metrics (rage clicks, dead clicks, quick backs) across a specific dimension. Args: project_id: Microsoft Clarity Project ID. dimension: Breakdown dimension: 'URL', 'Device', 'Browser', 'OS', or 'Country/Region'. Defaults to 'URL'. num_of_days: Lookback window in days (1, 2, or 3; defaults to 3). token: Optional Clarity API token. Returns: Structured JSON ranking dimension values by user frustration severity. |
| get_js_errorsA | Analyze JavaScript errors and unhandled exceptions across browsers and operating systems. Args: project_id: Microsoft Clarity Project ID. num_of_days: Lookback window in days (1, 2, or 3; defaults to 3). token: Optional Clarity API token. Returns: Structured JSON breakdown of JavaScript script errors and error clicks by Browser and OS. |
| doctorB | Validate Microsoft Clarity credentials, project configurations, on-disk cache, and remaining daily request quota. |
| skills_listA | List available dynamic skill playbooks bundled with microsoft-clarity-mcp. |
| skill_readB | Load a dynamic skill playbook by name from GitHub (with local fallback). Args: name: Skill name (e.g., 'ux-triage', 'setup-clarity-token', 'frustration-audit'). |
| check_for_updatesA | Check PyPI for newer versions of microsoft-clarity-mcp and get upgrade instructions. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 7 tools
The three data tools overlap somewhat: get_ux_insights already surfaces rage clicks, dead clicks, quick backs, and JS errors that get_frustration_breakdown and get_js_errors cover in more depth. However, granularity distinguishes them (summary vs. dimension breakdown vs. focused error analysis), and the meta tools (doctor, skills_list, skill_read, check_for_updates) are clearly distinct.
Data tools follow a clean get_<noun> pattern (get_ux_insights, get_frustration_breakdown, get_js_errors), but the rest deviate: skills_list and skill_read use noun_verb, check_for_updates uses verb_for_noun, and doctor is a bare noun. Mixed conventions, though all still readable.
Seven tools is well-scoped for an analytics server: three domain tools for insights/frustration/errors plus four supporting utilities for auth, skills, and updates. Each tool earns its place with no redundancy in count.
Core workflows (overview insights, frustration breakdown, JS error analysis) are covered, along with credential validation and skill playbooks. Minor gaps exist—no raw session/heatmap retrieval, no multi-project or custom-range support beyond the 3-day window—but agents can work around these.