Grafana Cloud

Query Grafana Cloud metrics, logs and traces from Claude.

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

What the Grafana Cloud connector does

The Grafana Cloud MCP server is Grafana Labs' hosted connector between your Grafana Cloud stack and Claude. Its 61 tools query Prometheus metrics, Loki logs, Pyroscope profiles and other data sources, read dashboards, alerts, incidents and on-call schedules, and can change dashboards, alert rules and incidents. Writes need a separate consent that only Grafana admins can grant.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Grafana Cloud tools (61)

  • add_activity_to_incident
  • alerting_manage_routing
  • alerting_manage_rules
  • ask_assistant
  • create_annotation
  • create_folder
  • create_incident
  • describe_clickhouse_table
  • describe_infrastructure
  • find_error_pattern_logs
  • find_slow_requests
  • generate_deeplink
  • get_alert_group
  • get_annotation_tags
  • get_annotations
  • get_assertions
  • get_current_oncall_users
  • get_dashboard_by_uid
  • get_dashboard_panel_queries
  • get_dashboard_property
  • get_dashboard_summary
  • get_datasource
  • get_incident
  • get_oncall_shift
  • get_panel_image
  • get_query_examples
  • get_sift_analysis
  • get_sift_investigation
  • list_alert_groups
  • list_clickhouse_tables
  • list_cloudwatch_dimensions
  • list_cloudwatch_metrics
  • list_cloudwatch_namespaces
  • list_datasources
  • list_incidents
  • list_loki_label_names
  • list_loki_label_values
  • list_oncall_schedules
  • list_oncall_teams
  • list_oncall_users
  • list_prometheus_label_names
  • list_prometheus_label_values
  • list_prometheus_metric_metadata
  • list_prometheus_metric_names
  • list_pyroscope_label_names
  • list_pyroscope_label_values
  • list_pyroscope_profile_types
  • list_sift_investigations
  • query_clickhouse
  • query_cloudwatch
  • query_elasticsearch
  • query_loki_logs
  • query_loki_patterns
  • query_loki_stats
  • query_prometheus
  • query_prometheus_histogram
  • query_pyroscope
  • search_dashboards
  • search_folders
  • update_annotation
  • update_dashboard

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • Grafana Cloud only. Self-hosted instances are not supported by this hosted server.
  • Streamable HTTP only. Grafana says SSE is not supported.
  • Query access is not read-only. Grafana warns raw SQL queries "can modify data". Grant it only to users who would be trusted with the same query in Grafana.
  • Usage counts toward Grafana Assistant. Each MCP user is an Assistant active user, and tools that invoke an Assistant model consume tokens. Grafana's pricing page has the rates.
  • No rate limits are documented. Grafana's MCP page states none.
  • We did not read the tools. Our anonymous request returned a 401 with an OAuth challenge, so parameter-level schemas and annotations are not on this page.
  • Data handling, as Grafana states it. Grafana says it routes MCP queries through a proxy and does not train AI models on PromQL or LogQL queries, investigation content or prompt payloads.

Frequently asked questions

How do I make the Grafana Cloud connector read-only?

Tick only Read access on the consent page and clear both Query access and Write access. Grafana's documentation is specific that clearing Write alone is not enough, because Query access still exposes raw SQL tools against sources such as ClickHouse, Snowflake, Athena and InfluxDB, and Grafana warns those queries can modify data. Read access covers dashboards, alerts, incidents, metrics, logs, traces and profiles.

Why can't I see the Write access checkbox when I connect?

Because your Grafana role does not allow granting it. Grafana documents that Editors and above can grant read and query access by default, while only Admins can also grant write access. If a checkbox you need is missing, or the connection is refused, ask an administrator for the Assistant Cloud MCP User role or the grafana-assistant-app.cloud-mcp:access permission.

Does using the Grafana Cloud MCP server cost anything?

It counts toward your Grafana Assistant usage. Grafana states that each user connecting through MCP counts as an Assistant active user. Calling a tool does not consume Assistant tokens by itself; tokens are used only when a tool invokes an Assistant model, such as ask_assistant, and read-only usage consumes none. You can watch usage under Assistant, then Usage, in Grafana Cloud.

How do I connect more than one Grafana Cloud stack?

Add one connector entry per stack and put the stack host in the URL path, in the form mcp.grafana.com/mcp/ followed by your stack's grafana.net host, rather than in a header. Grafana warns that reusing the same endpoint for several entries can make a client load only one of them. A single stack can use the plain endpoint, optionally with the X-Grafana-URL header.

How long does a Grafana Cloud MCP connection stay signed in?

Up to 30 days. Grafana documents one-hour access tokens that refresh automatically for 30 days, after which you must authorise again in the browser. Each user connects under their own Grafana identity, so the connector sees what that user's role allows. You can revoke a connection at any time under Settings, then Connectors, then MCP clients, in Grafana Cloud.

Sources

Use it in an agent

Put Grafana Cloud to work.

Connect Grafana Cloud once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Call (650) 285-1019, Agentman.Our AI receptionist answers.