If you already know the Grafana MCP server, the reason to pick this fork is narrow and specific: two datasource types the original does not query, and streamable-http as a transport option. Everything else — including the flag-based category disabling that keeps the tool list from swallowing your context — comes along unchanged.
A fork of the Grafana MCP server. It keeps the upstream surface — dashboards, datasources, Prometheus, Loki, incidents, Sift, OnCall, Pyroscope, alerting — and adds QuestDB and Athena as queryable datasource types, each behind its own enable flag.
- The fork's additions: `query_questdb_sql` and `query_athena_sql`, each executing SQL against that datasource and returning one JSON object per row
- Dashboards — `search_dashboards`, `get_dashboard_by_uid`, `update_dashboard`, `get_dashboard_panel_queries` for pulling every panel's query and datasource
- Metrics and logs — `query_prometheus`, `list_prometheus_metric_names`, `list_prometheus_label_values`, `query_loki_logs`, `query_loki_stats`
- Incidents and on-call — `list_incidents`, `create_incident`, `resolve_incident`, `list_oncall_schedules`, `get_current_oncall_users`
- Sift investigations, including `find_error_pattern_logs` and `find_slow_requests`
- Profiling — `list_pyroscope_profile_types`, `fetch_pyroscope_profile`
- Per-category disable flags, so you can drop whole groups you do not use and keep the tool list short
A Grafana service account token with the permissions the tools you want will need, passed as GRAFANA_API_KEY alongside GRAFANA_URL. Run the published Docker image, a release binary on your PATH, or build from source with Go. One catch worth knowing before you configure a client: the Docker image's entrypoint defaults to SSE, so for a stdio client you must pass `-t stdio` and run the container with `-i`. Apache licensed.
One command plus a key — mcp-grafana, then supply credentials