Grafana MCP server

A (MCP) server for Grafana.

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

Features

• Search for dashboards

• Dashboards

  • Get dashboard by UID

  • Update or create a dashboard (DISCLAIMER: Be careful with context windows. See https://github.com/grafana/mcp-grafana/issues/101 for details)

  • Get the title, query string, and datasource information (including UID and type, if available) from every panel in a dashboard

• List and fetch datasource information

• Query datasources

  • Prometheus

  • Loki

    • Log queries

    • Metric queries

  • Tempo

  • Pyroscope

• Query Prometheus metadata

  • Metric metadata

  • Metric names

  • Label names

  • Label values

• Query Loki metadata

  • Label names

  • Label values

  • Stats

• Search, create, update and close incidents

• Start Sift investigations and view the results

  • Create Investigations

  • List Investigations with a limit parameter

  • Get Investigation

  • Get Analyses

  • Find error patterns in logs using Sift

  • Find slow requests using Sift

  • Add tools on the other Sift Checks

• Alerting

  • List and fetch alert rule information

  • Get alert rule statuses (firing/normal/error/etc.)

  • Create and change alert rules

  • List contact points

  • Create and change contact points

• Access Grafana OnCall functionality

  • List and manage schedules

  • Get shift details

  • Get current on-call users

  • List teams and users

  • List alert groups

• Admin functionality

  • List users

  • List teams

  • List roles

  • List assignments of roles

  • Debug role assignments

The list of tools is configurable, so you can choose which tools you want to make available to the MCP client. This is useful if you don't use certain functionality or if you don't want to take up too much of the context window. To disable a category of tools, use the --disable-<category> flag when starting the server. For example, to disable the OnCall tools, use --disable-oncall.

Tools

Usage

1. Create a service account in Grafana with enough permissions to use the tools you want to use, generate a service account token, and copy it to the clipboard for use in the configuration file. Follow the for details.

2. You have several options to install mcp-grafana:

   • Docker image: Use the pre-built Docker image from Docker Hub:

     docker pull mcp/grafana docker run -p 8000:8000 -e GRAFANA_URL=http://localhost:3000 -e GRAFANA_API_KEY=<your service account token> mcp/grafana

   • Download binary: Download the latest release of mcp-grafana from the releases page and place it in your $PATH.

   • Build from source: If you have a Go toolchain installed you can also build and install it from source, using the GOBIN environment variable to specify the directory where the binary should be installed. This should also be in your PATH.

     GOBIN="$HOME/go/bin" go install github.com/grafana/mcp-grafana/cmd/mcp-grafana@latest

3. Add the server configuration to your client configuration file. For example, for Claude Desktop:

   If using the binary:

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

   If using Docker:

   { "mcpServers": { "grafana": { "command": "docker", "args": [ "run", "--rm", "-p", "8000:8000", "-e", "GRAFANA_URL", "-e", "GRAFANA_API_KEY", "mcp/grafana" ], "env": { "GRAFANA_URL": "http://localhost:3000", "GRAFANA_API_KEY": "<your service account token>" } } } }

Note: if you see Error: spawn mcp-grafana ENOENT in Claude Desktop, you need to specify the full path to mcp-grafana.

Using VSCode with remote MCP server

Make sure your .vscode/settings.json includes:

Debug Mode

You can enable debug mode for the Grafana transport by adding the -debug flag to the command. This will provide detailed logging of HTTP requests and responses between the MCP server and the Grafana API, which can be helpful for troubleshooting.

To use debug mode with the Claude Desktop configuration, update your config as follows:

If using the binary:

If using Docker:

Development

Contributions are welcome! Please open an issue or submit a pull request if you have any suggestions or improvements.

This project is written in Go. Install Go following the instructions for your platform.

To run the server, use:

You can also run the server using the SSE transport inside a custom built Docker image. To build the image, use

And to run the image, use:

Testing

There are three types of tests available:

1. Unit Tests (no external dependencies required):

You can also run unit tests with:

2. Integration Tests (requires docker containers to be up and running):

3. Cloud Tests (requires cloud Grafana instance and credentials):

Note: Cloud tests are automatically configured in CI. For local development, you'll need to set up your own Grafana Cloud instance and credentials.

More comprehensive integration tests will require a Grafana instance to be running locally on port 3000; you can start one with Docker Compose:

The integration tests can be run with:

If you're adding more tools, please add integration tests for them. The existing tests should be a good starting point.

Linting

To lint the code, run:

This includes a custom linter that checks for unescaped commas in jsonschema struct tags. The commas in description fields must be escaped with \\, to prevent silent truncation. You can run just this linter with:

See the JSONSchema Linter documentation for more details.

License

This project is licensed under the Apache License, Version 2.0.