Skip to main content
Glama
charpeni

Pirsch MCP Server

by charpeni

Related Servers

Alternatives to Pirsch MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      F
      maintenance
      MCP server for Plausible Analytics, enabling querying of traffic, conversions, sources, and device breakdowns from any MCP-compatible AI assistant.
      12
      25 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for Umami analytics, enabling natural language queries of website stats, traffic trends, events, sessions, and analytics reports.
      13
      10 npm
      1
      Elastic 2.0
    • A
      license
      A
      quality
      D
      maintenance
      MCP server that provides read access to Plausible Analytics data with natural-language date resolution, enabling users to query analytics like 'yesterday' or 'last week' without needing to know exact date formats.
      8
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Umami Analytics that provides read-only tools to query website stats, events, sessions, reports, and more, enabling natural language analytics queries.
      16 npm
      3
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Enables natural language analytics queries for Pirsch Analytics, providing comprehensive website traffic statistics, period comparisons, and trend analysis through an MCP interface.
      4
      44 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      Not graded
      maintenance
      An experimental MCP server that enables interaction with Google Analytics APIs, allowing users to retrieve account information, run core reports, and access realtime analytics data through natural language queries.
      Apache 2.0

    TDQS

    A4.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: get_domain returns the default, list_domains enumerates available domains, and query_statistics fetches analytics. No overlap or ambiguity exists.

    Naming Consistency5/5

    All tool names follow a consistent pattern of 'pirsch_' prefix plus a verb_noun structure (get, list, query). This makes the API predictable and easy to understand.

    Tool Count5/5

    Three tools is well-scoped for an analytics server: domain discovery, default selection, and statistics querying. Each tool is necessary and there is no bloat.

    Completeness5/5

    The tool surface fully covers the workflow of selecting a domain and querying comprehensive statistics (traffic, pages, events, etc.). No obvious missing operations or dead ends exist for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues