Skip to main content
Glama
Grafana MCP Server

Grafana MCP Server

by DrDroidLab

Grafana MCP Server

Available Tools

The following tools are available via the MCP server:

  • test_connection: Verify connectivity to your Grafana instance and configuration.

  • grafana_promql_query: Execute PromQL queries against Grafana's Prometheus datasource. Fetches metrics data using PromQL expressions, optimizes time series responses to reduce token size.

  • grafana_loki_query: Query Grafana Loki for log data. Fetches logs for a specified duration (e.g., '5m', '1h', '2d'), converts relative time to absolute timestamps.

  • grafana_get_dashboard_config: Retrieves dashboard configuration details from the database. Queries the connectors_connectormetadatamodelstore table for dashboard metadata.

  • grafana_query_dashboard_panels: Execute queries for specific dashboard panels. Can query up to 4 panels at once, supports template variables, optimizes metrics data.

  • grafana_fetch_label_values: Fetch label values for dashboard variables from Prometheus datasource. Retrieves available values for specific labels (e.g., 'instance', 'job'). Supports optional metric filtering.

  • grafana_fetch_dashboard_variables: Fetch all variables and their values from a Grafana dashboard. Retrieves dashboard template variables and their current values.

  • grafana_fetch_all_dashboards: Fetch all dashboards from Grafana with basic information like title, UID, folder, tags, etc.

  • grafana_fetch_datasources: Fetch all datasources from Grafana with their configuration details.

  • grafana_fetch_folders: Fetch all folders from Grafana with their metadata and permissions.

Related MCP server: Metabase MCP Plus

šŸš€ Usage & Requirements

1. Get Your Grafana API Endpoint & Service Account Token

  1. Ensure you have a running Grafana instance (self-hosted or cloud).

  2. Generate a Service Account Token from your Grafana UI:

    • Create Service Account: In your Grafana dashboard, navigate to Admin >> Users & Access >> Service Accounts >> Create a Service Account with Viewer permissions

    • Generate Service Account Key: Within Service Account, create a new Service Account token.

    • Copy the service account token (starts with glsa_)


2. Installation & Running Options

2A.1. Install dependencies with uv

uv venv .venv
source .venv/bin/activate
uv sync

2A.2. Run the server with uv

uv run -m src.grafana_mcp_server.mcp_server
  • You can also use uv to run any other entrypoint scripts as needed.

  • Make sure your config.yaml is in the same directory as mcp_server.py or set the required environment variables (see Configuration section).


  1. Edit grafana-mcp-server/src/grafana_mcp_server/config.yaml with your Grafana details (host, API key).

  2. Start the server:

    docker compose up -d
    • The server will run in HTTP (SSE) mode on port 8000 by default.

    • You can override configuration with environment variables (see below).


3. Configuration

The server loads configuration in the following order of precedence:

  1. Environment Variables (recommended for Docker/CI):

    • GRAFANA_HOST: Grafana instance URL (e.g. https://your-grafana-instance.com)

    • GRAFANA_API_KEY: Grafana Service Account Token (required)

    • GRAFANA_SSL_VERIFY: true or false (default: true)

    • MCP_SERVER_PORT: Port to run the server on (default: 8000)

    • MCP_SERVER_DEBUG: true or false (default: true)

  2. YAML file fallback (config.yaml):

    grafana:
      host: "https://your-grafana-instance.com"
      api_key: "your-grafana-api-key-here"
      ssl_verify: "true"
    server:
      port: 8000
      debug: true

4. Integration with AI Assistants (e.g., Claude Desktop, Cursor)

You can integrate this MCP server with any tool that supports the MCP protocol. Here are the main options:

4A. Using Docker (with environment variables)

{
  "mcpServers": {
    "grafana": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "GRAFANA_HOST",
        "-e",
        "GRAFANA_API_KEY",
        "-e",
        "GRAFANA_SSL_VERIFY",
        "drdroidlab/grafana-mcp-server",
        "-t",
        "stdio"
      ],
      "env": {
        "GRAFANA_HOST": "https://your-grafana-instance.com",
        "GRAFANA_API_KEY": "your-grafana-api-key-here",
        "GRAFANA_SSL_VERIFY": "true"
      }
    }
  }
}
  • The -t stdio argument is supported for compatibility with Docker MCP clients (forces stdio handshake mode).

  • Adjust the volume path or environment variables as needed for your deployment.

4B. Connecting to an Already Running MCP Server (HTTP/SSE)

If you have an MCP server already running (e.g., on a remote host, cloud VM, or Kubernetes), you can connect your AI assistant or tool directly to its HTTP endpoint.

{
  "mcpServers": {
    "grafana": {
      "url": "http://your-server-host:8000/mcp"
    }
  }
}
  • Replace your-server-host with the actual host where your MCP server is running.

  • For local setup, use localhost as the server host (i.e., http://localhost:8000/mcp).

  • Use http for local or unsecured deployments, and https for production or secured deployments.

  • Make sure the server is accessible from your client machine (check firewall, security group, etc.).


Health Check

curl http://localhost:8000/health

The server runs on port 8000 by default.


5. Project Structure

grafana-mcp-server/
│   └── src/
│       └── grafana_mcp_server/
│           ā”œā”€ā”€ __init__.py
│           ā”œā”€ā”€ config.yaml              # Configuration file
│           ā”œā”€ā”€ mcp_server.py            # Main MCP server implementation
│           ā”œā”€ā”€ stdio_server.py          # STDIO server for MCP
│           └── processor/
│               ā”œā”€ā”€ __init__.py
│               ā”œā”€ā”€ grafana_processor.py # Grafana API processor
│               └── processor.py         # Base processor interface
ā”œā”€ā”€ tests/
ā”œā”€ā”€ Dockerfile
ā”œā”€ā”€ docker-compose.yml
ā”œā”€ā”€ pyproject.toml
└── README.md


6. Troubleshooting

Common Issues

  1. Connection Failed:

    • Verify your Grafana instance is running and accessible

    • Check your API key has proper permissions

    • Ensure SSL verification settings match your setup

  2. Authentication Errors:

    • Verify your API key is correct and not expired

    • Check if your Grafana instance requires additional authentication

  3. Query Failures:

    • Ensure datasource UIDs are correct

    • Verify PromQL/Loki query syntax

    • Check if the datasource is accessible with your API key

Debug Mode

Enable debug mode to get more detailed logs:

export MCP_SERVER_DEBUG=true

7. Contributing

  1. Fork the repository

  2. Create a feature branch (git checkout -b feature/amazing-feature)

  3. Commit your changes (git commit -m 'Add some amazing feature')

  4. Push to the branch (git push origin feature/amazing-feature)

  5. Open a Pull Request


8. License

This project is licensed under the MIT License - see the LICENSE file for details.


9. Support

  1. Need help anywhere? Join our discord channel and message on #mcp channel.

  2. Want a 1-click MCP Server? Join the same community and let us know.

  3. For issues and questions, please open an issue on GitHub or contact the maintainers.

Available Tools

10 tools
grafana_fetch_all_dashboardsC

Fetches all dashboards from Grafana with basic information like title, UID, folder, tags, etc.

Inputs: limit.

grafana_fetch_dashboard_variablesC

Fetches all variables and their values from a Grafana dashboard. Retrieves dashboard template variables and their current values.

Inputs: dashboard_uid (required).

grafana_fetch_datasourcesB

Fetches all datasources from Grafana with their configuration details.

Inputs: no named parameters.

grafana_fetch_foldersB

Fetches all folders from Grafana with their metadata and permissions.

Inputs: no named parameters.

grafana_fetch_label_valuesC

Fetches label values for dashboard variables from Prometheus datasource. Retrieves available values for specific labels (e.g., 'instance', 'job').

Inputs: datasource_uid (required), label_name (required), metric_match_filter.

grafana_get_dashboard_configC

Retrieves dashboard configuration details from the database. Queries the connectors_connectormetadatamodelstore table for dashboard metadata.

Inputs: dashboard_uid (required).

grafana_loki_queryA

Queries Grafana Loki for log data. Fetches logs for a specified duration (e.g., '5m', '1h', '2d'), converts relative time to absolute timestamps. Note: Loki queries require at least one non-empty matcher. Use patterns like '{job=".+"}' instead of '{job=".*"}' or '{}' to avoid syntax errors.

Inputs: datasource_uid (required), query (required), duration, start_time, +2 more.

grafana_promql_queryC

Executes PromQL queries against Grafana's Prometheus datasource. Fetches metrics data using PromQL expressions, optimizes time series responses to reduce token size.

Inputs: datasource_uid (required), query (required), start_time, end_time, +1 more.

grafana_query_dashboard_panelsA

Executes queries for specific dashboard panels. Can query up to 4 panels at once, supports template variables, optimizes metrics data.

Inputs: dashboard_uid (required), panel_ids (required), template_variables.

test_connectionA

Test connection to Grafana API to verify configuration and connectivity. Requires API key or open Grafana instance.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.6/5.0

    Scored across 10 tools

    Disambiguation5/5

    Every tool has a clearly distinct purpose targeting specific Grafana resources or functions. For example, grafana_fetch_all_dashboards retrieves dashboard lists while grafana_fetch_dashboard_variables gets template variables, and grafana_loki_query versus grafana_promql_query handle different query types. There is no overlap that would cause agent misselection.

    Naming Consistency5/5

    All tools follow a consistent snake_case pattern with 'grafana_' prefix and descriptive verb_noun combinations. The naming convention is perfectly predictable: grafana_fetch_*, grafana_get_*, grafana_query_*, and grafana_*_query patterns are used appropriately throughout the set.

    Tool Count5/5

    With 10 tools, this server is well-scoped for Grafana operations. Each tool earns its place by covering distinct aspects: dashboard management, data source access, query execution, and connectivity testing. This count provides comprehensive coverage without being overwhelming.

    Completeness4/5

    The toolset provides excellent coverage for querying, fetching, and testing Grafana resources. Minor gaps exist in dashboard lifecycle management (no create/update/delete operations for dashboards or folders), but agents can work effectively with the read-oriented operations provided for the core Grafana use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to interact with Signoz observability platform, providing tools to query dashboards, metrics, traces, logs, and APM data with time range support.
      14
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query databases, execute SQL, and manage Metabase resources like dashboards, cards, and collections through natural language.
      22
      18 PyPI
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables AI assistants to query and analyze logs from Grafana Loki using LogQL, supporting label discovery and keyword search.
      4
      -