I’ve tried really hard to configure cloud agents to use my Sentry MCP and a custom MCP for my API logs and the agents are just never able to discover the tools. They always report that ListMcpResources() came back empty, even though I have MCPs enabled before kicking off the agent.
I’ve tried creating both personal and team environments for the repo, grant MCP access for both the user and team, creating and deleting mcps etc and nothing has worked.
We’re really trying to use automations + cloud agents for bug resolution customer support and are hitting a wall.
Steps to Reproduce
Add the Sentry MCP from the marketplace, authorize, enable it for a new cloud agent in cursor.com/agents, kick off the agent and ask it something simple: please use the sentry mcp to list the top 5 issues in project XYZ. Agent replies that it doesn’t have access to any mcp tools.
Hi @ishaan Thank you for reporting and I apologize for the frustration this has caused. This is a known class of issue that is being actively worked on. However, I do have some steps that might help. Do you want to try setting this up as a local automation first, confirming that it works successfully on your local instance of Cursor with all of the MCPs hooking in and fetching data, and then try sending it to Cloud. If you search for Automations in Settings, you’ll see the list. Note that you’ll need to set up the Automation completely before you see the Send to Cloud Icon.
Perhaps for both your existing Cloud Agent setup and the Send to Cloud Automation one. This may not lead us to a guaranteed resolution but it’s worth a shot!
Thanks for the follow up. I’ll look into the local automation setup. Currently we want to trigger cloud agents directly with MCP access (from slack, web, or cursor glass), and then want to build automations once we determine what works. So we’re getting stuck at the cloud agents not having the tools to achieve it’s goals.
