plausible-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAUSIBLE_API_KEY | Yes | Your Plausible API key | |
| PLAUSIBLE_API_BASE | No | API base URL (change for self-hosted) | https://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
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_statsB | Query Plausible analytics with full flexibility — metrics, dimensions, filters, date ranges. The main stats endpoint. |
| realtime_visitorsA | Get the current number of real-time visitors on a site. |
| get_breakdownB | Get a breakdown of visitors by a specific dimension (top sources, pages, countries, browsers, etc.). |
| get_timeseriesC | Get time-series data for one or more metrics — daily, hourly, weekly, or monthly intervals. |
| list_sitesB | List all sites in your Plausible account. |
| get_siteB | Get detailed information about a specific site. |
| get_custom_eventsB | Get custom event breakdown — see which events fire most, conversion rates, and revenue. |
| get_entry_pagesB | Get top entry pages — where visitors land on your site. |
| get_exit_pagesB | Get top exit pages — where visitors leave your site. |
| get_utm_statsB | Get UTM campaign, source, and medium breakdowns — see which campaigns drive traffic. |
| get_device_statsC | Get breakdown by device type, browser, OS, and screen size. |
| get_goalsC | Get conversion stats for all configured goals on a site. |
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 12 tools
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.
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.
12 tools cover the Plausible analytics domain well—neither too few nor too many. Each tool serves a distinct purpose without redundancy.
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.