nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Atlassian MCP connector times out on connect from Claude (Cowork)

Parichit Sharma

Using the Atlassian connector in Claude (Cowork desktop app), the connection fails at session start with CONNECT_TIMEOUT / REQUEST_TIMEOUT. Jira tools are then unavailable for the session. Disconnecting, reconnecting, and starting new sessions haven’t reliably fixed it.

Is this a known issue? Anyone else seeing it?

Accepted answers

Ciro

Hey. You're not alone: Atlassian had an MCP incident yesterday afternoon. The Rovo status page lists "Degraded performance of Rovo MCP" from 15:30 to 18:25 UTC on Oct 21, and the 16:35 update says affected users may see "timeout issues", which matches CONNECT_TIMEOUT / REQUEST_TIMEOUT at session start. A fix went out and it's marked resolved.
The "trouble showing permissions" screen in the reply above came in the same window, so I'd retry once from scratch: remove the connector, start a new session, add it back and pick the site again.
If it still times out today, it's no longer the incident, so open a ticket with the exact time it failed and your client logs.