Skip to main content
Glama
hyoon2007

mpulse-mcp

by hyoon2007
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to mpulse-mcp

No user-submitted related servers found.

    Related Servers

    • Umami MCP Server

      Mzaxd
      A
      license
      A
      quality
      D
      maintenance
      Read-only MCP server for Umami analytics. It talks to the Umami REST API directly over HTTP, supporting self-hosted and cloud setups.
      8
      6 npm
      MIT

    • crux-mcp

      miguelrisero
      A
      license
      A
      quality
      B
      maintenance
      MCP server for the Chrome UX Report, providing real-user Core Web Vitals (LCP, INP, CLS) and historical trends for any origin or URL via natural language queries.
      3
      2
      MIT

    • clarity-mcp

      Raffaele86
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Microsoft Clarity Data Export API, providing tools to retrieve traffic, popular pages, engagement metrics, and user behavior insights such as dead clicks, rage clicks, and script errors. Supports multiple projects with daily quota management and shared caching.
      MIT

    • clarity-mcp

      Biz2Gig
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to query Microsoft Clarity analytics data via a single HTTP endpoint, providing live insights, metric-specific tools, cached responses, quota tracking, and historical snapshots from a local database.
      1 npm
      MIT

    • telemetry-mcp

      selamy-labs
      A
      license
      Not graded
      quality
      A
      maintenance
      A read-only MCP server for querying telemetry data from configurable backends. Provides tools to list sources, describe schemas, run bounded queries, and compute aggregates.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.4/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct role: summary/histogram/time-series/metrics cover different data shapes, query is explicitly for uncovered query-types, and list_apps/list_query_types/describe_query are discovery aids. No two tools appear interchangeable.

    Naming Consistency5/5

    Tool names follow a predictable verb_noun pattern: get_* for data retrieval, list_* for enumeration, describe_* for details, and a single 'query' for generic access. The style is uniform and intuitive.

    Tool Count5/5

    Eight tools is well-scoped for an analytics server: four query-specific getters, one generic fallback, and three utility/metadata tools. Each tool earns its place without redundancy or bloat.

    Completeness5/5

    The server covers the core mPulse analytics surface (summary, histogram, time series) and provides a generic query tool for any undiscovered query-type, plus list/describe tools for self-discovery. No obvious gaps; agents can handle arbitrary query-types without dead ends.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources