Atlassian MCP Stuck on "Loading"

Support Help
,
1

Hi,

I successfully installed the Atlassian MCP.
However, in Settings > Tools & MCPs, the Atlassian MCP stays stuck on “Loading” and eventually shows “Show errors.”

2026-07-28 11:13:07.737 [info] [MCPService] [MCPService] createClient: identifier="user-atlassian", serverName="atlassian"
2026-07-28 11:13:07.739 [info] [MCPService] [MCPService] createClient completed for server: user-atlassian, statusType=initializing, success=true
2026-07-28 11:13:43.420 [warning] [Shared MCP process] Transient error connecting to streamableHttp server: MCP error -32001: Request timed out
2026-07-28 11:13:43.423 [warning] [Shared MCP process] MCP HTTP exchange failed
2026-07-28 11:13:43.432 [warning] [Shared MCP process] MCP HTTP exchange failed

This issue only occurs when I’m connected to my company’s network. If I switch to my home network, the Atlassian MCP loads and works normally.

I’m wondering if there are any network settings, proxy configurations, firewall rules, or allowlisted domains that need to be configured so that Cursor can successfully load the Atlassian MCP on a corporate network.

Has anyone encountered a similar issue, or is there any troubleshooting guidance you can recommend?

Thank you!

6

Hey James, this is the classic corp-network signature for third-party MCPs. The Atlassian MCP is a direct Cursor → mcp.atlassian.com streamable HTTP connection, so your corp firewall / SSL-inspecting proxy has to be configured for it explicitly.

Three asks for your IT / security team:

  1. Allowlist mcp.atlassian.com, auth.atlassian.com, api.atlassian.com, id.atlassian.com.
  2. Exclude those hosts from SSL inspection and response buffering - streamable HTTP needs unbuffered streaming (Zscaler-style appliances tend to break it).
  3. Confirm your corporate root CA is trusted in the OS cert store (Windows cert store / Keychain).

Worth trying inside Cursor in the meantime: Cursor Settings > Network > Enable HTTP/1.1, then fully quit and reopen.

Docs: Network Configuration.

If that doesn’t clear it, share the log line right after MCP HTTP exchange failed - the specific error (SELF_SIGNED_CERT_IN_CHAIN, ENOTFOUND, ECONNRESET, etc.) will narrow it down.

7

Hi Mohit,

It works!
I have contacted our IT to complete the setup you mentioned.
The MCP works perfectly now.

Thank you for your help.