Skip to main content
Glama
Defilan

Plausible Analytics MCP Server

by Defilan

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PLAUSIBLE_API_KEYYesYour Plausible API key
PLAUSIBLE_BASE_URLNoBase URL for self-hosted instanceshttps://plausible.io

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
list-sitesA

List all sites you have access to in Plausible Analytics

get-current-visitorsA

Get the number of people currently on a site (real-time)

get-aggregate-statsA

Get aggregate stats for a site over a time period (visitors, pageviews, bounce rate, etc.). Use this for summary/overview questions.

get-timeseriesA

Get traffic trends over time. Returns data points broken down by time interval (day, week, or month). Use this for trend analysis and charts.

get-breakdownA

Break down stats by a dimension (e.g. page, source, country, device, browser, OS, UTM tags). Use this for 'top pages', 'traffic sources', 'visitor countries', etc.

queryA

Execute a raw Plausible Stats API v2 query. Use this for advanced queries that the other tools don't cover, such as custom property breakdowns, behavioral filters, or combining multiple dimensions with time series.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: aggregate overview, breakdown by dimension, real-time visitors, time series trends, site listing, and a raw query for advanced needs. No two tools are likely to be confused.

Naming Consistency4/5

Most tools follow a 'get-<resource>' pattern, but 'list-sites' deviates to 'list' and 'query' uses a bare verb. The pattern is readable and largely consistent, with minor exceptions.

Tool Count5/5

Six tools cover the core analytics query needs (aggregate, breakdown, timeseries, real-time, site listing, raw query) without bloat. The count is well-scoped for the domain.

Completeness4/5

The tool set covers the main analytics operations: summary, breakdown, trends, real-time, site list, and a raw query for custom requests. Missing explicit support for custom properties or goals, but the raw query compensates, so only minor gaps.

Maintenance

ActivityInactive
ResponsivenessNo issues