Skip to main content
Glama
getsentry

plausible-mcp

by getsentry
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to plausible-mcp

No user-submitted related servers found.

    Related Servers

    • plausible-mcp-server

      friendlygeorge
      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
      38 npm
      MIT

    • plausible-whenever-mcp

      Schneckenhausmann
      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

    • Plausible Analytics MCP Server

      AryanKo
      F
      license
      B
      quality
      C
      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
      -

    • plausible-mcp

      michldav
      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
      53 npm
      MIT

    • Yandex Metrica MCP

      askads
      A
      license
      A
      quality
      A
      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
      103 npm
      4
      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

    A3.7/5.0

    Scored across 4 tools

    Disambiguation4/5

    The four tools have largely distinct purposes: time series trends, dimension breakdowns, goal conversions, and period comparisons. However, get_conversions can break down by page, which overlaps slightly with get_breakdown, though descriptions clarify the focus on goals.

    Naming Consistency5/5

    All tool names follow a clear verb_noun pattern in snake_case: get_timeseries, get_breakdown, get_conversions, compare_periods. Minor deviation in verb (get_ vs compare_) is appropriate and predictable.

    Tool Count4/5

    Four tools are well within the typical 3-15 range and each covers a distinct analytical need. It is slightly thin for a full analytics surface (e.g., no site listing or realtime), but not problematic for a focused metrics server.

    Completeness3/5

    Core analytical queries are covered, but there are notable gaps such as listing available sites, retrieving site metadata, or accessing realtime/current visitors. For a read-only analytics server, these omissions could force agents to work around missing context.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources