plausible-whenever-mcp
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.
README
plausible-whenever-mcp
The Plausible Analytics MCP server that finally understands "yesterday".
A local Model Context Protocol server that gives an AI assistant full read access to your Plausible data — and, crucially, resolves natural-language dates (yesterday, last week, last 30 days, 3 days ago…) in your site's own timezone. So prompts like "analyze yesterday's traffic" just work, even with small local LLMs.
Why this exists
The Plausible Stats API has presets like day, 7d and month, but no "yesterday" — and to query a specific past day you must send explicit YYYY-MM-DD dates. LLMs (especially smaller local models) routinely get this wrong because they don't reliably know today's date or your site's timezone. The result: "yesterday" silently returns the wrong range, or the model burns turns guessing date formats (/, .., YYYYMMDD, date vs date_range…) and gives up.
This server moves all of that to the server side. The model says date_range: "yesterday"; the server computes the exact dates in your site's timezone before calling Plausible. There is no tool where the model must know Plausible's native date format — and if it ever passes something unrecognizable, the error message lists exactly what's accepted.
Features
- 🗓️ Natural-language dates resolved in the site timezone — keywords, synonyms,
N days ago,last N days/weeks/months, single dates, and ranges with,../ortoseparators. - 🧰 8 tools covering the full read API: sites, realtime, aggregates, time series, breakdowns, period comparison, plus a raw query escape hatch — and all of them resolve friendly dates.
- 🏠 Self-hosted friendly — works against any Plausible instance via
PLAUSIBLE_BASE_URL, with aPLAUSIBLE_TIMEZONEoverride for instances where the Sites API (timezone auto-detect) is disabled. - 🤖 Tuned for local LLMs — forgiving inputs, self-explaining errors, and clean tool output (no HTML dumps).
- 🔒 Read-only — every tool only ever reads your analytics.
Tools
| Tool | What it does |
|---|---|
list_sites |
List sites your API key can access (with timezones). |
get_current_time |
Today + yesterday as concrete dates in a site's timezone. |
get_realtime_visitors |
People on the site right now. |
get_stats |
Aggregate totals for a period (visitors, pageviews, bounce rate…). |
get_timeseries |
Traffic over time (hour/day/week/month) for trends and charts. |
get_breakdown |
Top pages, sources, countries, devices, browsers, UTM tags… |
compare_periods |
Two periods side by side with absolute + % deltas. |
query |
Raw Stats API v2 escape hatch for anything else. |
Date expressions accepted everywhere
- Keywords (resolved in the site timezone):
today,yesterday,this_week,last_week,this_month,last_month,this_year,last_year,last_7_days,last_30_days,last_90_days,last_12_months - Natural phrasing & synonyms:
3 days ago,day before yesterday,last 14 days,last 6 months,previous month,the last week,ytd,mtd,all time, … - Plausible presets:
day,7d,30d,month,6mo,12mo,year,all - A single date:
2024-03-15→ that one day - An explicit range (any separator):
2024-01-01,2024-01-31,2024-01-01..2024-01-31,2024-01-01/2024-01-31,2024-01-01 to 2024-01-31
Install
Requires Node.js ≥ 18 and a Plausible Stats API key (Plausible dashboard → Settings → API Keys; on self-hosted: <your-instance>/settings/api-keys).
git clone https://github.com/Schneckenhausmann/plausible-whenever-mcp.git
cd plausible-whenever-mcp
npm install
npm run build
Configure
Set environment variables (see .env.example):
| Variable | Required | Description |
|---|---|---|
PLAUSIBLE_API_KEY |
Yes | Your Plausible Stats API key. |
PLAUSIBLE_BASE_URL |
No | Self-hosted instance URL (default https://plausible.io). |
PLAUSIBLE_DEFAULT_SITE_ID |
No | Default site domain so you can omit site_id on every call. |
PLAUSIBLE_TIMEZONE |
No | IANA timezone (e.g. Europe/Berlin) for relative dates. Recommended on self-hosted instances where the Sites API is disabled (otherwise falls back to UTC). |
Connect to Claude Desktop
~/Library/Application Support/Claude/claude_desktop_config.json:
{
"mcpServers": {
"plausible": {
"command": "node",
"args": ["/absolute/path/to/plausible-whenever-mcp/dist/index.js"],
"env": {
"PLAUSIBLE_API_KEY": "your-key",
"PLAUSIBLE_DEFAULT_SITE_ID": "example.com"
}
}
}
}
For a self-hosted instance, add PLAUSIBLE_BASE_URL and PLAUSIBLE_TIMEZONE:
{
"mcpServers": {
"plausible": {
"command": "node",
"args": ["/absolute/path/to/plausible-whenever-mcp/dist/index.js"],
"env": {
"PLAUSIBLE_API_KEY": "your-key",
"PLAUSIBLE_BASE_URL": "https://analytics.example.com",
"PLAUSIBLE_DEFAULT_SITE_ID": "example.com",
"PLAUSIBLE_TIMEZONE": "Europe/Berlin"
}
}
}
}
Connect to Claude Code
claude mcp add plausible \
--env PLAUSIBLE_API_KEY=your-key \
--env PLAUSIBLE_DEFAULT_SITE_ID=example.com \
-- node /absolute/path/to/plausible-whenever-mcp/dist/index.js
Example prompts that just work
- "Look at yesterday's data for example.com and analyze it."
- "Top 10 pages last week vs the week before."
- "Show the hourly visitor trend for yesterday — we had a spike in the morning."
- "Which countries drove the most traffic last month?"
Self-hosted note
On Plausible Community Edition the Sites API (/api/v1/sites) is often disabled, so:
list_siteswill reportsites_api_available: falseand point at your configured default — this is expected and does not affect any stats queries.- Timezones can't be auto-detected, so set
PLAUSIBLE_TIMEZONEto keep relative dates correct.
Develop
npm run build # compile TypeScript -> dist/
npm run dev # tsc --watch
npm test # build + run the date-resolver test suite
npm run inspector # open the MCP Inspector against the server
Acknowledgments
Built fresh, but inspired by two excellent MIT-licensed projects — thank you to their authors:
- Defilan/plausible-mcp by Defilan — clean stdio tool surface.
- getsentry/plausible-mcp by Sergiy Dybskiy — per-tool architecture and the period-comparison idea.
Full third-party license notices are in CREDITS.md.
License
MIT © 2026 Nikias Herzhauser
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.