- Home
- Resources
- Integrations
- Grafana
Claude Grafana connectorWhat Claude can do in your Grafana account.
The Claude Grafana connector exposes 71 tools. 59 read dashboards, data sources, logs, alerts and on-call data, 11 create, change or delete something, and 1 is described nowhere. Here is what Claude can query, what it can touch, and what your install keeps off limits.
Verified Trustpilot reviews · AI, automation & growth agency
What Grafana changes for Claude
Grafana holds your dashboards, Prometheus metrics, Loki logs, alerts and on-call rotations. With the connector, Claude reads them for you while it answers. Ask why checkout latency has been climbing since this morning, and Claude finds the right dashboard, runs the queries and sums up what it sees, without you writing PromQL.
Investigate without hand-writing queries. query_prometheus runs a PromQL query, query_loki_logs digs through logs in LogQL, and find_error_pattern_logs flags unusual error patterns. Claude builds the queries from your question.
Find your way through a sprawl of dashboards. search_dashboards locates the right one, then get_dashboard_summary gives you the gist without loading the whole thing.
Handle alerts and incidents. list_alert_rules shows where each alert rule stands, create_alert_rule adds one, and create_incident opens an incident in Grafana Incident.
What Claude does not do here: it watches nothing on its own. No query fires when a metric spikes at night; you have to ask. The connector is a desktop extension, available in Claude Desktop only. Several tool families are switched off by default in the server, and everything stays bounded by the Grafana service account in use. For a chain that reacts to an alert by itself, the Grafana n8n integration does a different job, automation; the Integrations hub lists the other options.
Vocabulary in one minute
Five words so the rest reads cleanly.
- Connector
- The link you set up once between Claude and your Grafana instance, so Claude can work in it while it answers you.
- Tool
- One named action the connector opens to Claude. Claude picks which to call on its own, and the directory sheet lists each one by name.
- Authorization
- The access you hand Claude on the service. Given once per person, it is withdrawn the same way, from Claude or from the service itself.
- Approval
- The confirmation Claude waits for before it completes an action that would change your account, shown in the chat when it matters.
- MCP
- The shared standard connectors are built on, which is what lets an assistant like Claude talk to an outside service such as Grafana.
Connect Grafana to Claude
- 01
Find Grafana in Claude Desktop
The Grafana connector is a desktop extension: open Claude Desktop's settings, go to Customize, then Connectors, and locate Grafana. On a Team or Enterprise workspace, an Owner or Primary Owner enables the connector for the organization first.
- 02
Connect from the Grafana row
Click Connect on the Grafana row, then sign in to the service in the window it opens itself. The access Claude gets from there is the one this step grants, nothing wider.
- 03
Approve the authorization screen
Read the authorization screen before you accept: it belongs to the service, not Claude, and it sets what the access covers. If the link breaks, use Disconnect and connect again; you can also withdraw access from the service itself.
The 71 tools of the Claude Grafana connector
Grafana gives Claude 71 tools: 59 that read your account, 11 that change something in it, and 1 no official source describes.
Fifty-nine lookup tools, eleven write tools and one name with no description. Names stay exactly as Claude shows them.
- 59 read
- 11 write
- 1 not documented
Tools index
- search_dashboards
- list_datasources
- get_datasource_by_uid
- get_datasource_by_name
- get_dashboard_by_uid
- get_dashboard_summary
- get_dashboard_property
- get_dashboard_panel_queries
- query_prometheus
- query_prometheus_histogram
- list_prometheus_metric_metadata
- list_prometheus_metric_names
- list_prometheus_label_names
- list_prometheus_label_values
- query_loki_logs
- list_loki_label_names
- list_loki_label_values
- query_loki_stats
- query_loki_patterns
- list_alert_rules
- get_alert_rule_by_uid
- list_contact_points
- list_incidents
- get_incident
- list_sift_investigations
- get_sift_investigation
- get_sift_analysis
- find_error_pattern_logs
- find_slow_requests
- list_oncall_schedules
- get_oncall_shift
- get_current_oncall_users
- list_oncall_teams
- list_oncall_users
- list_alert_groups
- get_alert_group
- list_teams
- list_users_by_org
- list_all_roles
- get_role_details
- get_role_assignments
- list_user_roles
- list_team_roles
- get_resource_permissions
- get_resource_description
- list_pyroscope_label_names
- list_pyroscope_label_values
- list_pyroscope_profile_types
- fetch_pyroscope_profile
- generate_deeplink
- get_annotations
- get_annotation_tags
- get_panel_image
- get_assertions
- search_logs
- query_clickhouse
- list_clickhouse_tables
- describe_clickhouse_table
- get_query_examples
What Claude reads (59)
59 toolsFifty-nine tools that look at dashboards, data, logs, alerts, on-call and permissions without touching them.
search_dashboards
Searches the dashboards of your Grafana instance from a few words. It is often Claude's first call, before opening anything at all.
list_datasources
Lists the data sources registered in your instance: Prometheus, Loki, ClickHouse and the rest. Claude then knows which source to query.
get_datasource_by_uid
Opens a data source record from its unique ID. Handy when a dashboard or query cites the ID without the name.
get_datasource_by_name
Fetches a data source by its readable name, to get its type and ID before querying it.
get_dashboard_by_uid
Loads a complete dashboard from its ID, with its full definition.
get_dashboard_summary
Gives a compact summary of a dashboard without loading its full definition, which spares the conversation's context.
get_dashboard_property
Pulls one targeted part of a dashboard through a path expression, without loading the rest.
get_dashboard_panel_queries
Returns, for each panel of a dashboard, its title, its query, and the ID and type of its data source.
query_prometheus
Runs a PromQL query against a Prometheus source and returns the values. Claude can compose the query from your plain-English question.
query_prometheus_histogram
Calculates percentiles from a Prometheus histogram, so you do not have to hand-craft the function yourself.
list_prometheus_metric_metadata
Lists the metadata Prometheus holds on its metrics. Claude gets a better idea of what a metric measures before relying on it.
list_prometheus_metric_names
Returns the metric names available on a Prometheus source.
list_prometheus_label_names
Returns Prometheus label names matching a selector, such as service, region or environment.
list_prometheus_label_values
Gives the values a specific Prometheus label takes, for instance every region or every instrumented service.
query_loki_logs
Queries Loki in LogQL, either to read log lines or to compute a metric from them.
list_loki_label_names
Lists every label name available in Loki logs, so Claude knows how to filter before it runs a log query.
list_loki_label_values
Shows the values of a given Loki log label, for example the list of applications present in the logs.
query_loki_stats
Provides statistics on Loki log streams rather than the lines themselves. A way to measure before reading.
query_loki_patterns
Surfaces recurring patterns detected in Loki logs, to spot repeated structures without reading everything.
list_alert_rules
Lists the alert rules configured in your Grafana instance. Claude gets the overall picture before opening a single rule.
get_alert_rule_by_uid
Opens one alert rule in full from its ID, once Claude has spotted it in the list.
list_contact_points
Lists notification contact points, both those Grafana manages and those of an external Alertmanager. Claude sees where each notification is meant to land.
list_incidents
Lists incidents from Grafana Incident. The Viewer role is enough for this lookup. It gives the overall picture first.
get_incident
Retrieves one Grafana Incident record by its ID, with its details.
list_sift_investigations
Returns the list of Sift investigations, Grafana's automated error and performance analysis, with an optional result limit. It is the entry point to Sift.
get_sift_investigation
Loads an existing Sift investigation from its unique ID, so Claude can go through it with you.
get_sift_analysis
Pulls one specific analysis inside a Sift investigation, to go deep on a single line of inquiry. It keeps the answer on one angle.
find_error_pattern_logs
Uses Sift to detect error patterns rising abnormally in Loki logs.
find_slow_requests
Relies on Sift to spot slow requests in the relevant Tempo trace sources. It works from trace data, not from logs.
list_oncall_schedules
Lists on-call schedules from Grafana OnCall. Each rotation shows up separately.
get_oncall_shift
Details one specific Grafana OnCall shift, picked out by its ID. It is the zoom that follows a look at the schedules.
get_current_oncall_users
Tells you who is on call right now for a given schedule.
list_oncall_teams
Enumerates the teams declared in Grafana OnCall, to scope an on-call question to the right group.
list_oncall_users
Lists the users Grafana OnCall knows about, so Claude can match a name to the right person in a rotation.
list_alert_groups
Lists Grafana OnCall alert groups, with filtering options to narrow the list. It is where Claude starts when you ask what has been firing.
get_alert_group
Opens one OnCall alert group from its ID. You get the full record.
list_teams
Lists every team configured in Grafana. It is an admin tool, switched off by default in the server.
list_users_by_org
Enumerates the users of a Grafana organization. It belongs to the admin tools, off by default. It is a plain roster.
list_all_roles
Lists every role defined in Grafana, so Claude can see what exists before looking at who holds what. Admin tool, off by default in the server.
get_role_details
Details one Grafana role, so you can see what sits behind its name.
get_role_assignments
Lists the assignments of a given role. It answers the question of who, not what.
list_user_roles
Lists the roles assigned to one or more Grafana users.
list_team_roles
For one or more Grafana teams, returns the roles they hold.
get_resource_permissions
Lists the permissions defined on one Grafana resource. Claude sees who can do what on it without clicking through the settings.
get_resource_description
Describes a type of Grafana resource, as seen from the permissions side.
list_pyroscope_label_names
Gives Pyroscope label names matching a selector. Pyroscope is Grafana's continuous profiling tool. It is where profiling questions start.
list_pyroscope_label_values
Returns the values of a Pyroscope label for a given selector, for instance the services being profiled.
list_pyroscope_profile_types
Lists the profile types available in Pyroscope. It frames what you can ask next about an application's performance.
fetch_pyroscope_profile
Fetches a Pyroscope profile in DOT format, a graph format Claude can then read to spot costly functions.
generate_deeplink
Builds exact links to Grafana resources, so Claude does not have to guess URLs.
get_annotations
Retrieves annotations, the markers placed on graphs, with filters to target the ones you need.
get_annotation_tags
Lists the tags used on annotations, with an optional filter. It is a quick sanity check.
get_panel_image
Renders a PNG image of a single panel or of a whole dashboard.
get_assertions
Returns an assertion summary for a given entity, with permissions specific to the plugin involved.
search_logs
Searches logs across ClickHouse and Loki at once, in a single request. Grafana switches it off by default in its server.
query_clickhouse
Fires a SQL query at a ClickHouse source, with Grafana macro substitution. Off by default in the server.
list_clickhouse_tables
Lists the tables in a ClickHouse database. It belongs to the ClickHouse family, disabled by default.
describe_clickhouse_table
Gives a ClickHouse table's schema, with each column's type. Claude can then get a query right the first time.
get_query_examples
Provides sample queries for a data source type, to help Claude phrase a valid query.
What Claude changes (11)
11 toolsEleven tools that act on your instance. No source describes a specific confirmation, so the general rule below applies.
update_dashboard
Approval: see the ruleUpdates an existing dashboard or creates a new one from a complete definition.
create_alert_rule
Approval: see the ruleCreates a new alert rule in Grafana from what you describe.
update_alert_rule
Approval: see the ruleModifies an alert rule that already exists in Grafana.
delete_alert_rule
Approval: see the ruleDeletes an alert rule from its ID.
create_incident
Approval: see the ruleOpens an incident in Grafana Incident straight from the conversation.
add_activity_to_incident
Approval: see the ruleAdds an activity item to a Grafana Incident record, to keep a trace of the ongoing investigation.
create_annotation
Approval: see the rulePlaces a new annotation on a dashboard or panel, to mark an event on the graphs.
create_graphite_annotation
Approval: see the ruleCreates an annotation in the Graphite format rather than Grafana's usual one.
update_annotation
Approval: see the ruleReplaces every field of an existing annotation: a full update.
patch_annotation
Approval: see the ruleEdits only some fields of an annotation, leaving the others alone.
create_folder
Approval: see the ruleGrafana lists this tool among the write operations on folders that its read-only mode disables. Its documentation says nothing more about it.
Undocumented (1)
1 toolThe directory publishes this name and nothing else. No official source says what it does, and a name is not a description.
search_folders
This name appears on the directory sheet, but no version of Grafana's documentation we checked describes it. No official source says whether it reads or acts. Only the name is published.
What Claude checks with you first
By default, Claude stops and asks before any action it takes on an account on your behalf. With Grafana, that concerns the eleven write tools.
On a Team or Enterprise workspace, owners decide whether members can let some actions through without being asked again. They can also cap what a connector does for the whole organization, for instance keep reading and block writing, and nobody overrides that from their own account. On the Grafana side, two more locks exist: the server can run in read-only mode, which removes the write tools, and Claude inherits the rights of the configured service account. The official per-tool labels only appear in the settings of a connected account.
Which Claude plans include Grafana
None of the 819 directory sheets shows plan availability. Connector by connector, that information is not published anywhere.
The general rule is public: remote connectors are open to all users on Claude, Cowork, Claude Desktop and mobile, and desktop extensions such as Grafana's install on Claude Desktop. On Team and Enterprise, an Owner or Primary Owner enables the connector for the organization before its members. For Grafana's current status on your account, check its sheet in the official directory.
Where the Grafana connector stops
A connector is not an automation. Claude calls these tools while it answers you, so nothing fires when an alert goes off.
Only the publisher documents this connector: neither Claude's help center nor Anthropic's developer docs have a page on it, and the limits below come from Grafana's repository. The tool list is an observed floor, since an admin can open actions no public sheet shows. The partner badge is not a security audit, and Anthropic notes on every sheet that it does not pick a publisher's tools or vouch for how they behave. The directory sheet also tracks an older version of the server: several tools have since been renamed or merged on Grafana's side.
Need help connecting Grafana to Claude?
A person reads every message.
