Use the Grafana MCP server safely
Sets the ground rules for working with Grafana through the MCP server: confirm the instance, org and permissions, pick the right tool, keep queries small, and ask before any change.
Use it when
- You have just connected Grafana and want to know what the assistant can see
- A Grafana task is about to start and you want to confirm the right instance and org first
- You need to know which tools change Grafana and which only read it
Tools it uses
check_datasources_healthget_current_oncall_usersget_dashboard_by_uidget_alert_groupget_annotation_tagsget_dashboard_panel_queriesfind_error_pattern_logsfind_slow_requestsdiff_tempo_tracesanalyze_loki_labelsalerting_manage_rulesalerting_manage_silencesalerting_manage_routingcreate_incidentadd_activity_to_incidentgenerate_deeplinkcreate_annotationdelete_annotationcreate_snapshotdelete_snapshotcreate_datasourcecreate_folder
Before we look at the checkout alerts, confirm which Grafana we are on and what this token can read.
We are connected to the production Grafana, org 'Platform', with a read-only view of 14 dashboards and all 6 datasources. The write tools are available, so I will ask before changing anything. Two datasources returned no data for the last hour, so I will check those before trusting empty results.