Grafana AI Marketplace

Plugin

Grafana 官方插件市场,含托管 Grafana Cloud MCP、本地 mcp-grafana 与 Grafana Assistant 三个插件,覆盖看板、数据源、Prometheus/Loki 查询、告警与事件管理,支持 Claude Code 与 Codex。

grafana/ai-marketplace20
README

Grafana AI Marketplace

Plugin marketplace for AI-assisted Grafana observability workflows in Cursor, Claude Code, Kiro, Grok Build, and Codex.

Which one do I need?

You useInstall
Grafana Cloud with claude.ai, Claude Desktop, mobile, or CoworkThe Grafana Cloud connector
Grafana Cloud with Claude Code, Cursor, Kiro, Grok Build, or CodexThe Grafana Cloud plugin (grafana-cloud-mcp)
Self-hosted Grafana (or you need a service-account token)The Grafana (self-hosted) plugin (grafana-mcp)

The Grafana Cloud connector and the grafana-cloud-mcp plugin are not alternatives — they use the same hosted server (https://mcp.grafana.com/mcp) and the same sign-in. The plugin adds skills that teach the agent how to use the tools well. Install the plugin as well as the connector if your app supports plugins; you'll see one set of tools, not two.

Getting started

Grafana Cloud in Claude apps (connector)

  1. Have a Grafana Cloud account with the Assistant Cloud MCP User role or the grafana-assistant-app.cloud-mcp:access permission (Editor and higher have it by default).
  2. Add the connector:
    • Free, Pro, or Max: go to Customize → Connectors, choose Add custom connector, and enter https://mcp.grafana.com/mcp.
    • Team or Enterprise: an Owner adds it once for the organization under Organization settings → Connectors (Add → Custom → Web, URL https://mcp.grafana.com/mcp). Members can't add custom connectors themselves; it then appears for them under Customize → Connectors with a Custom label.
  3. Select Connect, enter your Grafana Cloud URL, and authorize in your browser. Choose read-only or read + write access during consent.

Grafana Cloud is also listed in the Claude Connectors Directory, which you can add it from instead of entering the URL.

Grafana Cloud in coding agents (plugin)

  1. Meet the same Grafana Cloud role requirement as above.
  2. Install the grafana-cloud-mcp plugin from your platform's marketplace (see Add this marketplace).
  3. When prompted, enter your Grafana Cloud URL and authorize the connection in your browser. Choose read-only or read + write access during consent.

Authorizing read + write access, through either the connector or the plugin, additionally requires the Assistant Admin role or the grafana-assistant-app.cloud-mcp.scope:write permission. If Write is unavailable on the OAuth consent page, ask your Grafana organization administrator to grant it.

No Docker, environment variables, or service-account token are required.

Self-hosted Grafana (grafana-mcp, Docker + service-account token)

Use this only for self-hosted Grafana or when you specifically need token-based access. Grafana Cloud users should use the connector or grafana-cloud-mcp above.

  1. Docker must be installed and running.

  2. Create a service account in Grafana with at least Viewer role (or Editor for write operations) and generate a token.

  3. Set environment variables:

    export GRAFANA_URL="http://localhost:3000"
    export GRAFANA_SERVICE_ACCOUNT_TOKEN="<your token>"
    
  4. Install the grafana-mcp plugin from your platform's marketplace.

Add this marketplace

Claude Code:

/plugin marketplace add grafana/ai-marketplace
/plugin install grafana-cloud-mcp@grafana-ai-marketplace

Codex:

codex plugin marketplace add grafana/ai-marketplace

Cursor, Kiro, and Grok Build install from their respective marketplace UIs.

What's included

  • Grafana Cloud (grafana-cloud-mcp) — hosted Grafana Cloud MCP server (OAuth 2.1), plus the grafana-cloud-mcp-tools skill covering dozens of tools for dashboards, datasources, Prometheus, Loki, Tempo, Pyroscope, alerting, incidents, OnCall, annotations, and Grafana Assistant (ask_assistant). Packaged for Codex as an app-plus-skills plugin.
  • Grafana (self-hosted) (grafana-mcp) — local grafana/mcp-grafana Docker MCP server (stdio) for self-hosted Grafana or token-based setups.

See each plugin's README.md for its full tool reference.

The grafana-assistant plugin has been removed, along with its skill for the deprecated Grafana Assistant CLI. To ask Grafana Assistant questions from an agent, use the Grafana Cloud plugin's ask_assistant tool.

Architecture

Each plugin ships manifests for the platforms it targets and shares components (rules, skills, MCP config) where the formats allow. Not every plugin targets every platform. The Cursor, Claude Code, Codex, Antigravity, and Agent Plugins (Kiro) manifests, the MCP configs, the POWER.md frontmatter, and the marketplace indexes' plugins lists are generated from one source file per plugin, sources/<name>.json, which holds the shared fields plus any format-specific ones. Sources sit outside the plugin directories so they aren't shipped with the plugins.

sources/grafana-cloud-mcp.json   # Source for the generated files below
plugins/grafana-cloud-mcp/
├── .cursor-plugin/plugin.json   # Cursor manifest (generated)
├── .claude-plugin/plugin.json   # Claude Code manifest (generated)
├── .codex-plugin/plugin.json    # Codex manifest (mcpServers + skills + listing metadata, generated)
├── .antigravity-plugin/plugin.json # Antigravity manifest (generated)
├── POWER.md                     # Legacy Kiro manifest (generated frontmatter + hand-written onboarding)
├── .mcp.json                    # Hosted MCP server config (Streamable HTTP, generated)
├── mcp.json                     # MCP config for Cursor, Kiro's POWER.md loader and Factory (generated)
├── mcp_config.json              # Antigravity MCP config (generated)
├── skills/                      # Shared skills (SKILL.md)
├── assets/logo.svg              # Marketplace/listing logo
└── steering/                    # Kiro steering files

Each plugin that targets Kiro also gets a generated power in the Agent Plugins format, which Kiro's powers registry requires. It sits in its own folder so other hosts that fall back to a root plugin.json don't load it instead of their own manifest:

kiro/grafana-cloud-mcp/
├── plugin.json                  # Agent Plugins manifest
├── mcp.json                     # Agent Plugins MCP config
├── README.md                    # Copied from the plugin
└── skills/                      # Copied from the plugin

Root marketplace manifests:

  • .cursor-plugin/marketplace.json — Cursor Marketplace
  • .claude-plugin/marketplace.json — Claude Code plugin registry
  • .grok-plugin/marketplace.json — Grok Build plugin marketplace
  • .kiro-power/marketplace.json — Kiro Powers registry
  • .agents/plugins/marketplace.json — Codex marketplace

CI checks that the generated files match their source.

Development

After editing a file in sources/, regenerate the manifests, then validate the plugin structure across all formats:

node scripts/generate.mjs
node scripts/validate-template.mjs

To add a plugin, create a directory under plugins/, add sources/<name>.json, and run the generator; it registers the plugin in each targeted marketplace. See docs/add-a-plugin.md for details.