Grafana OnCall MCP server — query and manage OnCall schedules, shifts, teams, users, and alert groups via the Model Context Protocol
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"grafana-oncall-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# grafana-oncall-mcp A dedicated Grafana OnCall MCP (Model Context Protocol) server written in Go. ## Overview The upstream `mcp-grafana` project targets Grafana Cloud and no longer supports `grafana-oncall-app`, which is archived and deprecated upstream. This MCP server exists to maintain compatibility for **self-hosted Grafana OnCall** instances that still run `grafana-oncall-app` or its rebranded successor `grafana-irm-app`. If you are using **Grafana Cloud**, use the official [`mcp-grafana`](https://github.com/grafana/mcp-grafana) from Grafana instead. ## Quick Start (Recommended: `uvx`) The fastest way to use this server is via `uvx`, which downloads a small Python wrapper plus the pre-compiled Go binary from PyPI on first invocation (~50MB total) and caches them. Requires [uv](https://docs.astral.sh/uv/). ```bash # Install uv if you don't have it yet curl -LsSf https://astral.sh/uv/install.sh | sh # Smoke test uvx --from grafana-oncall-mcp grafana-oncall-mcp -version # grafana-oncall-mcp 0.1.0 ``` ## Prerequisites - For `uvx`: [uv](https://docs.astral.sh/uv/) (Python package manager; handles the Python wrapper + Go binary). - For Docker: a working Docker daemon. - For source builds: Go 1.26.x. - Access to a **self-hosted Grafana** instance with **at least one** supported OnCall plugin installed: - `grafana-oncall-app` (legacy, archived upstream) **or** - `grafana-irm-app` (rebranded successor) - Grafana service account token with OnCall permissions. - MCP client capable of stdio, SSE, or Streamable HTTP. ## Configuration Use direct OnCall API mode to call the OnCall Application API directly, bypassing the Grafana plugin resource proxy. This is the recommended mode for self-hosted instances. ```bash export GRAFANA_ONCALL_API_URL="https://oncall-prod-us-central-0.grafana.net/oncall" export GRAFANA_ONCALL_API_KEY="oncall_user_scoped_key" ``` Get these values from `OnCall -> Settings`: - `GRAFANA_ONCALL_API_URL`: the **OnCall Application endpoint…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.