HTTP+SSE Deprecation Notice

[#1]

The HTTP+SSE transport for the Atlassian Rovo MCP Server at https://mcp.atlassian.com/v1/sse is deprecated and will remain available for backward compatibility until 30 June 2026. New and existing integrations should use the Streamable HTTP transport at https://mcp.atlassian.com/v1/mcp instead.

Why we’re deprecating HTTP+SSE

We’re deprecating HTTP+SSE transport in favor of Streamable HTTP due to reliability limitations and to align with the MCP specification.

Fragile during network drops; SSE sessions are harder to recover cleanly (e.g., “No connection established for request ID”, “SSE error: Non-200 status code”).

Protocol alignment: the MCP specification prioritises Streamable HTTP. HTTP+SSE remains only for backward compatibility and won’t see future improvements.

How to migrate

Note: All existing access and admin controls will continue to be applicable on the new Streamable HTTP endpoint for the Atlassian Rovo MCP Server.

1. Update your endpoint - Migrate from https://mcp.atlassian.com/v1/sse to https://mcp.atlassian.com/v1/mcp

2. Specify the transport type (if applicable) - Different clients may have different requirements for the transport type. In your MCP client or mcp-remote config, set the transport type to Streamable HTTP.

E.g.

{
  "mcpServers": {
    "atlassian-mcp": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.atlassian.com/v1/mcp",
        "--transport",
        "http-first",
      ]
    },
  }
}

Have questions or need migration help? Comment below - our MCP team will be actively monitoring this thread. Thank you for helping keep our MCP integrations reliable and up to date.

[Nicola Pacini]

Hi @Jemma Swaak in Visual Studio Code (with Amazon Q) you can set the MCP with http or stdio transport, I guess http is fine for this new setup, right?

Thanks!

[Sunil Kunisetty]

yes, http will work

[John Johnson]

Thanks for the detailed migration guide! This is really helpful for anyone
working with MCP integrations. I manage a tech platform at
Free Fire feedback program APK where we handle APK delivery and early access
features for Android users, and keeping integrations reliable is always
a top priority for us too. The shift from HTTP+SSE to Streamable HTTP
makes complete sense  SSE session recovery has always been a pain point,
especially when dealing with unstable network conditions. The fragile
connection behavior during network drops is something our team has
experienced firsthand as well. Good to see Atlassian proactively aligning
with the MCP specification rather than waiting until the last minute.
The migration steps are clear and straightforward  appreciate the
code snippet for the mcp-remote config. Will be updating our integrations
well before the June 30 deadline. Thanks to the Atlassian MCP team for
keeping the community informed! 👍