Compatibility change · breaking
Atlassian now requires Streamable HTTP for Rovo MCP connections after retiring its legacy SSE endpoint on June 30, 2026. Observed July 11, 2026 and published after review on July 11, 2026.
Operator action
This is a compatibility action, not a security, availability, or provider-performance guarantee.
Verify that the client uses the current Streamable HTTP endpoint and remove legacy SSE configuration before reconnecting.
chg_6e7f4d1a2b3c4d5e8f9012a3b4c5d6e7Retrospective event: the effective date predates ResolveMesh observation.
Effective date: June 30, 2026.
1 reviewed fact delta
Values are projected from the approved typed ledger; the page does not fetch or reinterpret the source at request time.
| Field | Before | After |
|---|---|---|
| transports | SSE, STREAMABLE_HTTP | STREAMABLE_HTTP |
Affected surfaces
Only the named records are included. ResolveMesh does not infer that every unlisted client or provider is unaffected.
Local and remote MCP client with HTTP, legacy SSE, stdio, OAuth, and explicit project trust controls.
IDE MCP client supporting local stdio and remote SSE or Streamable HTTP connections.
Terminal MCP client supporting stdio, SSE, Streamable HTTP, and browser-based OAuth discovery.
Atlassian's hosted server for Jira, Confluence, Compass, and other permitted product actions.
Official evidence
The source owner can revise documentation after this observation. Verify the current page before a production change.
Official documentation used to approve this compatibility fact delta.
Read the primary sourceThe same event is available without page markup at the stable change-ID endpoint.
GET /v1/compatibility-changes/chg_6e7f4d1a2b3c4d5e8f9012a3b4c5d6e7