Atlassian MCP server stopped working with VS code

Vartika Sharma

Facing problems with both versions of the Atlassian MCP server.

The older SSE endpoint (<a href="https://mcp.atlassian.com/v1/sse" rel="noopener nofollow noreferrer" target="_blank">https://mcp.atlassian.com/v1/sse</a>) was working fine last week, but now after successful authorization it just keeps loading and never returns any responses. There are no clear errors

The newer MCP HTTP endpoint (<a href="https://mcp.atlassian.com/v1/mcp" rel="noopener nofollow noreferrer" target="_blank">https://mcp.atlassian.com/v1/mcp</a>) authorizes successfully but fails with errors like “Session not found” (404).

So at the moment:

• /v1/sse often hangs indefinitely after auth

• /v1/mcp drops sessions even though OAuth succeeds

 

Are these endpoints still considered beta/experimental?
Is there any recommended stable endpoint or known outage/limitation we should be aware of?

Dr Valeri Colon (Connect Centric)

Welcome to the community @Vartika Sharma Both MCP endpoints are still unstable and behave like beta services. The SSE endpoint (/v1/sse) can hang after OAuth when the stream never opens cleanly, and the HTTP endpoint (/v1/mcp) often drops sessions with “Session not found.” This isn’t a client issue—it's a backend reliability problem Atlassian is actively working on. There’s no “stable” endpoint today. If both fail, capture timestamps and open a Support ticket so they can check the MCP service for your tenant.