This repository is a fork of the original Grafana MCP server. It includes custom modifications listed below.
Connect MCP Grafana With Questdb to Claude, Cursor or any other MCP client and it stops being a tab you switch to. This repository is a fork of the original Grafana MCP server. It includes custom modifications listed below. The mcp grafana with questdb mcp server is what makes that connection.
The toolset is worth reading before you wire it up, because it tells you what the integration is really for:
list_teams — Adminsearch_dashboards — Searchget_dashboard_by_uid — Dashboardupdate_dashboard — Dashboardget_dashboard_panel_queries — Dashboardlist_datasources — Datasourcesget_datasource_by_uid — Datasourcesget_datasource_by_name — Datasourcesquery_prometheus — Prometheuslist_prometheus_metric_metadata — Prometheuslist_prometheus_metric_names — Prometheuslist_prometheus_label_names — PrometheusConfiguration is passed through the environment: GRAFANA_URL, GRAFANA_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.
Installation goes through your MCP client rather than a global install: point it at mcp/grafana on a container image and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.
This sits in the monitoring and observability group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. MCP Grafana With Questdb's toolset — list_teams, search_dashboards, get_dashboard_by_uid and 11 more — is a fair guide to whether it matches your workflow. It is maintained by kis9a; worth a glance at recent repository activity before you build anything load-bearing on it.
This entry was verified against MCP Grafana With Questdb's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.
| Tool | What it does |
|---|---|
| list_teams | Admin |
| search_dashboards | Search |
| get_dashboard_by_uid | Dashboard |
| update_dashboard | Dashboard |
| get_dashboard_panel_queries | Dashboard |
| list_datasources | Datasources |
| get_datasource_by_uid | Datasources |
| get_datasource_by_name | Datasources |
| query_prometheus | Prometheus |
| list_prometheus_metric_metadata | Prometheus |
| list_prometheus_metric_names | Prometheus |
| list_prometheus_label_names | Prometheus |
| list_prometheus_label_values | Prometheus |
| list_incidents | Incident |
**If using Docker:**
```json
{
"mcpServers": {
"grafana": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"-e",
"GRAFANA_URL",
"-e",
"GRAFANA_API_KEY",
"mcp/grafana",
"-t",
"stdio",
"-debug"
],
"env": {
"GRAFANA_URL": "http://localhost:3000",
"GRAFANA_API_KEY": "<your service account token>"
}
}
}
}Configuration as documented by the project. Restart the client after saving.
| Variable | Description | Required |
|---|---|---|
| GRAFANA_URL | Endpoint or connection string the server talks to. | Yes |
| GRAFANA_API_KEY | Credential the server authenticates with. | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
Enables enhanced web research capabilities for large language models through intelligent search queuing and advanced content extraction.
Automates browser interactions and enables Large Language Models (LLMs) to interact with web pages through Playwright and Chrome DevTools Protocol
Guides tool usage by providing recommendations for MCP tools at each problem-solving stage.