Hi,
I’m trying all different ways to have grafana mcp working with cursor cloud agents to fully automate my personal AI SRE but I’m stuck. Our Grafana instance is behind cloudflare ZTNA and despite passing the right headers with all the service tokens to call the mcp (I tested from multiple places outside of ZTNA and it’s working) cursor is just ignoring it and says that the MCP is not even available. What am I missing here?
Am I the only one stuck with this? Thank you.
The issue you’re hitting is a known bug where team-configured command-based (stdio) MCP servers fail to start in cloud agent sessions. Our team is actively working on MCP reliability in cloud agents and this is being tracked.
Regarding the Cloudflare ZTNA piece: since mcp-grafana runs as a process on the cloud agent VM and uses your GRAFANA_EXTRA_HEADERS to authenticate requests, the Cloudflare service tokens should handle access correctly once the MCP process starts. So ZTNA shouldn’t be a separate blocker here.
A few things to check in the meantime:
-
Verify cloud agent access is enabled for the MCP: On cursor.com/settings, make sure the grafana MCP server has the “Cloud Agents” toggle enabled (not just the IDE toggle)
-
If you need this urgently, the Cursor TypeScript SDK supports passing MCP servers via inline config. You can configure your MCP directly in the SDK call, bypassing the dashboard resolution entirely.
I’ll follow up here once the underlying fix ships. Let me know if you have any questions.
Verify cloud agent access is enabled for the MCP: On cursor.com/settings, make sure the grafana MCP server has the “Cloud Agents” toggle enabled (not just the IDE toggle)
Hi, I don’t see this option. When I go to https://cursor.com/settings it redirects me to https://cursor.com/dashboard and I don’t see that option anywhere. As I showed above this is a STDIO mcp I have and there’s no option anywhere to enable a "“Cloud Agents” toggle.
For team-level stdio MCPs configured via the admin dashboard, there isn’t a separate “Cloud Agents” toggle to flip. Your MCP should be available automatically once it’s configured at the team level.
The core issue here is the bug I mentioned: the cloud agent runtime isn’t properly starting team-configured stdio MCPs, even though they show as configured. A fix for this has been implemented internally and is working through review. I expect it to ship soon.
In the meantime, the SDK inline config approach (option #2 from my earlier reply) remains the only reliable workaround if you need this unblocked now. I’ll post back here once the fix is live.