Grafana

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.

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)

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)

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.

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

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

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.

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

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.

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

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|stringoptional|Title of the contact point to retrieve (required for get_contact_point operation) datasource_uid|stringoptional|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|integeroptional|The maximum number of results to return. Default is 100. Only used with get_contact_points. name|stringoptional|Filter contact points by name (exact match). Only used with get_contact_points. time_interval_name|stringoptional|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|objectoptional|Optional annotations for the alert rule condition|stringoptional|The query condition identifier, e.g. 'A', 'B' (required for 'create', 'update') data|arrayoptional|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|stringoptional|Optional: UID of a Prometheus or Loki datasource to query for datasource-managed alert rules (for 'list' operation) disable_provenance|booleanoptional|If true, the alert remains editable in the Grafana UI (sets X-Disable-Provenance header). Defaults to true. exec_err_state|stringoptional|State on execution error: NoData, Alerting, OK (required for 'create', 'update') folder_uid|stringoptional|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|stringoptional|Duration before alert fires, e.g. '5m' (required for 'create', 'update') is_paused|booleanoptional|If true, the alert rule remains inactive, Default is false keep_firing_for|stringoptional|Enables continous firing of alert for specified time even when condition is no longer met. Default is 0 (resolves immediately) label_selectors|arrayoptional|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|objectoptional|Optional labels for the alert rule limit_alerts|integeroptional|Limit alert instances per rule. For list: 0 omits alerts. For get: <=0 defaults to 200. Max 200. matchers|arrayoptional|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|integeroptional|Consecutive evaluation intervals with no data required to mark the alert as resolved. Default is 2. no_data_state|stringoptional|State when no data: NoData, Alerting, OK (required for 'create', 'update') notification_settings|objectoptional|Notification settings object. Fields: receiver (string, required), groupBy ([]string), groupWait/groupInterval/repeatInterval (duration strings), muteTimeIntervals/activeTimeIntervals ([]string). org_id|integeroptional|The organization ID (required for 'create', 'update') record|objectoptional|Recording rule config. Fields: from (string, required - ref ID e.g. 'A'), metric (string, required - metric name), targetDatasourceUid (string, optional). rule_group|stringoptional|The rule group name (required for 'create', 'update') rule_limit|integeroptional|Maximum number of rules to return (default 200, max 200). Requires Grafana 12.4+ (for 'list' operation) rule_type|stringoptional|Filter by rule type (for 'list' operation) rule_uid|stringoptional|The UID of the alert rule (required for 'get', 'versions', 'update', 'delete'; optional for 'create') search_folder|stringoptional|Search folders by path using partial matching (for 'list' operation). Requires Grafana 12.4+. Mutually exclusive with folder_uid. search_rule_name|stringoptional|Search alert rule names/titles using partial matching. Requires Grafana 12.4+ (for 'list' operation) states|arrayoptional|Filter by alert state: firing, pending, normal, recovering, nodata, error (for 'list' operation) title|stringoptional|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 dashboard properties.

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

Tool: get_dashboard_summary

Get a compact summary of a dashboard including title, panel count, panel types, variables, and other metadata without the full JSON. Use this for dashboard overview and planning modifications without consuming large context windows.

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

Tool: get_datasource

Retrieves detailed information about a specific datasource by UID or name. Returns the full datasource model, including name, type, URL, access settings, JSON data, and secure JSON field status. Provide either uid or name; uid takes priority if both are given.

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

Tool: get_incident

Get a single incident by ID. Returns the full incident details including title, status, severity, labels, timestamps, and other metadata.

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

Tool: get_oncall_shift

Get detailed information for a specific Grafana OnCall shift using its ID. A shift represents a designated time period within a schedule when users are actively on-call. Returns the full shift details.

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

Tool: get_panel_image

Render a Grafana dashboard panel or full dashboard as a PNG image. Returns the image as base64 encoded data. Requires the Grafana Image Renderer service to be installed. Either dashboardUid (for stored dashboards) or provisioningPreview (for dashboards staged on a provisioning repository branch, e.g. a git-sync PR) must be supplied. Use this for generating visual snapshots of dashboards for reports, alerts, or presentations.

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

Tool: get_plugin

Check whether a Grafana plugin is installed and retrieve its details (name, version, type, enabled status). Returns installed=false when the plugin is not found. Use install_plugin when a plugin is not installed to install plugin after confirming this action with the user.

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

Tool: get_sift_analysis

Retrieves a specific analysis from an investigation by its UUID. The investigation ID and analysis ID should be provided as strings in UUID format.

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

Tool: get_sift_investigation

Retrieves an existing Sift investigation by its UUID. The ID should be provided as a string in UUID format (e.g. '02adab7c-bf5b-45f2-9459-d71a2c29e11b').

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

Tool: get_snapshot

Get a Grafana snapshot by key, including snapshot metadata and dashboard payload.

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

Tool: grafana_api_request

Make an authenticated HTTP request to the Grafana API. Similar to 'gh api' for GitHub. Supports any Grafana API endpoint with optional jq-style response filtering. Use this for API endpoints that don't have a dedicated tool.

Tool: install_plugin

Install a Grafana plugin by its plugin ID. If the version is not already confirmed with the user, omit it — the tool will look up the latest version and return it for confirmation before installing.

This tool may perform destructive updates.

Tool: list_alert_groups

List alert groups from Grafana OnCall with filtering options. Supports filtering by alert group ID, route ID, integration ID, state (new, acknowledged, resolved, silenced), team ID, time range, labels, and name. For time ranges, use format '{start}_{end}' ISO 8601 timestamp range (e.g., '2025-01-19T00:00:00_2025-01-19T23:59:59' for a specific day). For labels, use format 'key:value' (e.g., ['env:prod', 'severity:high']). Returns a list of alert group objects with their details. Supports pagination.

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

Tool: list_datasources

List all configured datasources in Grafana. Use this to discover available datasources and their UIDs. Supports filtering by type and pagination.

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

Tool: list_incidents

List Grafana incidents. Allows filtering by status ('active', 'resolved') and optionally including drill incidents. Returns a preview list with basic details.

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

Tool: list_loki_label_names

Lists all available label/field names (keys) found in logs within a specified Loki or VictoriaLogs datasource and time range. Returns a list of unique label strings (e.g., ["app", "env", "pod"]). If the time range is not provided, it defaults to the last hour.

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

Tool: list_loki_label_values

Retrieves all unique values associated with a specific labelName within a Loki or VictoriaLogs datasource and time range. Returns a list of string values (e.g., for labelName="env", might return ["prod", "staging", "dev"]). Useful for discovering filter options. Defaults to the last hour if the time range is omitted.

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

Tool: list_oncall_schedules

List Grafana OnCall schedules, optionally filtering by team ID. If a specific schedule ID is provided, retrieves details for only that schedule. Returns a list of schedule summaries including ID, name, team ID, timezone, and shift IDs. Supports pagination.

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

Tool: list_oncall_teams

List teams configured in Grafana OnCall. Returns a list of team objects with their details. Supports pagination.

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

Tool: list_oncall_users

List users from Grafana OnCall. These are OnCall users (separate from Grafana users). Can retrieve all users in the OnCall directory, a specific user by ID, or filter by username. Returns a list of user objects with their details. Supports pagination.

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

Tool: list_prometheus_label_names

List label names in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Allows filtering by series selectors and time range.

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

Tool: list_prometheus_label_values

Use after list_prometheus_metric_names to find label values for filtering queries. Gets the values for a specific label name in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Allows filtering by series selectors and time range.

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

Tool: list_prometheus_metric_metadata

List Prometheus metric metadata. Returns metadata about metrics currently scraped from targets. Note: This endpoint is experimental.

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

Tool: list_prometheus_metric_names

DISCOVERY: Call this first to find available metrics before querying. Lists metric names in a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.). Retrieves all metric names and filters them using the provided regex. Supports pagination and an optional time range to restrict results to metrics active within that window.

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

Tool: list_provisioning_repositories

List provisioning repositories (e.g. git-sync sources) configured for this Grafana instance. Returns each repository's slug along with its source URL, branch, path, sync state, and health. Use the returned name as the repo argument when rendering a not-yet-applied dashboard preview via get_panel_image's provisioningPreview parameter.

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

Tool: list_pyroscope_label_names

Lists all available label names (keys) found in profiles within a specified Pyroscope datasource, time range, and optional label matchers. Label matchers are typically used to qualify a service name ({service_name="foo"}). Returns a list of unique label strings (e.g., ["app", "env", "pod"]). Label names with double underscores (e.g. name) are internal and rarely useful to users. If the time range is not provided, it defaults to the last hour.

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

Tool: list_pyroscope_label_values

Lists all available label values for a particular label name found in profiles within a specified Pyroscope datasource, time range, and optional label matchers. Label matchers are typically used to qualify a service name ({service_name="foo"}). Returns a list of unique label strings (e.g. for label name "env": ["dev", "staging", "prod"]). If the time range is not provided, it defaults to the last hour.

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

Tool: list_pyroscope_profile_types

Lists all available profile types available in a specified Pyroscope datasource and time range. Returns a list of all available profile types (example profile type: "process_cpu:cpu:nanoseconds:cpu:nanoseconds"). A profile type has the following structure: ::::. Not all profile types are available for every service. If the time range is not provided, it defaults to the last hour.

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

Tool: list_sift_investigations

Retrieves a list of Sift investigations with an optional limit. If no limit is specified, defaults to 10 investigations.

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

Tool: list_snapshots

List Grafana dashboard snapshots with optional query and result limit filters.

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

Tool: query_loki_logs

Executes a log query against a Loki or VictoriaLogs datasource and returns matching log entries (or metric samples on Loki). Defaults to the last hour, a limit of 10 entries, and 'backward' direction (newest first). The logql parameter takes LogQL on Loki and LogsQL on VictoriaLogs (e.g., Loki: {app="foo"} |= "error"; VictoriaLogs: {app="foo"} "error"). To count matching log lines precisely, use a count_over_time() metric query with queryType='instant'. Prefer using query_loki_stats first to cheaply check whether a stream contains data (avoiding expensive queries against empty streams) and list_loki_label_names / list_loki_label_values to verify labels exist before querying. Note: query_loki_stats returns approximate storage-level counts, not exact log line counts.

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

Tool: query_loki_patterns

Retrieves detected log patterns from a Loki datasource for a given stream selector and time range. Returns a list of patterns, each containing a pattern string and a total count of occurrences. Patterns help identify common log structures and anomalies. The logql parameter must be a stream selector (e.g., {job="nginx"}) and does not support line filters or aggregations. Defaults to the last hour if the time range is omitted. Not supported on VictoriaLogs datasources - use a | stats pipeline instead.

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

Tool: query_loki_stats

Retrieves index-level statistics about log streams matching a given selector within a Loki or VictoriaLogs datasource and time range. Returns an object containing the count of streams, chunks, entries, and total bytes (e.g., {"streams": 5, "chunks": 50, "entries": 10000, "bytes": 512000}). Important: the entries count reflects storage-level index entries (chunk metadata), NOT the number of individual log lines matching the selector. To count actual matching log lines, use query_loki_logs with a count_over_time() metric query instead. On VictoriaLogs only entries is populated; the other fields remain zero. The logql parameter must be a simple label selector (e.g., {app="nginx", env="prod"}) and does not support line filters, parsers, or aggregations. Defaults to the last hour if the time range is omitted.

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

Tool: query_prometheus

WORKFLOW: list_prometheus_metric_names -> list_prometheus_label_values -> query_prometheus. Query a PromQL-compatible datasource (Prometheus, Thanos, Mimir, Cloud Monitoring, etc.) using a PromQL expression. Supports instant queries (single point) and range queries (time range). Time: RFC3339 or relative expressions like 'now', 'now-1h'.

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

Tool: query_prometheus_histogram

Query Prometheus histogram percentiles. DISCOVER FIRST: Use list_prometheus_metric_names with regex='.*_bucket$' to find histograms.

Generates histogram_quantile PromQL. Example: metric='http_duration', percentile=95, labels='job="api"'

Time formats: 'now-1h', '2026-02-02T19:00:00Z', '1738519200000' (Unix ms)

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

Tool: query_pyroscope

Unified Pyroscope query tool for fetching profiles or metrics from Pyroscope. Profile data shows WHICH functions consume resources; metrics data shows WHEN consumption spiked. Use query_type="both" for complete analysis in one call.

query_type options (extends Grafana's PyroscopeQueryType):

• "profile": returns DOT-format call graph
• "metrics": returns time-series data points
• "both" (default): returns both profile and metrics in one response Parameters|Type|Description -|-|- data_source_uid|string|The UID of the datasource to query profile_type|string|The profile type, use list_pyroscope_profile_types to discover available types end_rfc_3339|stringoptional|End time in RFC3339 or relative time (e.g. 'now') (defaults to now) group_by|arrayoptional|Labels to group metrics series by matchers|stringoptional|Prometheus style matchers (defaults to: {}) max_node_depth|integeroptional|Max depth for profile call graph (default: 100) query_type|stringoptional|Query type: "profile" (flamegraph), "metrics" (time-series), or "both" (default). Use "both" for complete analysis start_rfc_3339|stringoptional|Start time in RFC3339 or relative time (e.g. 'now-1h') (defaults to 1 hour ago) step|numberoptional|Seconds between metrics data points (default: auto)

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

Tool: search_dashboards

Search for Grafana dashboards by a query string. Returns a list of matching dashboards with details like title, UID, folder, tags, and URL.

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

Tool: search_folders

Search for Grafana folders by a query string. Returns matching folders with details like title, UID, and URL.

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

Tool: search_plugin_information

Search the Grafana plugin catalog by keyword to discover available plugins before installing or getting plugin details on a specific instance. Returns results sorted by trust: official Grafana Labs plugins first, then commercial partner plugins, then community plugins. Use this tool when a user describes a plugin by purpose or partial name (e.g. 'azure monitoring', 'loki', 'database') — it returns the exact pluginId to pass to get_plugin or install_plugin. Results include warnings for enterprise-only or Angular-based plugins.

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

Tool: suggest_loki_alloy_label_config

Generates an Alloy loki.process snippet enforcing an approved label set via stage.label_keep, with optional log-level normalisation and soft-enforcement placeholders.

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

Tool: update_annotation

Updates the provided properties of an annotation by ID. Only fields included in the request are modified; omitted fields are left unchanged.

This tool may perform destructive updates.

Tool: update_dashboard

Create or update a dashboard. Two modes: (1) Full JSON — provide 'dashboard' for new dashboards or complete replacements. (2) Patch — provide 'uid' + 'operations' to make targeted changes to an existing dashboard. One of these two modes is required; 'folderUid', 'message', and 'overwrite' are supplementary and do nothing on their own. Dashboard authoring guidance: if a saved query must support one, many, or All values from a multi-select variable inside a regex expression or matcher, save '${var:regex}' rather than plain '$var'. Saved dashboard annotation queries/definitions must be written into dashboard JSON under 'annotations.list'; the create_annotation tool creates annotation events and does not add a reusable dashboard annotation query/definition to the saved dashboard. For stat panels over the current dashboard range, make the query return the range-level result the stat should display; panel-side reduction only reduces returned series and does not compute peak-over-range or ratio-of-peaks semantics for you. Patch operations support JSONPaths like '$.panels[0].targets[0].expr', '$.panels[1].title', '$.panels[2].targets[0].datasource', '$.templating.list/-', and '$.annotations.list/-'. Append to arrays with '/- ' syntax: '$.panels/- '. Remove by index: {"op": "remove", "path": "$.panels[2]"}. Multiple removes on the same array are automatically reordered to avoid index-shifting issues. Note: only numeric array indices are supported in patch paths; filter expressions like [?(@.id==2)] and wildcards like [*] are not supported. v2 dashboards (check 'isV2' from get_dashboard_by_uid) use a different shape: patch '$.elements..spec.title' or '$.elements..spec.data.spec.queries[0].spec' and edit '$.variables'/'$.layout' rather than '$.panels'/'$.templating.list'. Full-JSON saves containing top-level 'elements'/'layout' are written as v2 and require a Kubernetes-capable Grafana. After creating or updating a dashboard, verify that panel queries return data by using run_panel_query or the appropriate query tool (query_prometheus, query_loki_logs, etc.) to validate expressions before considering the task complete.

This tool may perform destructive updates.

Tool: update_datasource

Update non-secret datasource fields by UID. Omitted fields are preserved. For secrets, direct the user to the Grafana UI.

Tool: validate_provisioning_file

Validate a file in a provisioning repository at a given branch or commit by dry-run applying it. Returns whether the file would be accepted (valid), what resource action would result (create/update), the target resource type, and any structured validation errors. Use to confirm a draft dashboard or other resource will be accepted before merging or applying a PR — this is the same validation surface that Grafana's PR commenter reports.

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

Use this MCP Server

{
 "mcpServers": {
 "grafana": {
 "command": "docker",
 "args": [
 "run",
 "-i",
 "--rm",
 "-e",
 "GRAFANA_URL",
 "-e",
 "GRAFANA_API_KEY",
 "mcp/grafana",
 "--transport=stdio"
 ],
 "env": {
 "GRAFANA_URL": "http://localhost:3000",
 "GRAFANA_API_KEY": "<your service account token>"
 }
 }
 }
}

Why is it safer to run MCP Servers with Docker?⁠