Where does the bug appear (feature/product)?
Somewhere else…
Describe the Bug
When you create an MCP Server through the Automations flow where you add tools, after creation that MCP server is set that way forever and you can no longer update it. That means if you didn’t configure it correctly, there’s nothing you can do, including delete it.
When I try to configure an MCP server through the Dashboard → Integrations view, nothing I add persists to the panel.
This is most obvious with the Figma MCP. If you try to add it in the Automations flow, you’ll get a forbidden error (and can’t authenticate to the remote). If you add it in Integrations flow - it is into the ether. Adding as a plugin doesn’t allow you to authenticate in-browser, so the MCP isn’t available for Automations or Cloud Agents either.
Steps to Reproduce
Create a new automation
Add a custom MCP server, like figma (I can’t put URL here, forums restricting me)
Give it a name
Click Save
It will error with 403. You can delete the server from the tools list on the automation, but you cannot edit or delete the server itself. It’s in the list forever.
Go to cursor.com/dashboard?tab=integrations
Click “Add MCP”
Add the same Figma MCP server as above
Save
Its gone
Expected Behavior
The server should be visible and editable. I’d also expect to be able to authenticate to the Figma plugin for my Cloud Agent/Automations to use.
Operating System
MacOS
Version Information
For AI issues: which model did you use?
N/A
For AI issues: add Request ID with privacy disabled
N/A
Additional Information
N/A
Does this stop you from using Cursor
No - Cursor works, but with this issue
Hi Nick,
Thanks for reporting this. We’ve identified the issue: a recent update inadvertently removed the dashboard UI for managing user-scoped MCP servers. The backend support is still in place, but the management surface to view/edit/delete those servers isn’t currently available.
As a result:
-
MCP servers created during Automations setup can’t be edited or deleted right now because there isn’t a UI to manage them.
-
MCP servers added from the dashboard may not appear as expected for non-admin users, since the current view is limited in what it surfaces.
On the Figma MCP 403: that’s a separate, known limitation related to OAuth-based authentication with certain remote MCP servers in the Automations/Cloud Agents context, and it’s being tracked independently.
We’ve flagged both items internally and will update this thread once a fix is available.
In the meantime, if you’re a team admin, you can manage team-scoped MCP servers from the dashboard integrations page. For user-scoped servers created during automation setup, there isn’t a workaround until the management UI is restored, as of now.
Best,
Mohit
3 Likes
Hi @mohitjain ,
I still have issues with adding team-level MCPs as tools to an automation → it cannot even list mcp servers, let alone access secrets that are injected into mcp definitions.
Is there any update on this being fixed, as it really breaks the feature for us 
Hi Petar,
This is a different issue from the one in this thread – your report about team-level MCPs not being accessible in automations is being tracked in Automations is not able to use the custom MCP, where you’ve already posted. I’ll help you out there!
1 Like
Hey!
this issue still persists. Are there plans to fix this? We cannot use the platform for now.