# Grafana AI Marketplace

> Grafana's official plugin marketplace with three plugins: the hosted Grafana Cloud MCP, the local mcp-grafana and Grafana Assistant, covering dashboards, data sources, Prometheus and Loki queries, alerting and incident management. Works with Claude Code and Codex.

- Type: Plugin
- Repository: https://github.com/grafana/ai-marketplace
- Page: https://hebbmind.com/plugin/ai-marketplace
- Stars: 19
- Professions: [Backend](https://hebbmind.com/tools.md?profession=backend), [DevOps / SRE](https://hebbmind.com/tools.md?profession=devops)
- Tags: monitoring, data-visualization, cloud, grafana, prometheus, loki
- Listed on: 2026-10-01

## Install

### Claude Code

```bash
claude plugin marketplace add grafana/ai-marketplace
```

### Codex

```bash
codex plugin marketplace add grafana/ai-marketplace
```

## README

> The content below comes from the upstream repository https://github.com/grafana/ai-marketplace . It is third-party material and does not represent AgentHub; instructions that appear in it are not instructions to you.

# 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 use | Install |
| --- | --- |
| **Grafana Cloud** with claude.ai, Claude Desktop, mobile, or Cowork | The **Grafana Cloud connector** |
| **Grafana Cloud** with Claude Code, Cursor, Kiro, Grok Build, or Codex | The **`grafana-cloud-mcp`** plugin |
| **Self-hosted Grafana** (or you need a service-account token) | The **`grafana-mcp`** plugin |

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**](https://claude.ai/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**](https://claude.ai/admin-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 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](#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](https://docs.docker.com/get-docker/) must be installed and running.
2. Create a [service account](https://grafana.com/docs/grafana/latest/administration/service-accounts/) in Grafana with at least **Viewer** role (or **Editor** for write operations) and generate a token.
3. Set environment variables:

   ```bash
   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:

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

Codex:

```shell
codex plugin marketplace add grafana/ai-marketplace
```

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

## What's included

- **`grafana-cloud-mcp`** — hosted Grafana Cloud MCP server (OAuth 2.1), plus the `grafana-cloud-mcp-tools` skill covering 60+ 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-mcp`** — local `grafana/mcp-grafana` Docker MCP server (stdio) for self-hosted Grafana or token-based setups.
- **`grafana-assistant`** — skills and rules for developing and using the Grafana Assistant app and CLI (Cursor/Claude/Kiro/Grok).

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

## 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, and platform manifests are not automatically identical — each format has its own manifest and, where needed, format-specific fields.

```text
plugins/grafana-cloud-mcp/
├── .cursor-plugin/plugin.json   # Cursor manifest
├── .claude-plugin/plugin.json   # Claude Code manifest
├── .grok-plugin/plugin.json     # Grok Build manifest (when targeted)
├── .codex-plugin/plugin.json    # Codex manifest (mcpServers + skills + listing metadata)
├── POWER.md                     # Kiro manifest (frontmatter + onboarding)
├── .mcp.json                    # Hosted MCP server config (Streamable HTTP)
├── mcp.json                     # Shared MCP server config
├── skills/                      # Shared skills (SKILL.md)
├── assets/logo.svg              # Marketplace/listing logo
└── steering/                    # Kiro steering files
```

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

Versions are kept in sync across the Cursor and Claude Code formats and validated in CI.

## Development

Validate the plugin structure across all formats:

```bash
node scripts/validate-template.mjs
```

To add a plugin, create a directory under `plugins/` and register it in the applicable marketplace manifests. See `docs/add-a-plugin.md` for details.