# Grafana MCP server

> Apache-2.0 MCP server from Grafana Labs for dashboards, datasources, alerts and incidents

**Category:** AI Agents  
**Pricing:** open-source  
**URL:** https://github.com/grafana/mcp-grafana  
**GitHub:** https://github.com/grafana/mcp-grafana  
**Added:** 2026-10-10

---

## The Hook

mcp-grafana lets an MCP client search dashboards, query Prometheus and Loki, read alert rules and work incidents in your Grafana — so the agent investigating an outage can look at the same panels you would.

## What's Good

Apache-2.0, maintained by Grafana Labs, release v2.0.2. `uvx mcp-grafana` with `GRAFANA_URL` (plus a service account token) gets you running; a Docker image, a standalone binary and a Helm chart cover the other setups. Works against self-hosted Grafana or Grafana Cloud. ★~3.5k.

## The Catch

Needs Grafana 9.0 or newer. Several tool groups — panel queries, SQL datasources, InfluxDB, CloudWatch and more — stay off until you turn them on with `--enabled-tools`, so check the list before assuming the agent can see a datasource. Updating a dashboard means sending its full JSON, which eats a lot of agent context on big dashboards. Vs grafana (the dashboards themselves) and opensre (an agent that runs incident investigations end to end): this is the plain bridge that gives any agent read and write access to Grafana.

## Verdict

The official way to put Grafana in an agent’s hands — enable only the tool groups you need and keep dashboard edits small.
