Skip to content
Back to search

grafana-mcp-vm-operator

Grafana mcp server operator

Safety scan

A static text scan, not a guarantee. Select the badge to see what was scanned and every finding.

Checked today
Badge for your README
findsafeskills safety rating

Markdown

[![findsafeskills safety rating](/api/listings/dwellir-public--grafana-mcp-vm-operator/badge.svg)](/listings/dwellir-public--grafana-mcp-vm-operator)

HTML

<a href="/listings/dwellir-public--grafana-mcp-vm-operator"><img src="/api/listings/dwellir-public--grafana-mcp-vm-operator/badge.svg" alt="findsafeskills safety rating" /></a>

Install

i

What was scanned

The files the safety scan read, as written by the repository's author and shown as plain text. Lines with a finding are marked.

README.md · README · 38 lines
  1. # grafana-mcp-vm
  2. Ubuntu machine charm for the official [Grafana MCP server](https://github.com/grafana/mcp-grafana).
  3. The charm runs one read-only server. It binds to `127.0.0.1:8000` by default;
  4. the only other accepted listener is a Tailscale IPv4 address.
  5. The charm pins Grafana MCP v2.2.0 and verifies the upstream archive's SHA-256 before installing
  6. it. It uses a dedicated `grafana-mcp` system user and keeps the Grafana and MCP caller tokens in
  7. Juju secrets. The generated systemd environment file is mode `0600` and is never included in
  8. status text or process arguments.
  9. ## Configure
  10. Create two Juju secrets with a `token` field and grant them to the `grafana-mcp-vm` application.
  11. Set `grafana-url`, `grafana-token-secret`, and `caller-token-secret` to the stack URL and secret IDs.
  12. See [DEVELOPING.md](DEVELOPING.md) for build and validation commands.
  13. An MCP client should use `http://127.0.0.1:8000/mcp` when deployed on the same
  14. machine and present the caller token as a bearer token. No public Juju port is opened.
  15. If an operator deliberately exposes the MCP endpoint through a public HTTPS proxy, set
  16. `allowed-host` to its exact DNS hostname, for example
  17. `mcp.example.com`. The charm then adds that hostname and its explicit
  18. `:443` form to the three local Host values. It rejects wildcards and whitespace. The
  19. bearer token and read-only tool restrictions remain in force. Keep `allowed-host` empty
  20. for a local-only deployment. The public `/healthz` endpoint is unauthenticated; do not
  21. use it to infer MCP access.
  22. For a local-only deployment, leave `allowed-host` empty and keep the listener on loopback.
  23. ## Build and release
  24. Pull requests and pushes to `main` run the locked lint and unit checks. The manual
  25. `Release charm to Charmhub and GitHub` workflow builds the Ubuntu 24.04 amd64
  26. artifact, uploads it to Charmhub `latest/edge`, and attaches the same artifact
  27. to a GitHub prerelease. It requires a repository secret named `CHARMHUB_TOKEN`
  28. containing a Charmcraft exported login scoped to this charm and the edge channel.
  29. See [DEVELOPING.md](DEVELOPING.md) for local checks.

Ratings and comments

Sign in to rate this skill.

Sign in

Free to use. If it’s helped, pass it on.