Plausible's own API is one endpoint that takes a site, a metric list and a date range, so wrapping it as one tool is the honest shape rather than a shortcut — the flexibility is in the arguments. Because `PLAUSIBLE_API_URL` is configurable, the same server points at a self-hosted instance without a code change. Note that it reads: nothing here writes goals, sites or events.
An MCP server over the Plausible Analytics v2 API. It exposes Plausible's query endpoint as a single tool, so an assistant can pull visitor and pageview figures for a domain over a period without opening the dashboard.
- An analytics query against a site you own, taking the domain as `site_id`, a list of metrics such as visitors or pageviews, and a date range such as `7d` or `30d` — `plausible_query`
- All three arguments required, so a query is unambiguous about which site, which numbers and which period it is asking for
A Plausible account and an API key, supplied as `PLAUSIBLE_API_KEY` — the server refuses to start without it. `PLAUSIBLE_API_URL` points at the API and defaults to Plausible's hosted v2 endpoint, so set it if you run Plausible yourself. The npm package name is `plausible-model-context-protocol-server` (0.0.1); build from a clone and run `node dist/index.js`.
One command plus a key — npx -y github:AVIMBU/plausible-mcp-server, then supply credentials
