Dashboards, Prometheus and Loki queries, incidents and alerts — observability by conversation.
The Grafana MCP server (maintained by Grafana Labs, written in Go) connects assistants to the observability stack most infrastructure teams already run: dashboards, datasources, Prometheus metrics, Loki logs, alert rules, and Grafana's incident and OnCall tooling.
Its defining capability is query without query-language fluency. PromQL and LogQL are powerful and nobody's favourite; being able to ask "what's the p95 latency on the API over the last six hours?" or "show error-level logs from the payments service around 14:30" and have correct queries generated, executed and interpreted lowers the barrier to data most teams underuse. The assistant handles rate windows, label matchers and histogram quantiles — the parts humans get subtly wrong.
Incident workflows benefit next. During an investigation the assistant can pull the relevant dashboard panels, correlate a metric spike with matching log lines, check which alerts fired and when, and draft the incident timeline — the toil half of incident response, automated where it's most resented. Alert-rule management and on-call schedule queries round out the operational surface.
It runs as a local binary/Docker container against any Grafana instance (Cloud or self-hosted) with a service-account token, and tool categories can be disabled selectively — a nice touch when you want read-only observability without alert-editing capability. For teams whose single pane of glass is Grafana, this makes that pane conversational.
glsa_) inherit a Grafana role. A Viewer token still answers dashboard, Prometheus and Loki questions while being unable to edit an alert rule — the sensible starting posture.--disable-alerting or --disable-oncall trim the tool surface. The full set spans dashboards, alerting, Incident, OnCall, Pyroscope and Sift, which is a lot to carry if you only came for metrics.Metrics and log questions in English, correct queries underneath.
Spikes, logs and alert timings pulled together into a coherent story.
Which rules exist, which fire noisily, which silences are stale — audited by asking.
| Tool | What it does |
|---|---|
| search_dashboards / get_dashboard_by_uid | Find and read dashboards |
| query_prometheus | Run PromQL queries against Prometheus datasources |
| query_loki_logs | Run LogQL queries against Loki |
| list_alert_rules / get_alert_rule_by_uid | Inspect alerting rules and states |
| list_incidents / create_incident | Grafana Incident workflows |
| list_datasources | Enumerate configured datasources |
| get_current_oncall_users | Who's on call right now (OnCall) |
{
"mcpServers": {
"grafana": {
"command": "docker",
"args": ["run", "--rm", "-i",
"-e", "GRAFANA_URL", "-e", "GRAFANA_SERVICE_ACCOUNT_TOKEN",
"mcp/grafana", "-t", "stdio"],
"env": {
"GRAFANA_URL": "https://your-org.grafana.net",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "glsa_your_token"
}
}
}
}Create a service account token in Grafana with the viewer/editor roles you're comfortable delegating.
A Grafana instance (Cloud or self-hosted) and a service-account token. Binary or Docker to run the server.
| Variable | Description | Required |
|---|---|---|
| GRAFANA_URL | Your Grafana instance URLe.g. https://your-org.grafana.net | Yes |
| GRAFANA_SERVICE_ACCOUNT_TOKEN | Service-account token with appropriate rolese.g. glsa_... | Yes |
Give your coding agent the full DevTools toolbox: traces, network, console, heap snapshots and Lighthouse.
Errors with full context — stack traces, issue triage and AI-powered root-cause analysis from Sentry's server.
A Model Context Protocol (MCP) server that enables AI assistants to integrate with Prometheus Alertmanager
Auth0 Model Context Protocol (MCP) Server (Beta) — A secure and extendable implementation of an MCP server that provides AI assistants with
Query Onchain data, like ERC20 tokens, transaction history, smart contract state.
An MCP server for breaking down complex tasks into manageable pieces with structured JSON storage