Grafana MCP

At a glance

Grafana Labs' own server works with a self-hosted Grafana or Grafana Cloud. The model can search and summarise dashboards, read panel queries, run PromQL against Prometheus and LogQL against Loki, search traces in Tempo, and read alert rules, incidents, OnCall schedules and annotations. Tools for ClickHouse, CloudWatch, Elasticsearch and other datasources are there too, switched off until you ask for them.

It can also change things: edit dashboards, create folders and alert rules, open incidents. Start it with --disable-write and a service account that only has viewer rights unless you want that. It sends anonymous usage counts to Grafana Labs unless you turn them off.

Made by

Grafana Labs

Licence

Apache-2.0

Latest version

2.1.1 (20 Oct 2026)

PyPI package

mcp-grafana

GitHub stars

3.6K

Downloads

125.1K a week

Last commit

26 Oct 2026

Tools

62

Runs on

Your computer

Our check: We ran this exact config on 27 Oct 2026: it started and answered with 62 tools.

What's in the pod: its tools

We found 62 tools when we started it on 27 Oct 2026. Every one of them only reads, so nothing changes unless you act on what it finds.

Tool groups

Default

Dashboards, datasources, Prometheus, Loki, Tempo, Pyroscope, alerting, incidents, OnCall, annotations and docs, as listed here in read-only mode.

Write tools

Updating and patching dashboards, creating folders, alert rules, incidents and annotations. Hidden by --disable-write, which our config uses.

--enabled-tools extras

Off by default and switched on by name: sql (ClickHouse, Snowflake, Athena), cloudwatch, elasticsearch, influxdb, graphite, cloudlogging, runpanelquery and examples, among others.

Grouped and described by us. The README on GitHub lists the inputs each tool takes.

Set it up

Pick your app for the exact snippet and where it goes.

{
  "mcpServers": {
    "grafana": {
      "command": "uvx",
      "args": [
        "mcp-grafana",
        "--disable-write"
      ],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "YOUR_SERVICE_ACCOUNT_TOKEN"
      }
    }
  }
}

claude mcp add-json grafana '{"command":"uvx","args":["mcp-grafana","--disable-write"],"env":{"GRAFANA_URL":"http://localhost:3000","GRAFANA_SERVICE_ACCOUNT_TOKEN":"YOUR_SERVICE_ACCOUNT_TOKEN"}}'

{
  "mcpServers": {
    "grafana": {
      "command": "uvx",
      "args": [
        "mcp-grafana",
        "--disable-write"
      ],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "YOUR_SERVICE_ACCOUNT_TOKEN"
      }
    }
  }
}

{
  "servers": {
    "grafana": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "mcp-grafana",
        "--disable-write"
      ],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "YOUR_SERVICE_ACCOUNT_TOKEN"
      }
    }
  }
}

{
  "mcpServers": {
    "grafana": {
      "command": "uvx",
      "args": [
        "mcp-grafana",
        "--disable-write"
      ],
      "env": {
        "GRAFANA_URL": "http://localhost:3000",
        "GRAFANA_SERVICE_ACCOUNT_TOKEN": "YOUR_SERVICE_ACCOUNT_TOKEN"
      }
    }
  }
}

We publish it in read-only mode; drop "--disable-write" to allow edits. Add "GRAFANA_USAGE_STATS": "disabled" in env to stop usage reporting. For Grafana Cloud, set GRAFANA_URL to your stack, such as https://you.grafana.net.

New to this? See the setup guides for Claude Code, Cursor, Claude Desktop and ChatGPT.

Settings

Names are exactly as the project spells them. Required ones are marked.

What it can touch

Safer setup: Use --disable-write with a Viewer service account. That way even grafana_api_request cannot change anything the token is not allowed to.

Before you start

• Grafana 9.0 or newer, self-hosted or Grafana Cloud
• A service account token
• uv (or the Docker image or Go binary)

If it does not work

Every call returns 401 or 403

Check that the token belongs to a service account in the same organisation and has a role with the access you need.

Answers stop half way on big dashboards

Ask for get_dashboard_summary or get_dashboard_property instead of the full dashboard JSON.

Datasource tools fail on an old Grafana

Grafana 9.0 or newer is needed for full support.

A tool from the README is missing

Some groups are off by default. Add them with --enabled-tools, and drop --disable-write if it is a write tool.

Peas in a pod: similar servers

How Grafana MCP lines up against other cloud and operations servers on the shelf.

Questions

Something wrong on this page? Tell us.