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. | |
| PLAUSIBLE_API_URL | No | The URL of the Plausible API. | https://plausible.io/api/v2 |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sitesA | List all sites in your Plausible account |
| get_breakdownA | Get detailed analytics breakdown for a site. COMMON QUERIES:
AVAILABLE METRICS:
AVAILABLE DIMENSIONS: Event dimensions (page/content related):
Visit dimensions (visitor/session related):
Time dimensions (for trends and patterns):
Note: Time dimensions are mutually exclusive - only one can be used at a time. When using time dimensions, results are automatically sorted chronologically. FILTERING EXAMPLES:
|
| analyze_pageC | Get detailed analytics for a specific page |
| get_trafficB | Get traffic analytics for a site using structured parameters |
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
analyze_page and list_sites are distinct, but get_breakdown and get_traffic both provide site analytics with unclear differentiation, causing potential for confusion.
All tools follow a consistent verb_noun pattern (e.g., analyze_page, get_breakdown), making naming predictable and clear.
4 tools is slightly thin for an analytics server; while it covers basic operations, two overlapping tools suggest the count could be reduced or expanded.
Core analytics queries are covered, but missing functionality like managing goals or real-time data means agents may encounter dead ends.