AgentPhone
Give an AI agent its own US or Canada number to call and text.
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
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.
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
401 with an OAuth challenge, so parameter-level schemas and annotations are not on this page.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.
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.
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.
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.
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.
POST https://mcp.grafana.com/mcp returned 401 with a WWW-Authenticate challenge naming https://mcp.grafana.com/.well-known/oauth-protected-resource/mcp; that document lists mcp.grafana.com/mcp as the authorization server and the three scopes above · retrieved 2026-11-18Connect Grafana Cloud once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.