Grafana MCP server
A Model Context Protocol server that gives AI clients access to a Grafana instance's dashboards, datasources, alerting and incidents.
Tested on LinuxKnown vulnerabilities
Use it
Before you install: known vulnerabilities
pickfit found 1 known high or critical vulnerability in the packages a fresh install brings (OSV.dev, 16 Nov 2026). Weigh this before you install it.
npm:zod 4.6.5Zod can exhaust memory while validating oversized constrained collections (GHSA-mrhx-c7xc-m3w5, high, fixed in 4.6.6)
Linux x86_64
You need first
- Runtimes:
uv - Needs the network
- Keys or accounts: Grafana service account token
uv tool install mcp-grafana
uv tool install mcp-grafana
Check that it works
mcp-grafana --versionThe output should contain “v2.2.0”.
Add it to your agent
claude mcp add mcp-grafana -- mcp-grafanaJSON for Claude Desktop, Cursor and other clients
{
"mcpServers": {
"mcp-grafana": {
"command": "mcp-grafana",
"args": []
}
}
}Add mcp-grafana as an MCP server in your AI client, with your Grafana URL and credentials set, and the client will list its Grafana tools.
What it does
- Search, read and update Grafana dashboardsNot tested
- Query Prometheus and Loki datasourcesNot tested
- List and manage alert rulesNot tested
- Manage incidents and OnCall schedulesNot tested
How far pickfit got
Linux x86_64
- Installs
- Connects
- 0 of 4 features work
- Works offline
Good for
- search Grafana dashboards by title, folder or tag
- run PromQL queries against Prometheus datasources
- query Loki logs with LogQL
- manage incidents in Grafana Incident
- render a dashboard panel as a PNG image
How pickfit tested it
Each run starts from a clean machine and follows the steps above. How pickfit verifies
Linux x86_64
An MCP client called one of its tools
- Replayed from scratch
- Works offline
- Checked on 15 Nov 2026
- Version v2.2.0
An MCP client handshake over stdio listed 80 tools, and a call to suggest_loki_alloy_label_config returned a result.
Differences the test machine hit
- README: Set GRAFANA_URL and GRAFANA_SERVICE_ACCOUNT_TOKEN in the MCP client config
In the test: The server starts and lists its 80 tools without them; only the tools that talk to Grafana need a running Grafana instance and a token