plausible-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SENTRY_DSN | No | Sentry DSN for the Worker's own telemetry (wrangler secret put SENTRY_DSN). Unset disables Sentry — use your own DSN if you want telemetry on a self-hosted deployment. | |
| CF_ACCESS_AUD | No | The Access application's Application Audience (AUD) tag — checked against the assertion's aud. | |
| PLAUSIBLE_API_KEY | No | Your Plausible API key (get one here). On the Worker this is the shared key for /internal; /mcp takes each user's own key via Bearer. | |
| PLAUSIBLE_BASE_URL | No | URL of your Plausible instance (for self-hosted) | https://plausible.io |
| ALLOWED_EMAIL_DOMAIN | No | Comma-separated email domain(s) allowed to sign in to /internal. Set to your own domain when self-hosting. | sentry.io |
| CF_ACCESS_TEAM_DOMAIN | No | https://<team>.cloudflareaccess.com — verifies the Cf-Access-Jwt-Assertion JWKS + issuer. No trailing slash. | |
| MCP_ALLOWED_HOSTNAMES | No | Comma-separated hostname allowlist used to validate MCP Host headers. | |
| PLAUSIBLE_DEFAULT_SITE_ID | No | Default site domain so you don't have to pass site_id every call | |
| MCP_ALLOWED_ORIGIN_HOSTNAMES | No | Comma-separated browser Origin hostnames allowed to call /internal. A present Origin is rejected when the list is empty. |
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 |
|---|---|
| get_timeseriesA | Get traffic and conversion metrics over time for a site or specific page. Use to spot trends and changes around deploys. |
| get_breakdownA | Break down metrics by a dimension: page, traffic source, country, device, etc. Use to find top pages, sources, or segment traffic. |
| get_conversionsA | Get goal conversion rates and counts. Can break down by page to see which pages drive conversions. |
| compare_periodsA | Compare metrics between two date ranges side by side. Ideal for before/after deploy analysis. Returns aggregate values for each period plus the delta (absolute and %). |
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 4 tools
Each tool targets a distinct analytics pattern: breakdown, conversions, period comparison, and time series. Minor overlap exists because get_conversions is a specialized breakdown, but the descriptions make the boundaries clear.
All tool names use consistent snake_case verb_noun structure (get_breakdown, get_conversions, compare_periods, get_timeseries). No mixed casing or vague verb styles.
Four tools map directly to core analytics query patterns and are well-scoped for the server's purpose. No redundant or bloat tools, and the set does not feel too thin.
The surface covers the main query dimensions (breakdown, timeseries, conversions, period comparison). Minor gaps remain: no single-period aggregate tool and no site-listing operation, though agents can work around these with known site IDs and compare_periods.