Resources · Claude connector

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

Overview

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

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

Connect Grafana to Claude

  1. 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.

  2. 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.

  3. 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.

Tools

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

What Claude reads (59)

59 tools

Fifty-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.

When it helps
you need the payments API dashboard and have no idea which folder it sits in.
Watch out
only dashboards the service account can see come back.

Sourcegithub.com · September 30, 2026 ↗

list_datasources

Lists the data sources registered in your instance: Prometheus, Loki, ClickHouse and the rest. Claude then knows which source to query.

When it helps
you inherited an instance and want to know which metric and log stores are plugged in.
Watch out
it lists sources, it does not test them.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
a panel throws an error and you want to know which source it really points at.
Watch out
the ID usually comes from a dashboard or the source list first.

Sourcegithub.com · September 30, 2026 ↗

get_datasource_by_name

Fetches a data source by its readable name, to get its type and ID before querying it.

When it helps
you know the source is called prod-metrics and want Claude to query it directly.
Watch out
a misspelled name returns nothing, so check the list if in doubt.

Sourcegithub.com · September 30, 2026 ↗

get_dashboard_by_uid

Loads a complete dashboard from its ID, with its full definition.

When it helps
you want Claude to review every panel of a dashboard before a redesign.
Watch out
Grafana warns that a large dashboard can eat a big share of the conversation's context; the summary is often enough.

Sourcegithub.com · September 30, 2026 ↗

get_dashboard_summary

Gives a compact summary of a dashboard without loading its full definition, which spares the conversation's context.

When it helps
seeing at a glance what a dashboard covers before digging in.
Watch out
for the queries behind each panel, another tool goes further.

Sourcegithub.com · September 30, 2026 ↗

get_dashboard_property

Pulls one targeted part of a dashboard through a path expression, without loading the rest.

When it helps
you only want the dashboard's variables to understand its filters.
Watch out
the path has to match the dashboard's structure, so Claude often reads the summary first.

Sourcegithub.com · September 30, 2026 ↗

get_dashboard_panel_queries

Returns, for each panel of a dashboard, its title, its query, and the ID and type of its data source.

When it helps
understanding where a displayed figure comes from before quoting it in a meeting.
Watch out
it shows the queries, it does not run them.

Sourcegithub.com · September 30, 2026 ↗

query_prometheus

Runs a PromQL query against a Prometheus source and returns the values. Claude can compose the query from your plain-English question.

When it helps
finding the billing service error rate over the past hour.
Watch out
the service account needs query permission on that source.

Sourcegithub.com · September 30, 2026 ↗

query_prometheus_histogram

Calculates percentiles from a Prometheus histogram, so you do not have to hand-craft the function yourself.

When it helps
getting a high-percentile response time for an API in a performance report.
Watch out
the metric has to exist as a histogram in the first place.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
you hit a metric with a cryptic name and want to know what it counts.
Watch out
sparse metadata means sparse answers.

Sourcegithub.com · September 30, 2026 ↗

list_prometheus_metric_names

Returns the metric names available on a Prometheus source.

When it helps
checking whether a queue depth metric already exists before asking the platform team for a new one.
Watch out
on a large instance the list can run long, so narrow your question.

Sourcegithub.com · September 30, 2026 ↗

list_prometheus_label_names

Returns Prometheus label names matching a selector, such as service, region or environment.

When it helps
knowing which dimensions you can slice a metric by before framing your question.
Watch out
an overly broad selector brings back a lot of noise.

Sourcegithub.com · September 30, 2026 ↗

list_prometheus_label_values

Gives the values a specific Prometheus label takes, for instance every region or every instrumented service.

When it helps
confirming the new service reports its metrics under the expected name.
Watch out
a missing value can point to a collection problem.

Sourcegithub.com · September 30, 2026 ↗

query_loki_logs

Queries Loki in LogQL, either to read log lines or to compute a metric from them.

When it helps
pulling the auth service errors from just before this morning's incident.
Watch out
without a tight time window, the volume can swamp the conversation.

Sourcegithub.com · September 30, 2026 ↗

list_loki_label_names

Lists every label name available in Loki logs, so Claude knows how to filter before it runs a log query.

When it helps
you are new to an instance and want to know whether logs are labeled by team or by application.
Watch out
labels only help if they are applied consistently.

Sourcegithub.com · September 30, 2026 ↗

list_loki_label_values

Shows the values of a given Loki log label, for example the list of applications present in the logs.

When it helps
checking that a new container shows up in Loki after its rollout.
Watch out
it says nothing about the volume behind each value.

Sourcegithub.com · September 30, 2026 ↗

query_loki_stats

Provides statistics on Loki log streams rather than the lines themselves. A way to measure before reading.

When it helps
finding which service produces the most logs before you look closely at the storage bill.
Watch out
these are aggregates, not content.

Sourcegithub.com · September 30, 2026 ↗

query_loki_patterns

Surfaces recurring patterns detected in Loki logs, to spot repeated structures without reading everything.

When it helps
identifying the error message that has dominated since the last release.
Watch out
a rare but serious pattern can slip under the radar.

Sourcegithub.com · September 30, 2026 ↗

list_alert_rules

Lists the alert rules configured in your Grafana instance. Claude gets the overall picture before opening a single rule.

When it helps
reviewing active alerts before the on-call handoff.
Watch out
the service account needs read permission on alert rules.

Sourcegithub.com · September 30, 2026 ↗

get_alert_rule_by_uid

Opens one alert rule in full from its ID, once Claude has spotted it in the list.

When it helps
an alert fires too often and you want its exact threshold before discussing it with the team.
Watch out
the ID comes from the rule list first.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
checking which channel critical database alerts go to.
Watch out
it shows configuration, it does not test delivery.

Sourcegithub.com · September 30, 2026 ↗

list_incidents

Lists incidents from Grafana Incident. The Viewer role is enough for this lookup. It gives the overall picture first.

When it helps
preparing the weekly reliability review with this week's incidents.
Watch out
it only covers Grafana Incident, so incidents tracked elsewhere will not show up.

Sourcegithub.com · September 30, 2026 ↗

get_incident

Retrieves one Grafana Incident record by its ID, with its details.

When it helps
you want to reread an incident's timeline before drafting the team's post-mortem.
Watch out
the ID usually comes from the incident list, so check that first.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
finding the investigations launched during the last incident.
Watch out
the Viewer role is enough to browse them.

Sourcegithub.com · September 30, 2026 ↗

get_sift_investigation

Loads an existing Sift investigation from its unique ID, so Claude can go through it with you.

When it helps
reading the conclusions of an investigation a colleague ran overnight.
Watch out
without an ID, go through the investigation list first.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
you want the slow-requests analysis, not the whole investigation.
Watch out
you need to know the parent investigation.

Sourcegithub.com · September 30, 2026 ↗

find_error_pattern_logs

Uses Sift to detect error patterns rising abnormally in Loki logs.

When it helps
right after a release, checking whether a new kind of error has appeared.
Watch out
Grafana says this tool needs the Editor role, even though it only searches.

Sourcegithub.com · September 30, 2026 ↗

find_slow_requests

Relies on Sift to spot slow requests in the relevant Tempo trace sources. It works from trace data, not from logs.

When it helps
users complain about lag and you want to know which call drags.
Watch out
you need Tempo traces, and Grafana requires the Editor role for this tool.

Sourcegithub.com · September 30, 2026 ↗

list_oncall_schedules

Lists on-call schedules from Grafana OnCall. Each rotation shows up separately.

When it helps
a new engineering manager wants every existing rotation before reshaping the team's on-call.
Watch out
your organization has to run Grafana OnCall, and the account needs read access to schedules.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
checking who covered the night of the incident before the debrief.
Watch out
you need the shift ID, usually taken from a schedule.

Sourcegithub.com · September 30, 2026 ↗

get_current_oncall_users

Tells you who is on call right now for a given schedule.

When it helps
an alert lands and you want to know immediately who to ping on the network team.
Watch out
the answer holds for this moment; for next week, look at the schedule.

Sourcegithub.com · September 30, 2026 ↗

list_oncall_teams

Enumerates the teams declared in Grafana OnCall, to scope an on-call question to the right group.

When it helps
you want to know which teams have a formal rotation in OnCall.
Watch out
the account needs read access to OnCall user settings.

Sourcegithub.com · September 30, 2026 ↗

list_oncall_users

Lists the users Grafana OnCall knows about, so Claude can match a name to the right person in a rotation.

When it helps
confirming a new hire is in OnCall before adding them to a rotation.
Watch out
the account needs read access to OnCall user settings, like the teams tool.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
seeing every unresolved alert group since last night.
Watch out
narrow the filters, as the list can grow fast during an alert storm.

Sourcegithub.com · September 30, 2026 ↗

get_alert_group

Opens one OnCall alert group from its ID. You get the full record.

When it helps
you want the details of an alert group that woke the on-call engineer three times this week.
Watch out
get the ID from the alert group list first.

Sourcegithub.com · September 30, 2026 ↗

list_teams

Lists every team configured in Grafana. It is an admin tool, switched off by default in the server.

When it helps
taking an inventory of teams before an access audit.
Watch out
until admin tools are enabled at install time, it stays unavailable.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
spotting accounts that linger after several contractors left.
Watch out
the service account needs read permission on users.

Sourcegithub.com · September 30, 2026 ↗

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.

When it helps
understanding which roles exist before redrawing your access policy.
Watch out
reading roles takes a dedicated permission.

Sourcegithub.com · September 30, 2026 ↗

get_role_details

Details one Grafana role, so you can see what sits behind its name.

When it helps
knowing exactly what a custom role allows before granting it to a team.
Watch out
an admin tool that is disabled by default in the server.

Sourcegithub.com · September 30, 2026 ↗

get_role_assignments

Lists the assignments of a given role. It answers the question of who, not what.

When it helps
an audit asks for everyone holding an admin role.
Watch out
like the other admin tools, it has to be enabled at install time.

Sourcegithub.com · September 30, 2026 ↗

list_user_roles

Lists the roles assigned to one or more Grafana users.

When it helps
checking a colleague's rights when they say a dashboard is invisible to them.
Watch out
an admin tool, unavailable until enabled in the server, and it needs read permission on roles.

Sourcegithub.com · September 30, 2026 ↗

list_team_roles

For one or more Grafana teams, returns the roles they hold.

When it helps
making sure a contractor team has no more rights than planned.
Watch out
part of the admin family, off by default, and it needs read access to roles.

Sourcegithub.com · September 30, 2026 ↗

get_resource_permissions

Lists the permissions defined on one Grafana resource. Claude sees who can do what on it without clicking through the settings.

When it helps
figuring out why a team can see a sensitive folder it should not.
Watch out
an admin tool, off by default, that requires read access to permissions.

Sourcegithub.com · September 30, 2026 ↗

get_resource_description

Describes a type of Grafana resource, as seen from the permissions side.

When it helps
knowing which permissions exist on folders before designing an access model.
Watch out
it also belongs to the admin tools that are disabled by default.

Sourcegithub.com · September 30, 2026 ↗

list_pyroscope_label_names

Gives Pyroscope label names matching a selector. Pyroscope is Grafana's continuous profiling tool. It is where profiling questions start.

When it helps
knowing which dimensions you can slice a CPU profile by.
Watch out
you need a Pyroscope source and permission to query it.

Sourcegithub.com · September 30, 2026 ↗

list_pyroscope_label_values

Returns the values of a Pyroscope label for a given selector, for instance the services being profiled.

When it helps
confirming the new service is profiled before analyzing its memory.
Watch out
a missing value may mean profiling is not active.

Sourcegithub.com · September 30, 2026 ↗

list_pyroscope_profile_types

Lists the profile types available in Pyroscope. It frames what you can ask next about an application's performance.

When it helps
knowing which kinds of profile you can analyze before asking about a slow service.
Watch out
the list depends on what your applications report.

Sourcegithub.com · September 30, 2026 ↗

fetch_pyroscope_profile

Fetches a Pyroscope profile in DOT format, a graph format Claude can then read to spot costly functions.

When it helps
finding the function that devours a service's CPU since the last version.
Watch out
a detailed profile can weigh heavily in the conversation.

Sourcegithub.com · September 30, 2026 ↗

get_annotations

Retrieves annotations, the markers placed on graphs, with filters to target the ones you need.

When it helps
checking whether a release was flagged just before the error spike.
Watch out
only annotations someone actually placed come back; nothing is inferred.

Sourcegithub.com · September 30, 2026 ↗

get_annotation_tags

Lists the tags used on annotations, with an optional filter. It is a quick sanity check.

When it helps
seeing whether your team marks its deployments with a consistent tag before searching a version's annotations.
Watch out
messy tags make annotation searches less reliable.

Sourcegithub.com · September 30, 2026 ↗

get_panel_image

Renders a PNG image of a single panel or of a whole dashboard.

When it helps
dropping a graph into an incident report without a manual screenshot.
Watch out
Grafana requires the Image Renderer service to be installed and configured.

Sourcegithub.com · September 30, 2026 ↗

get_assertions

Returns an assertion summary for a given entity, with permissions specific to the plugin involved.

When it helps
your team uses Grafana assertions and you want their summary for one service ahead of a review.
Watch out
it needs permissions specific to the plugin behind it, not the usual Grafana ones.

Sourcegithub.com · September 30, 2026 ↗

search_logs

Searches logs across ClickHouse and Loki at once, in a single request. Grafana switches it off by default in its server.

When it helps
your logs are split between two systems and you want one search.
Watch out
it has to be enabled when the server is installed.

Sourcegithub.com · September 30, 2026 ↗

query_clickhouse

Fires a SQL query at a ClickHouse source, with Grafana macro substitution. Off by default in the server.

When it helps
counting user journey events stored in ClickHouse.
Watch out
the ClickHouse family must be enabled at install time, or the tool does not show up.

Sourcegithub.com · September 30, 2026 ↗

list_clickhouse_tables

Lists the tables in a ClickHouse database. It belongs to the ClickHouse family, disabled by default.

When it helps
discovering which event tables exist before asking a numbers question.
Watch out
the account needs query permission on the ClickHouse source.

Sourcegithub.com · September 30, 2026 ↗

describe_clickhouse_table

Gives a ClickHouse table's schema, with each column's type. Claude can then get a query right the first time.

When it helps
knowing whether the table stores dates as timestamps or as text.
Watch out
off by default, like every ClickHouse tool.

Sourcegithub.com · September 30, 2026 ↗

get_query_examples

Provides sample queries for a data source type, to help Claude phrase a valid query.

When it helps
you are new to a source whose query language you do not know.
Watch out
the examples show syntax for a source type, not results from your own data.

Sourcegithub.com · September 30, 2026 ↗

What Claude changes (11)

11 tools

Eleven tools that act on your instance. No source describes a specific confirmation, so the general rule below applies.

update_dashboard

Approval: see the rule

Updates an existing dashboard or creates a new one from a complete definition.

What Claude asks for
no confirmation specific to this tool is described, so the general approvals rule applies.
When it helps
adding an error-rate panel to a team dashboard.
Watch out
the complete definition uses a lot of context, according to Grafana.

Sourcegithub.com · September 30, 2026 ↗

create_alert_rule

Approval: see the rule

Creates a new alert rule in Grafana from what you describe.

What Claude asks for
nothing tool-specific is documented, so see the general approvals rule.
When it helps
alerting the team as soon as the processing queue passes an agreed threshold.
Watch out
the account needs write permission on alert rules.

Sourcegithub.com · September 30, 2026 ↗

update_alert_rule

Approval: see the rule

Modifies an alert rule that already exists in Grafana.

What Claude asks for
the docs describe no dedicated confirmation, and the approvals section is the reference.
When it helps
raising the threshold of a chatty alert that wakes on-call for nothing.
Watch out
the server's read-only mode disables this tool.

Sourcegithub.com · September 30, 2026 ↗

delete_alert_rule

Approval: see the rule

Deletes an alert rule from its ID.

What Claude asks for
no source describes a confirmation specific to this deletion; by default, Claude's general rule applies.
When it helps
clearing out the alerts of a decommissioned service.
Watch out
a deleted rule no longer warns anyone, so make sure it is truly obsolete.

Sourcegithub.com · September 30, 2026 ↗

create_incident

Approval: see the rule

Opens an incident in Grafana Incident straight from the conversation.

What Claude asks for
no dedicated rule is documented; see the general approvals rule.
When it helps
declaring an incident as soon as the payments error rate shoots up.
Watch out
Grafana requires the Editor role for this tool.

Sourcegithub.com · September 30, 2026 ↗

add_activity_to_incident

Approval: see the rule

Adds an activity item to a Grafana Incident record, to keep a trace of the ongoing investigation.

What Claude asks for
no source details a confirmation here, and Claude's default behavior is what applies.
When it helps
logging the root cause you found in the incident timeline.
Watch out
Editor role required.

Sourcegithub.com · September 30, 2026 ↗

create_annotation

Approval: see the rule

Places a new annotation on a dashboard or panel, to mark an event on the graphs.

What Claude asks for
nothing specific to this tool is described, so the general approvals rule applies.
When it helps
flagging on the curves the moment of a database failover.
Watch out
the account needs write permission on annotations.

Sourcegithub.com · September 30, 2026 ↗

create_graphite_annotation

Approval: see the rule

Creates an annotation in the Graphite format rather than Grafana's usual one.

What Claude asks for
no specific confirmation is documented; it falls back on the general rule.
When it helps
your legacy tooling runs on Graphite and you want to keep that format for deployment annotations.

Sourcegithub.com · September 30, 2026 ↗

update_annotation

Approval: see the rule

Replaces every field of an existing annotation: a full update.

What Claude asks for
the docs say nothing specific, so see the approvals section.
When it helps
fully correcting an annotation placed on the wrong time range.
Watch out
any field you leave out gets overwritten; for a touch-up, prefer the partial update.

Sourcegithub.com · September 30, 2026 ↗

patch_annotation

Approval: see the rule

Edits only some fields of an annotation, leaving the others alone.

What Claude asks for
no dedicated confirmation is described; the general approvals rule covers this tool.
When it helps
adding a tag to a deployment annotation that already exists.
Watch out
the service account needs write permission on annotations.

Sourcegithub.com · September 30, 2026 ↗

create_folder

Approval: see the rule

Grafana lists this tool among the write operations on folders that its read-only mode disables. Its documentation says nothing more about it.

What Claude asks for
no source describes a confirmation, so the general approvals rule applies.
When it helps
knowing that, like the other folder writes, it vanishes once the server runs in read-only mode.

Sourcegithub.com · September 30, 2026 ↗

Undocumented (1)

1 tool

The 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.

Watch out
with no description available, the general approvals rule covers it.
Approvals

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.

Plans

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.

Limits

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

Need help connecting Grafana to Claude?

A person reads every message.

FAQ

Claude Grafana connector FAQ

01What can Claude do with the Grafana connector?
Claude can query your Grafana instance while it answers you. Fifty-nine tools read dashboards, data sources, Prometheus metrics, Loki logs, alert rules, incidents, Sift investigations, OnCall rotations, Pyroscope profiles, annotations and access rights. Eleven tools act: update a dashboard, create or delete an alert rule, open an incident, place or adjust an annotation. One last name has no description, and everything happens inside Claude Desktop, bounded by your Grafana service account.
02Can Claude change or delete things in Grafana?
Yes, eleven tools act on your instance. They update or create a dashboard, create, modify or delete an alert rule, open an incident and add activity to it, and place, replace or patch an annotation. One folder-related tool also counts among the writes. Everything stays bounded by the Grafana service account's rights, and the server can run in read-only mode, which removes all of these writes at once. Pick that account's permissions with care.
03Does Claude ask before changing a Grafana alert?
By default, yes: Claude stops and asks before any action it takes on an account on your behalf. No source describes a confirmation specific to a Grafana tool, so that general rule covers all eleven write tools. On Team and Enterprise, owners decide whether some actions can go through without a fresh prompt. On the Grafana side, the server's read-only mode removes those writes entirely, which is the strongest lock available.
04Which Claude plans is the Grafana connector available on?
No official source publishes plan availability connector by connector, and none of the 819 directory sheets shows it. The general rule is that remote connectors are open to all users, and that desktop extensions, like Grafana's, install on Claude Desktop. On Team and Enterprise, an Owner enables the connector first. The directory sheet remains the only up-to-date reference for your own account, so check there before you plan around it.
05Does Claude see my whole Grafana instance?
No. Claude works with the rights of the configured Grafana service account, and each tool needs its own permissions. A data source, folder or rule outside that scope stays closed to it. For incidents and Sift, Grafana relies on basic roles: Viewer to look, Editor to act. The Editor role makes setup simpler but opens access widely, so Grafana advises keeping it for cases where convenience outweighs least privilege. Scope the account to the job it has to do.
06Why are some Grafana tools missing in Claude?
Because Grafana switches several families off by default in its server. ClickHouse, CloudWatch, log search and admin tools only become available once enabled at install time. Others fail if your Grafana version predates 9.0 or if the service account lacks the right permission. Finally, the image tool needs the Image Renderer service installed and configured, or it fails. Check those points before assuming something is broken, since the directory sheet also lags behind the server and some tools have been renamed.
07Claude or an automation tool for working with Grafana?
They do different jobs, so it depends on the use. Claude is for investigating and acting once in plain English: understand a latency spike, read logs, adjust an alert rule. An automation tool chains steps without you, for example on every alert. The connector never reacts on its own, so for automatic reactions pick an automation tool, and keep Claude for analysis and for the decisions that need a person looking at the data.