clarity-mcp-multi
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CLARITY_TOKENS | No | JSON object mapping client name to Clarity Data Export token. | |
| CLARITY_TOKENS_FILE | No | Path to a file containing the same JSON as CLARITY_TOKENS. | |
| CLARITY_DEFAULT_CLIENT | No | Optional client name to use at startup. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| clarity_clientiA | Elenca i clienti Clarity configurati (solo nomi) e qual è quello attivo. Nessun token esposto. |
| clarity_usa_clienteA | Imposta il cliente Clarity attivo passando SOLO il nome: il server usa il token corrispondente dal registro (il token non passa dalla chat). Chiamalo prima di leggere i dati quando lavori su un cliente specifico. |
| query-analytics-dashboardA | 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. |
| list-session-recordingsA | List Microsoft Clarity session recordings based on specified filters. The filters allow you to narrow down the recordings by various criteria such as URLs, device types, browser, OS, country, city, and more. The date filter is required and must be in UTC ISO 8601 format. |
| query-documentation-resourcesA | Retrieve 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. |
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 5 tools
Each tool has a clearly distinct purpose: client management (list/set active) vs. data retrieval (session recordings, analytics queries, documentation). No overlap.
Tools are named in two languages (Italian and English) and use different conventions: clarity_clienti and clarity_usa_cliente use snake_case and Italian, while the others use hyphens and English. This inconsistency can confuse agents.
5 tools is a reasonable number for a Clarity-focused server, covering client selection, recordings, analytics, and documentation without being excessive.
Covers core workflows (client management, listing recordings, analytics queries, documentation) but lacks detailed session drill-down or export capabilities, which are notable gaps.