Plausible MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PLAUSIBLE_API_KEY | Yes | Your Plausible Analytics API key | |
| PLAUSIBLE_API_URL | No | The URL of the Plausible Analytics 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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| plausible_queryC | Query analytics data from Plausible |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a distinct and clear purpose.
A single tool inherently has perfect naming consistency as there are no other tools to compare it against. The name 'plausible_query' follows a clear verb_noun pattern.
One tool is too few for a server intended to interact with an analytics platform like Plausible, which typically involves multiple operations such as fetching metrics, listing sites, or managing settings. This severely limits functionality.
The tool set is severely incomplete for a Plausible analytics server. It only provides querying capability, missing essential operations like listing sites, getting site details, managing goals, or accessing other analytics endpoints, which will cause significant agent failures.