Grafana Context MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GRAFANA_URL | Yes | The base URL of the Grafana instance, e.g. https://grafana.example.com | |
| GRAFANA_ORG_ID | No | Optional Grafana organization ID | |
| GRAFANA_VERIFY_SSL | No | Whether to verify TLS certificates for Grafana connections | true |
| GRAFANA_TIMEOUT_SECONDS | No | Timeout for Grafana API requests in seconds | 30 |
| GRAFANA_SERVICE_ACCOUNT_TOKEN | Yes | Grafana service account token with read-only permissions |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_datasourcesA | List configured data sources without exposing stored credentials. |
| get_datasourceA | Get configuration metadata for one data source by UID. |
| check_datasource_healthA | Run the Grafana plugin health check for one data source. |
| search_dashboardsA | Search dashboards by title and optional tag. |
| get_dashboardA | Get the complete dashboard JSON and metadata. |
| analyze_dashboardA | Explain dashboard structure, queries, data sources, variables, semantics, and interpretation risks. |
| query_datasourceA | Run bounded, read-only native plugin queries through Grafana's data source query API. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| investigate_dashboard | Guide a careful, evidence-based dashboard investigation. |
| troubleshoot_datasource | Guide data source connectivity and query troubleshooting. |
| explain_panel | Explain the meaning and limitations of one dashboard panel. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| datasource_guide | Reference for Grafana data source types and safe communication patterns. |
| dashboard_guide | Reference for reading dashboards and interpreting what panels mean. |
| querying_guide | Guide to querying data sources through Grafana. |
| instance_datasources | Live data source inventory from the configured Grafana instance. |
TDQS
Scored across 7 tools
Each tool has a clear and distinct responsibility: listing vs. getting vs. health-checking datasources, searching vs. getting vs. analyzing dashboards, and running queries. There is no meaningful overlap between tools that would cause an agent to select the wrong one.
All tools follow the same verb_noun snake_case pattern (e.g., list_datasources, get_dashboard, analyze_dashboard, query_datasource). Naming is predictable and makes the toolset easy to navigate.
Seven tools is a well-scoped size for a Grafana context server. Each tool covers a distinct, necessary operation without bloat or redundancy.
The toolset covers the full read-only context workflow: discovering datasources, checking their health, finding dashboards, retrieving dashboard JSON, understanding dashboard structure, and querying datasources. For the stated purpose of providing Grafana context, there are no significant gaps.