Grafana MCP Server
Vendor-official Grafana MCP server from Grafana Labs. Covers dashboards (search, get, summary, JSONPath extraction, patch), datasources (Prometheus, Loki, ClickHouse, CloudWatch, Elasticsearch), and direct query execution (PromQL, LogQL, InfluxQL/Flux, ClickHouse SQL).
“Grafana's MCP server is the observability hub for AI agents. The first wave of capabilities centres on dashboards: search, get full or summary views, extract specific dashboard properties via JSONPath, patch dashboards while keeping the full JSON out of the response. The second wave covers datasource operations across the major Grafana datasource types (Prometheus, Loki, ClickHouse, CloudWatch, Elasticsearch). The third wave runs queries directly: PromQL against Prometheus including histogram percentile calculations, LogQL against Loki with pattern detection, InfluxDB queries (InfluxQL or Flux), ClickHouse SQL. The architectural decision worth understanding: context-window management is treated as a first-class concern, with `get_dashboard_summary` and `get_dashboard_property` providing scoped access to large dashboards while keeping the full JSON out of the agent's context. This is the kind of detail that signals vendor maturity. Grafana version 9.0+ is required for full functionality; older instances may miss specific datasource API endpoints. For teams running Grafana, this is the observability MCP to install.”
INSTALL THIS SERVER
{
"mcpServers": {
"grafana": {
"command": "uvx",
"args": [
"mcp-grafana"
],
"env": {
"GRAFANA_URL": "http://localhost:3000",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
}
}
}
}
{
"mcpServers": {
"grafana": {
"command": "uvx",
"args": [
"mcp-grafana"
],
"env": {
"GRAFANA_URL": "http://localhost:3000",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
}
}
}
}
{
"mcpServers": {
"grafana": {
"command": "uvx",
"args": [
"mcp-grafana"
],
"env": {
"GRAFANA_URL": "http://localhost:3000",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
}
}
}
}
{
"mcpServers": {
"grafana": {
"command": "uvx",
"args": [
"mcp-grafana"
],
"env": {
"GRAFANA_URL": "http://localhost:3000",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
}
}
}
}
{
"mcpServers": {
"grafana": {
"command": "uvx",
"args": [
"mcp-grafana"
],
"env": {
"GRAFANA_URL": "http://localhost:3000",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
}
}
}
}
8 TOOLS AVAILABLE
OUR ASSESSMENT
- Vendor-official from Grafana Labs; same team builds Grafana and the MCP server.
- Context-window-aware tool design: `get_dashboard_summary` and `get_dashboard_property` provide scoped dashboard access for large dashboards.
- Multi-datasource query coverage: PromQL, LogQL, InfluxQL/Flux, ClickHouse SQL all supported through dedicated tools.
- Optional toolset gating (`runpanelquery`, `examples`, `influxdb`, `clickhouse`) keeps the default tool surface minimal until explicitly enabled.
- Requires Grafana 9.0 or later; older instances miss specific datasource API endpoints and some features fail silently.
- Context window management is operator's responsibility for large dashboards; the README warns explicitly against `get_dashboard_by_uid` for big dashboards.
- Service Account Token authentication scope determines what the agent can read; misconfigured scopes expose sensitive datasources.
Authentication uses Grafana Service Account Tokens via `GRAFANA_SERVICE_ACCOUNT_TOKEN`. The token's role and folder permissions bound the agent's blast radius, so least-privilege scoping at the Grafana identity layer is the security boundary. For Grafana Cloud, replace `GRAFANA_URL` with the team's instance URL. The MCP server runs locally and reads dashboards, datasources, and query results based on the token's scope; no destructive operations exist outside dashboard create/update which the agent's role determines. For multi-team Grafana instances, scope tokens to specific folders to restrict cross-team visibility.
Teams running Grafana 9.0+ who want an agent that can search dashboards, query datasources, and extract observability data through natural language.
TECHNICAL DETAILS
ADOPTION METRICS
// Reading this2.9k stars in fourteen months reflect Grafana Labs' vendor-stewardship and observability community adoption. Star traction tracks alongside Grafana Cloud expansion.
// Reading thisTop-ranked monitoring MCP and the only vendor-official observability server in the directory. The context-window-aware tool design signals editorial maturity.
SOURCES & VERIFICATION
We don't take any single directory's word for it. Before scoring, we cross-reference 5 public MCP sources, install the server ourselves against the clients we cover, and record when we last re-verified.
The same server, 5 different lenses. We reconcile these signals into our editorial score, which is why our number sometimes diverges from a directory-aggregate star count.
| Source | Their rating | Their star count | Their downloads | Last synced |
|---|---|---|---|---|
| AutomationSwitch This page | 4.5editorial | 2,929 | — | APR 28, 2026 |
| PulseMCP | — unrated | unavailable | unavailable | APR 28, 2026 |
| Official MCP Registry | — unrated | unavailable | unavailable | APR 28, 2026 |
| Awesome MCP Servers | — unrated | unavailable | unavailable | APR 28, 2026 |
| Smithery | — unrated | unavailable | unavailable | APR 28, 2026 |
| MCP.so | — unrated | unavailable | unavailable | APR 28, 2026 |
// Counts are directory-reported; we don't adjust them. Discrepancies usually come from different snapshot times or star-caching.
DISCUSS YOUR
MCP REQUIREMENTS.
Evaluating a server, scoping an internal deployment, or working out whether MCP is the right fit at all. Start the conversation and we will point you at the right piece of the ecosystem.