2.0 moves the server from mark3labs/mcp-go to the official MCP Go SDK. The major version bump is for the Go library: the SDK's types are part of this module's exported API.
For most people running the server there is nothing to change. You are only affected if you:
- import
mcp-grafanaas a Go library (new module path and SDK types) - use the Sift tools, which have been removed
- call
alerting_manage_rulesoralerting_manage_silencesdirectly, rather than letting your client discover tools - use the SSE transport with per-request headers (Grafana URL, credentials, org ID or forwarded headers); switch to streamable HTTP
Changed
- Breaking: The server now uses the official MCP Go SDK instead of
mark3labs/mcp-go(#1180). Over SSE, per-request headers no longer reach tool calls, so per-call Grafana URL overrides, credentials, org ID and forwarded headers only work over streamable HTTP.--session-idle-timeout-minutesis still accepted but ignored - Breaking: The Go module path is now
github.com/grafana/mcp-grafana/v2; importers must update their import paths (#1232) - Breaking: The alerting tools are split into read and write tools, so read-only credentials and
--disable-writekeep read access:alerting_manage_rulesbecomesalerting_rules_readandalerting_rules_write, andalerting_manage_silencesbecomesalerting_silences_readandalerting_silences_write(#1233) - Anonymous usage statistics reporting is now enabled by default. Opt out with
--usage-stats=disabled,GRAFANA_USAGE_STATS=disabledorDO_NOT_TRACK=1(#1197)
Added
alerting_routing_writecreates Grafana-managed contact points (#1245)
Removed
- Breaking: The deprecated Sift tools and the
sifttool category (#1191)
Fixed
- Browser clients on an allowed CORS origin can send the
X-Grafana-URL,X-Grafana-Service-Account-Token,X-Grafana-API-KeyandX-Grafana-Org-Idheaders, and CORS responses now setVary: Origin - Tool parameters that accept any value now declare an explicit type list in their JSON schema, so MCP clients no longer warn that the schema has no validation keywords (#1231)
- Observability providers shut down in parallel, so one slow exporter no longer makes the others time out on shutdown (#1230)