Skip to main content
Glama
friendlygeorge

plausible-mcp-server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to plausible-mcp-server

No user-submitted related servers found.

    Related Servers

    • plausible-mcp

      getsentry
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Plausible Analytics that enables querying traffic, conversions, and comparing time periods from any AI tool supporting MCP.
      4
      53 npm
      44
      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
      -

    • Pirsch MCP Server

      charpeni
      A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for the Pirsch Analytics API that lets users list domains and query traffic, pages, events, and other analytics metrics through conversational agents.
      3
      17 npm
      1
      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

    B3.4/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., realtime_visitors, list_sites, get_utm_stats). However, query_stats is a flexible endpoint that could overlap with specialized tools like get_breakdown or get_timeseries, potentially causing confusion.

    Naming Consistency3/5

    The majority use a get_* pattern, but query_stats and realtime_visitors deviate. The mix of verb-based and descriptive names is inconsistent but still readable.

    Tool Count5/5

    12 tools cover the Plausible analytics domain well—neither too few nor too many. Each tool serves a distinct purpose without redundancy.

    Completeness4/5

    The tool set covers all major analytics dimensions (traffic, sources, pages, devices, goals, UTM). A minor gap is the lack of site CRUD, but this server focuses on querying, not management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources