---
title: "Grafana MCP Server: review, setup & limitations · Undominated.ai"
canonical: https://undominated.ai/mcp-servers/grafana/
description: "Connects dashboards, logs, metrics and related Grafana data sources to an assistant, with separate controls for writes and query execution."
---

# Grafana MCP Server: review, setup & limitations · Undominated.ai

> Connects dashboards, logs, metrics and related Grafana data sources to an assistant, with separate controls for writes and query execution.

[← Explore all mcp servers](/mcp-servers/)

OBSERVABILITY / Grafana

# Grafana MCP Server

Connects dashboards, logs, metrics and related Grafana data sources to an assistant, with separate controls for writes and query execution.

 [See setup guidance ↓](#setup)[Original source ↗](https://github.com/grafana/mcp-grafana)

SOURCE REVIEW

 Reviewed 2026-10-14
 Evidence 4 linked sources
 Publisher Grafana
 Licence [Apache-2.0 ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/LICENSE)
 Revision 8424d5729dd3
 [Read what was—and wasn’t—checked ↓](#review)

“This provides access to your Grafana instance and the surrounding ecosystem.”

 [Grafana · upstream description ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/README.md) Our analysis follows below.

01 / THE REASONING

## Why this made the selection.

 - Separates metadata access, datasource query execution and write tools through explicit flags.
- Uses existing Grafana datasource connections, so an investigation can cross observability systems.
- The pinned README is the Grafana server that can query dashboards and datasources, and it documents separate switches for write tools and for datasource queries.
- Raw SQL tools are removed in read-only mode because the server does not inspect the query text.

### A good fit for

 - Starting from a dashboard summary and following a specific panel into bounded PromQL or LogQL investigation.
- Inventorying dashboards and datasource metadata with --disable-query when executing telemetry queries is outside the task.
- Reading Grafana dashboards and PromQL or LogQL when the service account should not change the instance
- Discovery of datasources and dashboards without running queries

### Weigh up before choosing

 - Write tools are enabled unless disabled; raw SQL permissions also depend on the underlying datasource.
- HTTP caller authentication is optional and must be configured; binding a public interface does not add it.
- --disable-query wins over --enable-query, but it is not a complete ban on datasource access: panel rendering is unaffected.
- GRAFANA_SERVICE_ACCOUNT_TOKEN_FILE is read on requests for rotation; if both token settings exist, the inline token takes precedence.
- A service-account token stays bound to one Grafana organisation; changing an organisation parameter does not confer membership.
- Google Cloud Logging and agent-observability tools are off unless named in --enabled-tools.
- A Grafana URL override without an allowlist can reach any HTTP or HTTPS URL the server can reach.
- Read-only mode does not make a raw SQL tool safe; it removes query_sql and query_influxdb unless --enable-query is also set.
- A pin does not verify transitive dependencies.
- This review did not execute the resource.
- Dynamic multi-org discovery can expose datasource tools across every organization available to the credential.

02 / THE REVIEW RECORD

## What we actually inspected.

Source review has boundaries. A clear record is more useful than a “safe” badge.

### Material inspected

 - README.md setup, configuration and operating-limit sections at 8424d5729dd362ae2d1d00cf23a1733c4458590e
- LICENSE at the same revision
- go.mod
- cmd/mcp-grafana/main.go
- README.md
- LICENSE
- Round 2 reread of acquired publisher setup and permission evidence; see immutable wave review.

### Our findings

 - Read-only mode removes raw SQL and InfluxDB query tools unless explicitly re-enabled; Grafana permissions alone do not make a downstream SQL credential read-only.
- The current README documents token-file precedence, query-control precedence and compact dashboard retrieval to reduce response size.
- `--disable-write` stops dashboard, folder, incident, alert, annotation, and snapshot writes, and it also drops raw SQL tools that can run DROP or DELETE when the datasource credential allows it.
- `--disable-query` removes every tool that executes a datasource query while leaving metadata tools, and it wins over `--enable-query`.
- Google Cloud Logging tools are disabled by default, and enabling X-Grafana-URL without an allowlist lets a caller select any HTTP or HTTPS URL the process can reach.
- Anonymous process-level usage reporting is enabled by default; the README documents GRAFANA_USAGE_STATS=disabled or DO_NOT_TRACK=1 to opt out.

### Not established by this review

 - Server startup, authentication and live tool calls were not tested.
- Published package/container parity with the inspected source commit and security isolation were not tested.
- The server was not started and its tools were not called.
- A pin does not verify transitive dependencies.

The review applies to the material and revision named here. A newer upstream release can change its behavior.

03 / PUT IT TO WORK

## Connect a server deliberately.

[Upstream setup instructions ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/README.md)

DOCUMENTED COMMAND

 uvx mcp-grafana Copy command ↗

Copying does not execute this command. It may retrieve a newer version than the reviewed source.

 - Set GRAFANA_URL and an appropriately scoped Grafana service-account token.
- Choose tool categories and write/query restrictions; configure a caller token before sharing a network listener.

### Before you start

 - uv and access to a supported Grafana instance.

### Documented configuration example

Use the client and authentication context described in the setup guidance. Configuration formats vary between hosts.

 {
 "mcpServers": {
 "grafana": {
 "command": "uvx",
 "args": [
 "mcp-grafana"
 ],
 "env": {
 "GRAFANA_URL": "http://localhost:3000",
 "GRAFANA_SERVICE_ACCOUNT_TOKEN": "<your service account token>"
 }
 }
 }
} Copy configuration ↗

### Compatibility

An MCP client supporting stdio, SSE, Streamable HTTP. · uv and access to a supported Grafana instance.

### Implementation

Go

### Transports

stdio · SSE · Streamable HTTP

### Observability / Configured credentials or local access

 - Reads dashboards, telemetry and datasource query results.
- Enabled tools can change Grafana state; SQL datasource queries may mutate data if allowed downstream.

### Cost model

Grafana and connected datasource plans or hosting/query usage apply.

04 / FOLLOW THE EVIDENCE

## The source trail.

Our notes are separate from the original resource. Check upstream before adopting a new version.

 - [Pinned upstream setup, capabilities and operating limits ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/README.md) Checked 2026-10-14 https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/README.md Supports: summary, upstreamDescription, install, configExample, access, limitations, bestFor, review
- [Licence at the reviewed revision ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/LICENSE) Checked 2026-10-14 https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/LICENSE Supports: license
- [Pinned implementation or package metadata: go.mod ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/go.mod) Checked 2026-10-14 https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/go.mod Supports: review, install, language
- [Pinned implementation or package metadata: cmd/mcp-grafana/main.go ↗](https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/cmd/mcp-grafana/main.go) Checked 2026-10-14 https://github.com/grafana/mcp-grafana/blob/8424d5729dd362ae2d1d00cf23a1733c4458590e/cmd/mcp-grafana/main.go Supports: review, install, language

KEEP COMPARING

## Other approaches to consider.

Related by category or shared topics. These are alternatives to inspect, not a measured quality order.

 [### IBM Instana MCP Server ↗ Inspect application telemetry, alerts and service-level objectives through Instana API tools.](/mcp-servers/instana/)[### New Relic MCP ↗ Hosted New Relic server at mcp.newrelic.com exposing entity lookup, alerting, incident response, NRQL and deployment-impact tools over Streamable HTTP. OAuth is the documented default; organisation admins gate access through feature-control toggles and an include-tags header filters which tool families a client receives.](/mcp-servers/newrelic/)[### Zabbix MCP Server ↗ Inspect Zabbix hosts, triggers and alerts and perform selected administration through scoped server tokens.](/mcp-servers/zabbix/)

 [AI Tools ↗](/tools/)[Skills ↗](/skills/)[Agents ↗](/agents/)[MCP Servers ↗](/mcp-servers/)[Workflows ↗](/workflows/)

## Continue your investigation

 - [Inspect resource evidence](/tools/)
- [Choose a host](/agents/)
- [Inspect reusable workflows](/skills/)
- [Use Undominated data](/api/)
