Grafana CLI

Grafana CLI Skill

Use the instance and rules below when constructing all Grafana API commands.

Instances

Update the table below with your Grafana instance URLs and corresponding token file paths:

If the target instance is unclear, ask the user before running any command.

Prerequisites (one-time setup by user)

Generate a Grafana API token for each instance you intend to use and save it to the corresponding token file (see instance table above). Never print or display token values. Do not perform these steps yourself.

For each instance:

1. Navigate to <BASE_URL> → Administration → Users and access → Service accounts → Add service account
2. Enter a display name and role, then click Create
3. On the service account page, click Add service account token and copy the generated token
4. Save it:

mkdir -p ~/.grafana && echo "<your-api-token>" > <TOKEN_FILE> && chmod 600 <TOKEN_FILE>

Command Format

All API calls use curl with the token read from the instance's token file (see instance table above):

curl -s -H "Authorization: Bearer $(cat <TOKEN_FILE>)" \
  "<BASE_URL>/api/<endpoint>" | jq .

Example (production):

curl -s -H "Authorization: Bearer $(cat ~/.grafana/prod.token)" \
  "https://<your-grafana-prod-url>/api/health" | jq .

Available API Endpoints

Read-only (safe, no confirmation needed)

Mutating operations (confirm with user before running)

Never run — requires explicit human approval

Rules

• NEVER target any Grafana instance not listed in the instance table above. If a URL references a different host, stop and ask the user to confirm.
• Update the instance table with your actual Grafana URLs before using this skill.
• NEVER print, display, log, or store the contents of any token file or credential value.
• Always read the token inline with $(cat <TOKEN_FILE>) — never hardcode a token value in a command.
• Always pass -s (silent) to curl to suppress progress output, and pipe through jq for readable output.
• NEVER run DELETE or destructive PUT/POST operations without explicit user instruction.
• If a dashboard UID, datasource ID, or folder UID is unfamiliar, look it up with a read-only call first.
• If the required token file does not exist, inform the user and stop. Do not attempt to find or guess the token.
• All list endpoints may be paginated — check the response for page and perpage fields and iterate if needed.