Does the generate_deeplink tool work with version 12.1?

[craigvphillips]

All the links i generate are invalid, if i manually go do the same via Explore, the links i get look nothing like what comes from the tool for the same query.

I can get it to work if i post an example of a working link, but until i do that it looks like it's generating for a different version of grafana.

[sd2k]

@craigvphillips Grafana's URLs have been stable for quite a while now so they should work the same for many Grafana versions. Do you have some examples of invalid links that you can share?

[fae7em]

@sd2k Grafana API schema has changed from version 12, for example:
Here is version 12.0 document (/apis/dashboard.grafana.app/v1beta1/namespaces/default/dashboards):
https://grafana.com/docs/grafana/v12.0/developers/http_api/dashboard/
and here is older version (/api/dashboards):
https://grafana.com/docs/grafana/v11.6/developers/http_api/dashboard/

so because of that most of the grafana mcp server tools getting error, like:

Failed to call tool 'get_dashboard_by_uid': get dashboard by uid XXX: [GET /dashboards/uid/{uid}][406] getDashboardByUidNotAcceptable {message:dashboard api version not supported, use /apis/dashboard.grafana.app/v2alpha1/namespaces/default/dashboards/XXX instead}

[sd2k]

Hm that is tricky, it looks like the Go OpenAPI client doesn't support the new endpoint yet. Also it seems like it's impossible to know in advance which endpoint to hit. I'll ask some of the Grafana API devs about this and figure out a good way forward.

[VtG242]

I'm using Grafana v12.1.0 and it seems that in case I ask for link to "explore" resource so generate_deeplink returns link in old format (explore?left=) but when I do the same in UI there is "explore?schemaVersion=1".
Also it would be great to have possibility to get short url(api/short-urls).

[jludvice]

I'm experiencing similar issue.
To me it appeared when during investigation of some issue in logs with cladue code. In the end I asked it to summarize findings with links to explore but the explore links were not working.

Investigation of incorrect explore links with claude code:

Problem

The generate_deeplink tool generates URLs using the left parameter format:

  /explore?left={"datasource":"LOKINONPROD"}&from=...&to=...

This causes a JavaScript error in Grafana 10+:

  TypeError: Cannot read properties of undefined (reading 'datasourceInstance')
      at external.utils.ts:11:22

Root Cause

In tools/navigation.go, the explore deeplink is constructed using the old format:

  exploreState := fmt.Sprintf(`{"datasource":"%s"}`, *args.DatasourceUID)
  params.Set("left", exploreState)

Required Fix

The current https://grafana.com/docs/grafana/latest/explore/get-started-with-explore/ specifies the schemaVersion=1 + panes format:

  /explore?schemaVersion=1&panes=<URL_ENCODED_JSON>&orgId=1

Where the panes JSON structure is:

  {
    "a": {
      "datasource": "DATASOURCE_UID",
      "queries": [
        {
          "refId": "A",
          "datasource": {
            "type": "loki",
            "uid": "DATASOURCE_UID"
          }
        }
      ],
      "range": {
        "from": "now-1h",
        "to": "now"
      }
    }
  }

References

• https://grafana.com/docs/grafana/latest/explore/get-started-with-explore/
• https://play.grafana.org/explore?schemaVersion=1&panes=%7B%22jk3%22%3A%7B%22datasource%22%3A%22grafanacloud-prom%22%2C%22queries%22%3A%5B%7B%22refId%22%3A%22A%22%2C%22expr%22%3A%22alloy_build_info%7Bbranch%3D%5C%22HEAD%5C%22%7D%22%7D%5D%7D%7D&orgId=1

---

about compatibility with older grafana versions - I'm not sure if it doesn't make anything up, but it seems like it won't fully work even with older grafana versions:

Backward Compatibility Summary

Based on my research:

URL Format History

  | Grafana Version | URL Format                                                | Status           |
  |-----------------|-----------------------------------------------------------|------------------|
  | Pre-9.0         | left=["now-1h","now",...] (compact array)                 | Deprecated       |
  | 9.0+            | left={"datasource":"...","queries":[...]} (standard JSON) | Supported in 9.x |
  | 10.0+           | schemaVersion=1&panes={"a":{...}}                         | Current standard |

What Grafana Does

1. Grafana 9.x: Supports left parameter with standard JSON format. Compact array format was deprecated but auto-converts.
2. Grafana 10+: Introduced schemaVersion=1 + panes format. The left parameter behavior is unclear - your error suggests it may not work properly or requires the full query structure.

The Problem with Current mcp-grafana Implementation

The tool generates: left={"datasource":"UID"}

This is incomplete - even for Grafana 9.x, the left parameter needed more fields (queries, range). The minimal JSON with just datasource doesn't work in either version properly.

[Znuff]

@sd2k Grafana API schema has changed from version 12, for example: Here is version 12.0 document (/apis/dashboard.grafana.app/v1beta1/namespaces/default/dashboards): https://grafana.com/docs/grafana/v12.0/developers/http_api/dashboard/ and here is older version (/api/dashboards): https://grafana.com/docs/grafana/v11.6/developers/http_api/dashboard/

so because of that most of the grafana mcp server tools getting error, like:

Failed to call tool 'get_dashboard_by_uid': get dashboard by uid XXX: [GET /dashboards/uid/{uid}][406] getDashboardByUidNotAcceptable {message:dashboard api version not supported, use /apis/dashboard.grafana.app/v2alpha1/namespaces/default/dashboards/XXX instead}

Having the same issues on Grafana 12.3, but the API version is now v2beta1.

● grafana - Get dashboard panel queries (MCP)(uid: "ad8nwk6")
  ⎿  Error: MCP error -32603: get dashboard by uid: get dashboard by uid ad8nwk6: [GET /dashboards/uid/{uid}][406] getDashboardByUidNotAcceptable {"message":"dashboard api version not supported, use /apis/dashboard.grafana.app/v2beta1/namespaces/default/dashboards/ad8nwk6
     instead"}

I was quite looking forward to build some things with this :-/

[sd2k]

I am hoping that #481 will resolve this. If anyone having this issue is able to test it out that would be appreciated.