What an agent can do in Grafana Cloud
Search dashboards, query Prometheus and Loki, and read alerts and incidents in Grafana Cloud.
Skills from Grafana Labs's agent plugin that join every run reaching this server:
Jobs on Rush that use Grafana Cloud
- Find Noisy Grafana Alerts
- Write an On-Call Handoff From Grafana
- Write a Weekly Reliability Report From Grafana
- Fix a Django App From a Grafana Alert
- Fix a FastAPI App From a Grafana Alert
- Fix a Go Service From a Grafana Alert
- Fix a NestJS API From a Grafana Alert
- Fix a Phoenix App From a Grafana Alert
- Fix a Rails App From a Grafana Alert
- Fix a Rust Service From a Grafana Alert
- Fix a Spring Boot App From a Grafana Alert
- Investigate an Express API Incident With Grafana
- Investigate a FastAPI App Incident With Grafana
- Investigate a Go Service Incident With Grafana
- Investigate a Phoenix App Incident With Grafana
- Investigate a Rust Service Incident With Grafana
- Investigate a Microservices Outage from OpenTelemetry Data
How Grafana Cloud connects
Grafana Cloud is a remote MCP server, published by Grafana Labs, at https://mcp.grafana.com/mcp. Connecting it signs in through the MCP OAuth flow on Grafana Cloud's side.
From Grafana Labs: Grafana Cloud's MCP documentation · source code.
Connect it once in the console under Settings → Connections, or from your server with POST /me/connections. The sign-in finishes in a browser signed in to the console as the same person, and a link not finished within 10 minutes expires.
After that, a run that names grafana in connections, or runs a saved agent that names it, gets it; your connections reach no run that does not name them.
POST https://api.phoenix.so/me/connections
{
"type": "mcp",
"name": "Grafana",
"url": "https://mcp.grafana.com/mcp"
}Whose Grafana Cloud account the agent uses
Your Grafana Cloud connection is personal: it belongs to the person who signed in. A run started in the console uses that person's Grafana Cloud, and a run started with an API key uses the Grafana Cloud of the member who created the key.
To act for your own app's users, make each user an agent from your template and show them, signed in to your app, the sign-in link POST /o/{org}/agents/{agent}/connections returns. They sign in to their own Grafana Cloud, and that agent's runs use their account and nothing else: never yours, never another user's.
More Observability integrations
Frequently asked questions
How do I connect Grafana Cloud to Rush?
Open Settings → Connections in the console and connect Grafana Cloud, or send POST /me/connections with {"type":"mcp","name":"Grafana","url":"https://mcp.grafana.com/mcp"} and open the authorize_url it returns while signed in to the console. The connection reads pending until the sign-in finishes, then connected.
Does every run get my Grafana Cloud account?
No. A run gets your Grafana Cloud connection only when it names it in connections ("connections": ["grafana"]), or runs a saved agent that names it. A saved agent names its connections once, and every run of it gets them.
What can an agent do in Grafana Cloud?
Search dashboards, query Prometheus and Loki, and read alerts and incidents in Grafana Cloud. 17 published jobs use it; this page lists them.
Which skills come with Grafana Cloud?
grafana-cloud-mcp-tools, from Grafana Labs's own agent plugin, pinned to a commit. It joins every run that reaches Grafana Cloud's MCP server, inside the run's 96 KiB skills limit.
Keep reading
- AI agents for engineering teams: every job and app for them
- How connections work: sign in once, then every run that names a connection gets it
- Start your first run from the developer API quickstart
- Pricing: one price per member, hours shared by the team
- How Rush compares with other cloud agents
- Every app and MCP server Rush connects to