Integration · Automate and collaborate
Grafana Cloud and Meteor AI agents
Connect Grafana Cloud to an internal Met: check alerts, incidents and on-call, query metrics and logs and search dashboards with the official MCP.
How does Grafana Cloud connect to Meteor?
With the Grafana Cloud ready connector, your Met uses Grafana's hosted MCP server with the account the admin authorizes and that account's Grafana permissions. It searches dashboards and brings their summary, queries metrics with PromQL and logs with LogQL, checks alert rules, alert groups and incidents, and tells you who is on call. With write permission it also creates incidents, adds notes to their timeline, creates annotations and updates dashboards. When authorizing you choose read, query or write. Watch the cost: according to Grafana, MCP server usage counts toward Grafana Assistant and each user who connects counts as an active user.
What it automates
What a Meteor Met does with Grafana Cloud
Tell you which alert fired and who is on call
When someone asks on WhatsApp whether something is down, the Met lists the active alert groups, opens the latest one and tells you who is on call right now in your team's schedule.
Open an incident and leave the note
If the connection has write permission, the Met creates the incident and adds to its timeline a note with what was reported on WhatsApp.
Find the error in the logs
The Met queries the logs with LogQL in the time window you give it and detects the most frequent patterns, to tell you what is failing.
Send you the panel that matters
The Met finds the dashboard, generates the deep link to the panel and, if you ask, renders it as an image so you can see it in the chat.
27 tools
Everything your Met can ask Grafana Cloud for
Each one is a real action in the connector. You can switch off the ones you would rather it never used.
| Tool | What it does |
|---|---|
search_dashboards | Searches dashboards with a text. |
search_folders | Searches folders with a text. |
generate_deeplink | Generates deep links to dashboards, panels and Explore queries. |
get_dashboard_summary | Returns a compact summary of a dashboard, without the full JSON. |
get_dashboard_panel_queries | Returns a dashboard's panel queries, with template variables substituted. |
get_panel_image | Renders a dashboard panel as a PNG image. |
update_dashboard | Creates or updates a dashboard with full JSON or targeted patches. It is a write tool. |
list_datasources | Lists the configured data sources, with filtering by type and pagination. |
list_prometheus_metric_names | Discovers the available metrics, with regex filtering and pagination. |
query_prometheus | Runs instant or range PromQL queries. |
query_prometheus_histogram | Queries histogram percentiles. |
list_loki_label_names | Lists the label names available in logs. |
query_loki_logs | Runs LogQL queries for log lines or metric values. |
query_loki_patterns | Detects and analyzes common log patterns. |
query_clickhouse | Runs SQL queries against ClickHouse data sources. Starts turned off. |
alerting_manage_rules | Lists and filters alert rules; with write permission, it also creates and updates them. |
alerting_manage_routing | Shows the alert routing configuration, notification policies, contact points and time intervals. |
get_annotations | Returns annotations filtered by dashboard, time range or tags. |
create_annotation | Creates an annotation on a dashboard or panel. It is a write tool. |
list_incidents | Lists incidents, with optional status filtering. |
get_incident | Returns the full details of an incident by ID. |
create_incident | Creates a new incident. It is a write tool. |
add_activity_to_incident | Adds a note to an incident's timeline. It is a write tool. |
list_oncall_schedules | Lists OnCall schedules, with optional team filtering. |
get_current_oncall_users | Returns the people currently on call for a schedule. |
list_alert_groups | Lists alert groups with filters by state, team, time range and labels. |
get_alert_group | Returns a specific alert group by ID. |
The limits
What the Grafana Cloud integration does NOT do
We would rather say it here than have you find out during rollout.
-
It is not free on Grafana's side. According to Grafana, MCP server usage counts toward Grafana Assistant and each user who connects counts as an active user for billing.
-
It does not ask you for confirmation in the chat before writing. The permission you choose when authorizing and the actions the admin leaves on in Connections are the control.
-
It does not protect your data with the query permission. According to Grafana, SQL queries run as written and can modify data. That is why the ClickHouse SQL query starts turned off in Connections; for read-only, also clear Write and Query when authorizing.
-
It does not work with self-hosted Grafana. The hosted server is for Grafana Cloud only.
-
It does not do more than your Grafana role allows. The agent only has the permissions Grafana gives you.
Before you start
What you need to connect Grafana Cloud
- 1
Grafana Cloud with Assistant available
Your Grafana Cloud stack must have Grafana Assistant available and its terms accepted. Depending on your agreement, they are accepted the first time you use Assistant or by an administrator.
- 2
The Assistant Cloud MCP User role or higher
You need the Assistant Cloud MCP User role or the grafana-assistant-app.cloud-mcp:access permission. Users with the Editor role or higher have it by default.
- 3
Connect it in Met
In Met, open Connections → Grafana Cloud → Connect. A Grafana window opens where you enter your stack URL, sign in and choose read, query or write permissions.
Frequently asked questions
Questions about Grafana Cloud and Meteor
On Grafana's consent page, clear Write access and Query access and leave Read access. If you only clear Write, SQL queries are still allowed.
It depends on your plan. Grafana says MCP server usage counts toward Grafana Assistant and each connected user counts as an active user; check the Assistant pricing page.
Only if you authorized write access. With that permission, creating incidents stays on unless the admin turns it off in Connections, and the Met runs it without asking you for confirmation in the chat.
You do, with your own Grafana Cloud plan. Meteor does not resell Grafana: the connector uses your company's account.
Step by step
Automations that use Grafana Cloud
Complete tasks, with the steps and the tools that run at each one.
Automate and collaborate
Other integrations in the same family
Want to see a Met running Grafana Cloud?
We will show you with your own account connected, not with a canned demo.