This is documentation for the next version of Grafana documentation. For the latest stable release, go to the latest version.
MCP tools reference
Use the table to confirm minimum Grafana RBAC permissions and scopes for each MCP tool. The sections after the table summarize RBAC patterns, optional categories, and a few operational notes.
Note
The tool list and behavior reflect the current server release. This page is not a roadmap or a commitment to future features.
What you’ll achieve
You can verify that a service account has the right permissions before you enable tools in production, and you can apply common scope patterns without rereading Grafana’s RBAC docs.
Before you begin
- Grafana 9.0 or later for full API support.
- Optional: a service account whose permissions match the tools you enable.
Review the tools table
The following table lists MCP tools, required RBAC permissions, and typical scopes. Categories marked with * are off until you add them to --enabled-tools (refer to Command-line flags). The table does not include proxied tools from external MCP servers (for example Grafana Tempo).
* Categories marked with * are off until you add them to --enabled-tools.
Dashboard tools and context window
update_dashboard supports full JSON replacement and patch-style updates (uid plus operations). Prefer patches for small changes so you do not send large dashboard JSON to the model.
To limit context use when working with dashboards (issue #101):
- Use
get_dashboard_summaryfor an overview before edits. - Use
get_dashboard_propertywith JSONPath when you only need part of a dashboard. - Avoid
get_dashboard_by_uidunless you need the full dashboard JSON.
RBAC permissions
Each tool requires specific RBAC permissions. When you create a service account for the MCP server, grant the minimum actions for the tools you enable. You often need matching scopes as well (for example datasources:*, dashboards:*, folders:*).
Tip: If you want a faster setup instead of tuning many scopes, assign a built-in role such as Editor to the service account. Editor grants broad read and write access for most MCP operations; it is less granular than least privilege.
Grafana Incident and Sift tools use basic Grafana roles instead of fine-grained RBAC permissions:
- Viewer: read-only operations (for example list incidents, get investigations).
- Editor: write operations (for example create incidents, run analyses that modify state).
Refer to Grafana RBAC for full detail.
RBAC scopes
Scopes define which resources a permission applies to. You need the right permission and scope together.
Broad access (organization-wide) often uses * wildcards:
datasources:*dashboards:*folders:*teams:*
Limited access uses specific UIDs or IDs:
datasources:uid:prometheus-uiddashboards:uid:abc123folders:uid:xyz789teams:id:5global.users:id:123
Examples:
Full MCP access (typical broad grants):
datasources:* (datasources:read, datasources:query)
dashboards:* (dashboards:read, dashboards:create, dashboards:write)
folders:* (for dashboard creation and alert rules)
teams:* (teams:read)
global.users:* (users:read)Limited datasource access (only specific Prometheus and Loki instances):
datasources:uid:prometheus-prod (datasources:query)
datasources:uid:loki-prod (datasources:query)Dashboard-only read access:
dashboards:uid:monitoring-dashboard (dashboards:read)
dashboards:uid:alerts-dashboard (dashboards:read)Enable or disable tools
You can limit which tools the server exposes with --enabled-tools, --disable-<category>, and --disable-write. Refer to Enable and disable tools and Command-line flags.
Panel and dashboard images
get_panel_image needs the Grafana Image Renderer service installed and configured in Grafana.


