Skip to main content
Glama
.Microsoft Clarity MCP Server

.Microsoft Clarity MCP Server

by surendranb

Related Servers

Alternatives to .Microsoft Clarity MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Session 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.
      977 npm
      2
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Enables 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.
      11
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding agents to retrieve real-user performance metrics and 28-day field trends, run Lighthouse lab audits, and access remediation playbooks for LCP, INP, and CLS.
      7
      47 PyPI
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      -

    TDQS

    A3.5/5.0

    Scored across 7 tools

    Disambiguation4/5

    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.

    Naming Consistency3/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues