plausible-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAUSIBLE_API_KEY | Yes | Your Plausible API key (required for STDIO mode) | |
| PLAUSIBLE_BASE_URL | No | URL of your Plausible instance (for self-hosted) | https://plausible.io |
| PLAUSIBLE_DEFAULT_SITE_ID | No | Default site domain so you don't have to pass site_id 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 |
|---|---|
| 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 has a clearly distinct purpose: timeseries, breakdown by dimensions, conversions, and period comparison. There is no overlap or ambiguity about which tool to use for a given analytics query.
All tools follow a consistent verb_noun pattern, with 'get_' prefix for three tools and 'compare_' for the fourth, both using an action verb followed by a descriptive noun. This makes the tool surface predictable and easy to navigate.
With 4 tools, the server is well-scoped for an analytics metrics use case. It covers the primary needs without being bloated or sparse, fitting the typical 3-15 tool range.
The tool set covers time-series analysis, dimensional breakdowns, conversion tracking, and period-to-period comparisons, which together handle the core analytics workflows. There are no obvious dead ends or missing operations for the stated purpose.