plausible-whenever-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAUSIBLE_API_KEY | Yes | Your Plausible Stats API key. | |
| PLAUSIBLE_BASE_URL | No | Self-hosted instance URL. | https://plausible.io |
| PLAUSIBLE_TIMEZONE | No | IANA timezone (e.g. Europe/Berlin) for relative dates. | |
| PLAUSIBLE_DEFAULT_SITE_ID | No | Default site domain so you can omit site_id on every call. |
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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List all Plausible sites your API key can access, with their timezones. Note: the Sites API is often disabled on self-hosted Plausible — if so, this returns a note telling you to use the configured default site instead. It does NOT affect stats queries. |
| get_current_timeA | Get the current date in a site's timezone (today + yesterday as concrete dates). Useful for grounding before analyzing recent data, or to double-check what 'yesterday' resolves to. |
| get_realtime_visitorsA | Get the number of people currently on the site (last 5 minutes, real-time). |
| get_statsA | Get aggregate stats (single totals) for a site over a period — visitors, pageviews, bounce rate, visit duration, etc. Use for overview/summary questions like 'how did we do yesterday?'. |
| get_timeseriesA | Get traffic over time as a series of points (per hour, day, week or month). Use for trends, charts, and 'how did traffic change over the last N days'. |
| get_breakdownA | Break stats down by one or more dimensions — top pages, traffic sources, countries, devices, browsers, UTM tags, etc. Returns ranked rows. Use for 'top pages yesterday', 'where did traffic come from last week', and similar. |
| compare_periodsA | Compare aggregate metrics between two periods side by side, with absolute and % deltas. Great for 'yesterday vs the day before', 'this week vs last week', or before/after a deploy. Both periods accept the same friendly keywords as date_range. |
| queryA | Run a raw Plausible Stats API v2 query for anything the other tools don't cover (custom property breakdowns, multi-dimension + time series, comparisons, imports, behavioral filters). Friendly date keywords like 'yesterday' and 'last_week' ARE resolved here too (in the site's timezone), so you never need to know the date format. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 8 tools
Each tool targets a distinct analytics function: period comparison, dimension breakdown, current time, real-time visitors, aggregate stats, time series, site listing, and a raw query fallback. No overlapping purposes.
Most tools follow a clear 'verb_noun' pattern (get_stats, list_sites, compare_periods), but 'query' deviates by being a bare verb. This minor inconsistency is easily understood.
8 tools is well-scoped for a Plausible analytics client. It covers all common analytics queries without unnecessary bloat or gaps.
The tool set covers essential stats queries and includes a raw query tool for edge cases. Minor gaps like site management or event details exist but are outside the server's stated purpose.