Connect Claude to Grafana

Search dashboards and folders by title or tag. This is the entry point for everything dashboard-shaped: it returns the UIDs that get_dashboard and the annotation actions need. Defaults to dashboards only; pass type dash-folder to list folders instead, or use list_folders.

Fetch one dashboard by UID, including every panel and the datasource queries behind it. Read this before writing your own PromQL: the panels record the queries a team already trusts for a service, and query_prometheus_range can re-run one directly. Call search_dashboards first for the UID. Panel trees are depth-limited to keep the response readable.

List the datasources configured in this Grafana with their UIDs and types. Call this first for every query action: query_prometheus, query_prometheus_range and query_loki all address a datasource by UID, and the type field is what tells you which of them applies (prometheus, loki, mimir, influxdb, …).

Run a PromQL query at a single instant through Grafana's datasource proxy and return the current value per series. Use this for "what is it right now" - error rate, replica count, queue depth. Use query_prometheus_range when you need a shape over time. The datasource UID comes from list_datasources and must be of type prometheus or mimir.

Run a PromQL query over a time window through Grafana's datasource proxy and return one series of points per label set. Use this to see whether something is climbing, and to line a metric up against a deploy. Keep step large enough that the window divides into a few hundred points or Prometheus refuses the query outright.

Run a LogQL query over a time window through Grafana's datasource proxy and return the matching log lines. Every LogQL query needs at least one stream selector in braces, e.g. {app="checkout"} |= "timeout". A metric-shaped LogQL query such as sum(rate({app="checkout"} |= "error" [5m])) returns series instead of lines. The datasource UID comes from list_datasources and must be of type loki.

List the Grafana-managed alert rules that are configured, with their queries, evaluation intervals and labels. This says what could fire; list_active_alerts says what is firing now. Use it to find out why an alert exists and which datasource it watches.

List the alerts currently held by Grafana's built-in Alertmanager - what is firing right now, with each alert's labels, annotations and when it started. Start here when asked "is anything on fire", then use list_alert_rules to understand a rule the answer names.

List the dashboard folders the token can see, with their UIDs and titles. Use it to map a team name onto the folder UID that search_dashboards filters on.

List annotations - the timestamped markers drawn on dashboard graphs, including the ones Grafana writes itself when an alert changes state. Use it to find out what a team recorded as happening at the moment a metric moved. Filter by dashboard UID or by tag; times are epoch milliseconds.