Skip to main content
Glama
plausible-mcp

plausible-mcp

by getsentry

Related Servers

Alternatives to plausible-mcp

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
      63 npm
      MIT
    • 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
    • F
      license
      B
      quality
      D
      maintenance
      A read-only stdio-based MCP server that provides tools to query Plausible Analytics data, including listing sites, fetching statistics with metrics/dimensions/filters, and getting realtime visitor counts.
      3
      -
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI tools that support the Model Context Protocol to query Plausible Analytics traffic and conversion data, break metrics down by page, source, country, device, and UTM parameters, and compare two date ranges side by side. All query tools are read-only and work with either a hosted bring-your-own-key endpoint or a local STDIO install.
      4
      42 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      MCP server for Yandex Metrica analytics: query web analytics metrics, goals, conversions, and raw API data using natural language from AI clients like Claude and Cursor.
      8
      708 npm
      4
      MIT

    TDQS

    A3.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a distinct analytics purpose: dimensional breakdown, conversion goals, time series, and period comparison. There is some conceptual overlap because conversions can be segmented and trended, but the descriptions make the intended boundaries clear.

    Naming Consistency5/5

    All tool names use snake_case verb_noun phrasing: get_breakdown, get_conversions, get_timeseries, and compare_periods. The get_/compare_ variation is still predictable and consistent with the action being performed.

    Tool Count5/5

    Four tools are well scoped for a focused analytics server, with each covering a meaningful query pattern. The compact surface avoids redundancy while still supporting the core reporting workflows.

    Completeness4/5

    The core analytics surface is covered: breakdowns, conversions, trends over time, and period comparisons. Minor gaps remain around site/property discovery or metadata, but the main analysis workflows are supported.

    Maintenance

    ActivityActive
    ResponsivenessOutdated data