Grafana AI Marketplace is a collection of plugins and related configuration for using AI coding agents with Grafana observability workflows. It connects agents to Grafana through either a hosted Grafana Cloud MCP server or a locally run Grafana MCP service, and its catalogue add-ons provide those integrations.
Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
npx skills add grafana/ai-marketplace --skill grafana-mcp-toolsgit clone --depth 1 https://github.com/grafana/ai-marketplaceWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/skills/grafana/ai-marketplace/grafana-mcp-tools)<a href="https://agentmods.dev/skills/grafana/ai-marketplace/grafana-mcp-tools"><img src="https://agentmods.dev/badge/skills/grafana/ai-marketplace/grafana-mcp-tools/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/skills/grafana/ai-marketplace/grafana-mcp-tools"><img src="https://agentmods.dev/badge/skills/grafana/ai-marketplace/grafana-mcp-tools.svg" alt="Reviewed on agentmods" width="80" height="20"></a>- NVIDIA SkillSpector pass
What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.00073 | $0.01799 |
| Opus 5 | $0.00036 | $0.00899 |
| Sonnet 5 | $0.00015 | $0.00360 |
| Haiku 4.5 | $0.00007 | $0.00180 |
Grade A, and why
grafana-mcp-tools scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 13d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 194 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Grafana MCP Server
MCP server exposing 50+ Grafana API tools. Supports Grafana 9.0+ (local and Grafana Cloud).
Prerequisites
The MCP server must already be installed. Do not attempt to install it automatically. If it is not available, stop and tell the user to install it first.
Installation instructions, pre-built binaries, Docker images, and Helm charts: github.com/grafana/mcp-grafana
Configuration
Environment variables
| Variable | Description |
|---|---|
GRAFANA_URL |
Grafana instance URL (default: http://localhost:3000) |
GRAFANA_SERVICE_ACCOUNT_TOKEN |
Service account token (recommended) |
GRAFANA_API_KEY |
API key (deprecated, use service account token) |
GRAFANA_USERNAME + GRAFANA_PASSWORD |
Basic auth |
GRAFANA_ORG_ID |
Organization ID for multi-org setups |
GRAFANA_EXTRA_HEADERS |
JSON object with custom HTTP headers |
Setup steps
-
Create a service account in Grafana with at least Viewer role (or Editor for write operations). Generate a token.
-
Set environment variables:
export GRAFANA_URL="https://mystack.grafana.net" export GRAFANA_SERVICE_ACCOUNT_TOKEN="glsa_..." -
The MCP server starts automatically when Cursor loads the plugin.
Docker config for local Grafana
When connecting to localhost from Docker, use host.docker.internal:
{
"env": {
"GRAFANA_URL": "http://host.docker.internal:3000"
}
}
Binary config (alternative to Docker)
If you prefer the binary over Docker, update mcp.json:
{
"mcpServers": {
"grafana": {
"command": "mcp-grafana",
"args": [],
"env": {
"GRAFANA_URL": "${GRAFANA_URL}",
"GRAFANA_SERVICE_ACCOUNT_TOKEN": "${GRAFANA_SERVICE_ACCOUNT_TOKEN}"
}
}
}
}
CLI flags
| Flag | Description |
|---|---|
-t, --transport |
Transport type: stdio (default), sse, streamable-http |
--address |
Host:port for SSE/HTTP (default: localhost:8000) |
--debug |
Enable debug logging |
--log-level |
debug, info, warn, error |
--disable-write |
Read-only mode (no create/update/delete tools) |
--enabled-tools |
Comma-separated list of enabled tool categories |
--metrics |
Enable Prometheus metrics at /metrics |
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 13d ago First seen · 194 lines · 73 tokens per session scan A a2e25518e57f
grafana-mcp-tools is a skill published in the GitHub repository grafana/ai-marketplace (17 stars, last pushed today), licensed Apache-2.0. It adds 73 tokens to every session and 1,799 once invoked, about $0.0004 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other skills, from other repositories
systematic-debugging
Use when encountering any bug, test failure, or unexpected behavior, before proposing fixes.
local-ai-agents
Build local-first AI agents that run entirely on a developer workstation with Microsoft Foundry Local and Qwen function-calling models. Covers Small Language Models (SLMs), the OpenAI-compatible local endpoint, sandboxed local tools, local RAG with Chroma, local MCP servers, hybrid cloud/local routing, and the…
next-cache-components-adoption
Turn on Cache Components in a Next.js app and resolve the blocking routes it surfaces. Use when the user wants to enable, adopt, or migrate to Cache Components, flip the cacheComponents flag, work through a flood of blocking-prerender / instant validation errors, run the cache-components-instant-false codemod, or…
chat-pet-sprite-creation
Use when creating or changing VS Code chat pet sprite art, sprite sheets, state animations, eye treatments, Stable/Insiders variants, or pet transitions under src/vs/workbench/contrib/chat/browser/widget/media/chatPet.
cpu-profile-analysis
Analyze V8/Chrome CPU profiles (.cpuprofile) and DevTools trace files (Trace-.json). Use when: profiling performance, investigating slow functions, comparing code paths, finding bottlenecks, analyzing timeToRequest, understanding call trees from sampling profiler data, analyzing layout/paint/rendering, investigating…
insight-error-page
Write or audit an insight-kind error page for the Next.js dev overlay. Use when creating a new errors/ .mdx page, auditing an existing one, or checking that a page matches the framework fix cards. Covers page structure, title alignment, FixCard cards with Copy prompt button, code snippets, terminology verification…