.Microsoft Clarity MCP Server
Related Servers
Alternatives to .Microsoft Clarity MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceEnables AI agents to access website analytics, including visitor sessions, UX friction, conversion funnels, and anomaly alerts.650 PyPIMIT

hootlens-mcpofficial
AlicenseNot gradedqualityBmaintenanceSession replay and click heatmaps for AI agents. Read a site’s visits as timed narratives, find repeated or dead clicks and the JavaScript errors behind them, and measure the impact of shipped changes.646 npm2MIT- FlicenseBqualityDmaintenanceEnables AI-powered analytics for OpenReplay user sessions through natural language queries. Supports session search, user journey analysis, error tracking, performance metrics, and funnel analysis to understand user behavior patterns.112-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to access recorded browser flows with user actions, network, console, storage, DOM events, and screen recording so they can debug, report bugs, perform regression testing, and generate Playwright tests without reproducing the issue.-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to analyze OpenReplay session recordings for user behavior patterns, problem detection, and actionable insights through session search, journey analysis, and AI-powered summaries.3MIT
- FlicenseNot gradedqualityAmaintenanceGives coding agents full browser context from recorded user flows, including actions, network, console, storage, DOM events, and screen recordings. Enables in-depth debugging, bug reporting, regression testing, and Playwright test generation without reproducing issues.-
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.