Failed to start HTTP MCP server at https://mcp.atlassian.com/v1/native/mcp

[David Andrews]

Hi,

Rovo used to work (not very well though), but now I get the following error which appears to be an authentication issue.

╭─ Failed to start third-party MCP server ─────────────────────────────────────────────────────────────────────────────╮
│ │
│ Failed to start HTTP MCP server at https://mcp.atlassian.com/v1/native/mcp │
│ │
│ Tools from this server will not be available. │
│ │
╰──────────────────────────────────────────────────────────────────────────────────────────────────────────────────────╯
Error reading SSE stream:
Traceback (most recent call last):
File "httpx/_transports/default.py", line 101, in map_httpcore_exceptions
File "httpx/_transports/default.py", line 271, in __aiter__
File "httpcore/_async/connection_pool.py", line 407, in __aiter__
File "httpcore/_async/connection_pool.py", line 403, in __aiter__
File "httpcore/_async/http11.py", line 342, in __aiter__
File "httpcore/_async/http11.py", line 334, in __aiter__
File "httpcore/_async/http11.py", line 203, in _receive_response_body
File "httpcore/_async/http11.py", line 217, in _receive_event
File "httpcore/_backends/anyio.py", line 32, in read
File "contextlib.py", line 162, in __exit__
File "httpcore/_exceptions.py", line 14, in map_exceptions
httpcore.ReadTimeout

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
File "mcp/client/streamable_http.py", line 287, in _handle_sse_response
File "httpx_sse/_api.py", line 39, in aiter_sse
File "httpx/_models.py", line 1031, in aiter_lines
File "httpx/_models.py", line 1018, in aiter_text
File "httpx/_models.py", line 997, in aiter_bytes
File "httpx/_models.py", line 1055, in aiter_raw
File "httpx/_client.py", line 176, in __aiter__
File "httpx/_transports/default.py", line 270, in __aiter__
File "contextlib.py", line 162, in __exit__
File "httpx/_transports/default.py", line 118, in map_httpcore_exceptions
httpx.ReadTimeout

I was able to:

curl -X POST \
-H "Authorization: Bearer {TOKEN}" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-H "Mcp-Session-Id: 56d6db37-400d-40e2-b386-4bd2193075d3" \
-d '{
"jsonrpc": "2.0",
"method": "getWorkspaces",
"params": {},
"id": 1
}' \
https://mcp.atlassian.com/v1/native/mcp
{"jsonrpc":"2.0","error":{"code":-32001,"message":"Session not found"},"id":null}%

This leads me to believe it is an authentication issue.

I have tried:

- Uninstalling acli, clearing old cache and configs, reinstalling and generating a new api token.

Other issues:

- Initial Startup: When Rovo was working, it took forever to initially load - even on small codebases.

- Approvals: Even after approving permissions, it still continuously asks for permissions.

- It fails or errors out quite often.

The most value I was able to extract when working was creating documentation. Other than that has been a bit underwhelming. I know Atlassian has a great team and looking forward to seeing improvements.

[Dr Valeri Colon _Connect Centric_ · Accepted solution]

Hi @David Andrews —welcome to the community and thanks for the detailed report.

You're correct: the "Session not found" response from your curl test confirms this is likely an authentication/session issue between the CLI and the MCP server. This can result from an expired or invalid session token, especially if CLI configs were reset.

Since this is the second post I've seen from a user on this I've post detailed troubleshooting tips and it may be a good idea to open a ticket https://support.atlassian.com/ and check out the Dev Cli Beta community. 

Here’s what you can do next:

1. Reset authentication completely using:

   acli rovodev auth logout

   acli rovodev auth login --reset

2. Delete old session/config cache:
   Remove or clear the .acli folder from your home directory (e.g., ~/.acli).

3. Ensure time sync: Authentication may fail if your system clock is out of sync. Ensure your machine’s time is correct.

4. Check for firewall or proxy: Network interruptions can cause stream timeouts or session loss. If you're behind a proxy, try configuring acli with proxy settings or test on a different network.

5. Known issues: Slow startup and repeated permission prompts are known limitations during the current beta. These are being addressed, but there’s no fix yet.

You're not alone in finding doc generation most useful at this stage—thanks again for sharing clear, constructive feedback.