I have a connection to Atlassian’s MCP server that was working with Cursor Automations for a few days, but now is stuck in the failing state. I have logged out and back in, deleted the MCP server, etc but it’s stuck. I’m unable to use these automations now as their purpose is to leverage information in Jira.
The refresh token should work or at the absolute minimum, I should be able to reset the state and reconnect manually until the bug around refresh tokens not working is fixed.
Hey, thanks for the report. This is a known issue: refresh tokens for OAuth MCP servers, especially Atlassian where tokens expire quickly, don’t refresh automatically in Automations, and the UI doesn’t let you reset state and re-auth.
This was already fixed in the IDE, but the issue still remains in Automations on the web. The team is aware, and I’ve shared your report again to help with prioritization. No ETA yet, but we’re tracking it.
Hey thanks Dean. Does that mean there’s a way for me to fix these via the IDE when they expire? Or do OAuth connections for Automations permanently break once the first access token expires?
Unfortunately, right now the IDE fix for refresh tokens doesn’t apply to Automations. Automations uses a separate flow, so we can’t fix it via the IDE either.
What’s happening today is this: once the access token expires in Automations, the OAuth connection gets stuck in a dead state. The Disconnect button doesn’t show up, and you can’t reset or reconnect. That’s the root cause.
The team is aware, but there’s no workaround for Automations at the moment. I’ve shared your case for prioritization, especially since this is blocking a team of 89 users.
