grafana-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAFANA_URL | Yes | Base URL of your Grafana instance, e.g. http://localhost:3000 | |
| SOCKS_PROXY | No | Optional: SOCKS5 proxy URL, e.g. socks5://localhost:1080 | |
| GRAFANA_USER | Yes | Grafana username | |
| GRAFANA_PASSWORD | Yes | Grafana password |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search-dashboardsA | Search for Grafana dashboards by query string, folder, or tag. |
| get-dashboardA | Get a dashboard by its UID. Returns the full dashboard JSON model. |
| create-or-update-dashboardB | Create a new dashboard or update an existing one. Pass the full dashboard JSON model. |
| delete-dashboardB | Delete a dashboard by its UID. |
| list-datasourcesA | List all configured datasources in Grafana. |
| get-datasourceB | Get a datasource by its name or numeric ID. |
| query-datasourceB | Run an instant or range query against a datasource using Grafana's ds/query endpoint. |
| influx-show-databasesA | List all InfluxDB databases accessible through a Grafana InfluxDB datasource. |
| influx-show-measurementsA | List all measurements (tables) in an InfluxDB database. |
| influx-show-field-keysA | List all field keys (numeric columns) for a measurement in InfluxDB. |
| influx-show-tag-keysB | List all tag keys (indexed dimensions) for a measurement in InfluxDB. |
| influx-show-tag-valuesA | List all values for a specific tag key in an InfluxDB measurement. Useful for discovering hostnames, environments, regions, etc. |
| influx-show-retention-policiesA | List retention policies for an InfluxDB database, including duration and replication. |
| list-alert-rulesC | List all Grafana Alerting rules (Grafana-managed alerts). |
| get-alert-ruleB | Get a Grafana-managed alert rule by UID. |
| create-alert-ruleC | Create a new Grafana-managed alert rule via the provisioning API. |
| update-alert-ruleB | Update an existing Grafana-managed alert rule by UID. |
| delete-alert-ruleB | Delete a Grafana-managed alert rule by UID. |
| list-notification-policiesA | Get the Grafana Alerting notification policy tree. |
| list-contact-pointsA | List all Grafana Alerting contact points (notification channels). |
| list-foldersC | List all dashboard folders in Grafana. |
| get-healthA | Check the health and version of the Grafana instance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 22 tools
Each tool targets a distinct resource and action. Alert, dashboard, datasource, folder, contact point, notification policy, health, query, and InfluxDB exploration tools all have clear, non-overlapping purposes. Even within alerts, single vs list tools are distinct.
Most tools follow a verb-noun pattern with hyphens (e.g., create-alert-rule, list-dashboards). Minor inconsistencies include 'create-or-update-dashboard' using a compound verb and 'get-datasource' singular vs 'list-datasources' plural, but overall pattern is predictable.
22 tools is slightly above the typical sweet spot but still reasonable for a comprehensive Grafana server. The scope covers alerts, dashboards, datasources, folders, contact points, notification policies, health, query, and InfluxDB exploration, justifying the count.
Core CRUD for dashboards and alerts is present, but missing create/update/delete for folders, contact points, and notification policies limits workflow completeness. InfluxDB tools are read-only. Basic querying and health checks are included.