This repository is a fork of the original Grafana MCP server. It includes custom modifications listed below.
If you want an AI assistant working directly with MCP Grafana Hyper, the mcp grafana hyper mcp server is the bridge. This repository is a fork of the original Grafana MCP server. It includes custom modifications listed below.
This repository is a fork of the original Grafana MCP server. It includes custom modifications listed below.
Once connected, the assistant can call these 14 tools directly:
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 — Prometheuslist_prometheus_label_values — Prometheuslist_incidents — IncidentThe server is distributed via a container image as mcp/grafana, so most clients can run it without a manual build step. Add it to your MCP client's configuration and restart the client to pick it up — the copy-paste configs for Claude Desktop, Claude Code and Cursor are on this page.
Before the server will start you need to supply 2 environment variables: GRAFANA_URL, GRAFANA_API_KEY. Keep credentials in your client's env block or a secrets manager rather than committing them.
Monitoring servers replace the paste-the-stack-trace ritual with an assistant that reads the real event, with all its surrounding context intact. MCP Grafana Hyper sits in that group, and the shape of its toolset — list_teams, search_dashboards, get_dashboard_by_uid among others — tells you what it is really for. Worth comparing against the other monitoring security servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.
| 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.