Skip to main content
Grafana connects to RubixKube today through the custom integrations path. There is no separate prebuilt app to install. Most teams start with Custom REST and move to Custom MCP when they want richer, semantic tools.

​
What to bring in

The signals that matter most when agents are investigating or writing RCAs:
  • Alert state (Grafana Alerting API) to surface firing alerts as insight candidates.
  • Dashboards (/api/dashboards/*) for the panels a team uses during an incident.
  • Datasource proxy queries (/api/datasources/proxy/...) to execute PromQL, LogQL, or SQL through Grafana’s datasource layer.
  • Annotations to read deploy markers and runbook entries.
Read-only service account tokens are enough for all of the above.

​
Which path to pick

Start with REST

Grafana ships a stable HTTP API. Point the custom REST integration at it with an OpenAPI wrapper.

Move to MCP when you need more

Wrap datasource queries behind named tools (for example prom_via_grafana(service, window)).

​
Quick recipe: REST path

1

Create a Grafana service account token

In Grafana, create a service account with a read role and generate a token.
2

Register the endpoint

In the RubixKube console, go to Integrations → Custom REST and register the Grafana API.
3

Enable the calls you care about

Start with alerts list, dashboard read, and datasource proxy queries for the specific datasources you want to reach through Grafana.
4

Set auth

Add the service account token to the workspace secret vault. Map it to the Authorization: Bearer <token> header.
5

Scope to skills

Attach the enabled endpoints to the skills that need Grafana context.
For Grafana behind a VPN or private network, use Custom MCP with a self-hosted server so no inbound exposure is needed.

​
Example tools worth having

  • grafana_firing_alerts(service) — returns alerts currently firing that tag or match the service.
  • grafana_dashboard(id) — returns the panels and queries from a dashboard, useful for agents trying to reproduce what a human would look at.
  • grafana_datasource_query(datasource, query, window) — runs a query through Grafana’s datasource proxy (PromQL, LogQL, SQL, etc).
Define these as skills (or as MCP tools if you want them to wrap multiple calls).

Custom REST Integrations

The full REST flow with auth options and approval rules.

Custom MCP Servers

When you want richer tool schemas and multi-call workflows.

Skills

How to compose Grafana queries into custom workflows.