Skip to content

grafana/mcp-grafana

Grafana MCP server

A Model Context Protocol (MCP) server for Grafana.

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

Features

  • Search for dashboards
  • 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
  • Search, create, update and close incidents
  • Start Sift investigations and view the results

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.

Tools

Tool Category Description
search_dashboards Search Search for dashboards
list_datasources Datasources List datasources
get_datasource_by_uid Datasources Get a datasource by uid
get_datasource_by_name Datasources Get a datasource by name
query_prometheus Prometheus Execute a query against a Prometheus datasource
list_prometheus_metric_metadata Prometheus List metric metadata
list_prometheus_metric_names Prometheus List available metric names
list_prometheus_label_names Prometheus List label names matching a selector
list_prometheus_label_values Prometheus List values for a specific label
list_incidents Incident List incidents in Grafana Incident
create_incident Incident Create an incident in Grafana Incident
add_activity_to_incident Incident Add an activity item to an incident in Grafana Incident
resolve_incident Incident Resolve an incident in Grafana Incident

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 Grafana documentation for details.

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

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

Note: if you see Error: spawn uvx ENOENT in Claude Desktop, you need to specify the full path to uvx (see discussion)

To disable a category of tools, set the environment variable GRAFANA_TOOLS__<CATEGORY>__ENABLED to "false". For example, to disable the search tools, set "GRAFANA_TOOLS__SEARCH__ENABLED": "false".

Development

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

This project uses uv to manage dependencies. Install uv following the instructions for your platform.

You can then create a virtual environment and install the dependencies with:

uv sync --all-groups

To run the server, use:

uvx --from . mcp-grafana

Testing

TL;DR: start a Grafana instance with docker-compose up, run uv run ruff check . for lints, and uv run pytest tests --integration to run unit and integration tests.

To run unit tests, run:

uv run pytest tests

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

docker-compose up -d

The integration tests can be run with:

uv run pytest --integration tests

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

Certain tools use functionality that is only available in Grafana Cloud. Such tests should use the mark_cloud Pytest mark; see the incident_test.py file for an example. Use the GRAFANA_URL and GRAFANA_API_KEY environment variables to configure the Grafana instance to use for testing, and run these tests with:

GRAFANA_URL=https://myinstance.grafana.net GRAFANA_API_KEY=my-api-key uv run pytest --cloud tests

Linting

This project uses ruff for linting.

License

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