Plausible MCP Server
# Plausible Model Context Protocol Server
MCP Interaction Server for Plausible Analytics
A Model Context Protocol (MCP) server implementation for interacting with the Plausible Analytics API. This server allows AI models to query analytics data from Plausible.
## Local Development
In order to run this client locally, add the following configuration to your Claude Desktop MCP Server config file:
```
{
"mcpServers": {
"mcp-plausible-local": {
"command": "node",
"args": ["/path/to/project/dist/index.js"], <---- replace this with your project path
"env": {
"PLAUSIBLE_API_URL": "https://plausible.io/api/v2",
"PLAUSIBLE_API_KEY": "test_api_key"
}
},
}
}
```
After this, you should be able to test this implementation in your Claude Desktop App using example prompts like:
- "Can you provide a daily overview of my analytics for avimbu.com?"
- "Can you generate relevant analytics reports from my Plausible account for the domain avimbu.com?"
Running the server locally:
```
node dist/index.js
```
With the build in another terminal
```
npm run watch
```
## Contact
If you have questions, feel free to contact us via [AVIMBU](https://avimbu.com).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.