mcp/grafana repository overview

⁠Grafana MCP Server

MCP server for Grafana.

What is an MCP Server?⁠

⁠MCP Info

⁠Image Building Info

⁠Available Tools (65)

---

⁠Tools Details

⁠Tool: add_activity_to_incident

Add a note (userNote activity) to an existing incident's timeline using its ID. The note body can include URLs which will be attached as context. Use this to add context to an incident.

---

⁠Tool: alerting_manage_routing

Manage Grafana alerting routing configuration, including notification policies, contact points and time intervals.

Notification policies define how alerts are grouped, routed, and which contact points receive them. Time intervals define active/mute periods for alert notifications.

When to use:

• Understanding how alerts are routed to contact points/receivers
• Debugging why an alert went to a specific receiver
• Checking grouping, timing, or mute interval settings

When NOT to use:

• Checking alert rule configuration or state (use alerting_manage_rules) Parameters|Type|Description -|-|- operation|string|The operation to perform: 'get_notification_policies' to retrieve the notification policy tree, 'get_contact_points' to list all contact points, 'get_contact_point' to get a specific contact point by name, 'get_time_intervals' to list all time intervals, 'get_time_interval' to get a specific time interval by name contact_point_title|string optional|Title of the contact point to retrieve (required for get_contact_point operation) datasource_uid|string optional|Optional: UID of an Alertmanager-compatible datasource to query for receivers. If omitted, returns Grafana-managed contact points. Only used with get_contact_points. limit|integer optional|The maximum number of results to return. Default is 100. Only used with get_contact_points. name|string optional|Filter contact points by name (exact match). Only used with get_contact_points. time_interval_name|string optional|Name of the time interval to retrieve (required for get_time_interval operation)

This tool is read-only. It does not modify its environment.

---

⁠Tool: alerting_manage_rules

Manage Grafana alert rules with full CRUD capabilities and filtering.

When to use:

• Understanding why an alert is or isn't firing
• Auditing alert rule configuration (queries, conditions, labels, notification settings)
• Finding alert rules by state, folder, group, or name
• Creating, updating, or deleting alert rules
• Comparing rule versions to see what changed

When NOT to use:

• Checking how alerts are routed to receivers (use alerting_manage_routing) Parameters|Type|Description -|-|- operation|string|The operation to perform: 'list', 'get', 'versions', 'create', 'update', or 'delete'. To create a rule, use operation 'create' and provide all required fields in a single call. To update a rule, first use 'get' to retrieve its full configuration, then 'update' with all required fields plus your changes. annotations|object optional|Optional annotations for the alert rule condition|string optional|The query condition identifier, e.g. 'A', 'B' (required for 'create', 'update') data|array optional|Array of alert query objects (required for 'create'/'update'). Each object has: datasourceUid (string, required), model (object with expr for data queries or type/expression/conditions for expressions), refId (string, auto-assigned if omitted), relativeTimeRange ({from, to} in seconds, defaults to {from:600,to:0}). For server-side expressions use datasourceUid 'expr'. Example: [{datasourceUid: 'prometheus', model: {expr: 'up == 0'}}, {datasourceUid: 'expr', model: {type: 'threshold', expression: 'A', conditions: [{evaluator: {type: 'gt', params: [0]}}]}}] datasource_uid|string optional|Optional: UID of a Prometheus or Loki datasource to query for datasource-managed alert rules (for 'list' operation) disable_provenance|boolean optional|If true, the alert remains editable in the Grafana UI (sets X-Disable-Provenance header). Defaults to true. exec_err_state|string optional|State on execution error: NoData, Alerting, OK (required for 'create', 'update') folder_uid|string optional|The folder UID. For 'list': filter by exact folder UID (mutually exclusive with search_folder). For 'create'/'update': the folder to store the rule in (required). for|string optional|Duration before alert fires, e.g. '5m' (required for 'create', 'update') is_paused|boolean optional|If true, the alert rule remains inactive, Default is false keep_firing_for|string optional|Enables continous firing of alert for specified time even when condition is no longer met. Default is 0 (resolves immediately) label_selectors|array optional|Prometheus-style selectors to filter alert rules by labels. Each string is a selector e.g. '{severity="critical", team=~"backend."}'. All selectors must match (AND). labels|object optional|Optional labels for the alert rule limit_alerts|integer optional|Limit alert instances per rule. For list: 0 omits alerts. For get: <=0 defaults to 200. Max 200. matchers|array optional|Label matchers to filter alert instances. Each string is a Prometheus-style matcher e.g. 'severity="critical"', 'env!="dev"', 'team=~"backend."'. Requires Grafana 12.4+. missing_series_evals_to_resolve|integer optional|Consecutive evaluation intervals with no data required to mark the alert as resolved. Default is 2. no_data_state|string optional|State when no data: NoData, Alerting, OK (required for 'create', 'update') notification_settings|object optional|Notification settings object. Fields: receiver (string, required), groupBy ([]string), groupWait/groupInterval/repeatInterval (duration strings), muteTimeIntervals/activeTimeIntervals ([]string). org_id|integer optional|The organization ID (required for 'create', 'update') record|object optional|Recording rule config. Fields: from (string, required - ref ID e.g. 'A'), metric (string, required - metric name), targetDatasourceUid (string, optional). rule_group|string optional|The rule group name (required for 'create', 'update') rule_limit|integer optional|Maximum number of rules to return (default 200, max 200). Requires Grafana 12.4+ (for 'list' operation) rule_type|string optional|Filter by rule type (for 'list' operation) rule_uid|string optional|The UID of the alert rule (required for 'get', 'versions', 'update', 'delete'; optional for 'create') search_folder|string optional|Search folders by path using partial matching (for 'list' operation). Requires Grafana 12.4+. Mutually exclusive with folder_uid. search_rule_name|string optional|Search alert rule names/titles using partial matching. Requires Grafana 12.4+ (for 'list' operation) states|array optional|Filter by alert state: firing, pending, normal, recovering, nodata, error (for 'list' operation) title|string optional|The title of the alert rule (required for 'create', 'update')

This tool may perform destructive updates.

---

⁠Tool: analyze_loki_labels

Audits a Loki label strategy and optionally diagnoses query performance. Returns per-label verdicts, missing base labels, normalisation issues, and a recommended set. Pass datasourceUid for live cardinality or labels for static scoring; both may be combined.

This tool is read-only. It does not modify its environment.

---

⁠Tool: check_datasources_health

Check datasource health. Filter by type or UIDs; omit both to check all.

This tool is read-only. It does not modify its environment.

---

⁠Tool: create_annotation

Create a new annotation on a dashboard or panel. Set format to 'graphite' and provide 'what' for Graphite-format annotations.

---

⁠Tool: create_datasource

Create a datasource. If type is ambiguous, call search_plugin_information first; install the plugin if needed. IMPORTANT: always call this tool twice. First call: provide only the type — the tool returns a field schema. After receiving the schema, you MUST ask the user for every required field value explicitly; do not infer or use defaults without user confirmation. Second call: provide the type, the display name in the top-level name argument, schemaReviewed=true, and the fields map populated with values confirmed by the user. Never handle credentials — remind the user to rotate any detected. Returns UID, health check, and a config page link.

---

⁠Tool: create_folder

Create a Grafana folder. Provide a title and optional UID. Returns the created folder.

---

⁠Tool: create_incident

Create a new Grafana incident. Requires title, severity, and room prefix. Allows setting status and labels. This tool should be used judiciously and sparingly, and only after confirmation from the user, as it may notify or alarm lots of people.

---

⁠Tool: create_snapshot

Create a Grafana snapshot from a full dashboard payload. Supports optional expiration and external snapshot fields.

---

⁠Tool: delete_snapshot

Delete a Grafana snapshot by snapshot key.

This tool may perform destructive updates.

---

⁠Tool: find_error_pattern_logs

Searches Loki logs for elevated error patterns compared to the last day's average, waits for the analysis to complete, and returns the results including any patterns found.

This tool is read-only. It does not modify its environment.

---

⁠Tool: find_slow_requests

Searches relevant Tempo datasources for slow requests, waits for the analysis to complete, and returns the results.

This tool is read-only. It does not modify its environment.

---

⁠Tool: generate_deeplink

Generate deeplink URLs for Grafana resources. Supports dashboards (requires dashboardUid or provisioningPreview), panels (requires dashboardUid or provisioningPreview, plus panelId), and Explore queries (requires datasourceUid and optionally queries). For dashboard and panel links, provisioningPreview points at a dashboard staged on a provisioning repository branch (e.g. a git-sync PR preview). For explore links, the time range and queries are embedded inside the Grafana explore state. Set shorten=true to also attempt a /goto/ short URL; if shortening fails, the full deeplink is returned.

---

⁠Tool: get_alert_group

Get a specific alert group from Grafana OnCall by its ID. Returns the full alert group details.

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_annotation_tags

Returns annotation tags with optional filtering by tag name. Only the provided filters are applied.

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_annotations

Fetch Grafana annotations using filters such as dashboard UID, time range and tags.

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_assertions

Get assertion summary for a given entity with its type, name, env, site, namespace, and a time range

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_current_oncall_users

Get the list of users currently on-call for a specific Grafana OnCall schedule ID. Returns the schedule ID, name, and a list of detailed user objects for those currently on call.

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_dashboard_by_uid

Retrieves the complete dashboard, including panels, variables, and settings, for a specific dashboard identified by its UID. The response includes 'apiVersion' and 'isV2': when 'isV2' is true the dashboard uses the v2 schema (panels live under 'elements' keyed by name, arranged by 'layout'; variables under 'variables'), otherwise it is classic v1 ('panels[]' with 'templating.list'). WARNING: Large dashboards can consume significant context window space. Consider using get_dashboard_summary for overview or get_dashboard_property for specific data instead.

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_dashboard_panel_queries

Retrieve panel queries from a Grafana dashboard. Supports all datasource types (Prometheus, Loki, CloudWatch, SQL, etc.) and row-nested panels. Optionally filter to a specific panel by ID with panelId. Optionally provide variables for template variable substitution, which populates processedQuery and requiredVariables fields. Returns an array of objects with fields: title, query (raw expression), datasource (object with uid and type), and optionally processedQuery, refId, and requiredVariables.

This tool is read-only. It does not modify its environment.

---

⁠Tool: get_dashboard_property

Get specific parts of a dashboard using JSONPath expressions to minimize context window usage. JSONPath targets the dashboard's native schema. Classic v1 paths: '$.title' (title), '$.panels[].title' (all panel titles), '$.panels[0]' (first panel), '$.templating.list' (variables), '$.annotations.list' (saved dashboard annotation queries/definitions), '$.tags' (tags), '$.panels[].targets[*].expr' (all queries). v2 dashboards (see isV2 from get_dashboard_by_uid) use different paths: '$.title', '$.elements' (panels, keyed by name), '$.variables' (variables), '$.annotations'. Use this instead of get_dashboard_by_uid when you only need specific d

[...]