IntelliJ MCP connection

[Dorin_Goldin]

Hi,

Maybe someone encountered this problem..?

When trying to connect Atlassian MCP to IntelliJ we encountered this issue:

[7884] Fatal error: SseError: SSE error: TypeError: fetch failed: Headers Timeout Error
at _eventSource.onerror (file:///C:/Users/xxxx/AppData/Local/npm-cache/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-OXNXVROF.js:12899:23)
at EventSource.scheduleReconnect_fn (file:///C:/Users/xxxx/AppData/Local/npm-cache/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-OXNXVROF.js:12800:53)
at file:///C:/Users/xxxx/AppData/Local/npm-cache/_npx/705d23756ff7dacc/node_modules/mcp-remote/dist/chunk-OXNXVROF.js:12650:174 {
code: undefined,
event: {
type: 'error',
message: 'TypeError: fetch failed: Headers Timeout Error',
code: undefined,
defaultPrevented: false,
cancelable: false,
timeStamp: 306624.4692

 Tried adding headers manually to json.mcp and updating IntelliJ to latest.

any thoughts?

Thanks!

[Tomislav Tobijas]

Hi @Dorin_Goldin ,

I'm no expert here, so I'll move this question to Rovo forum group so someone can chime in.
But, based on the error, you might want to check the following:

1. Check network and service availability > ensure a stable internet connection and that no firewall, proxy or VPN is blocking outbound connections
   MCP is beta, and it may experience downtime
2. Verify MCP server URL > double-check that you're using the correct endpoint:

   https://<mcp-server-domain>/v1/sse

3. Update tools and dependencies > make sure everything is up to date (IntelliJ and MCP-related plugins)
   You could run MCP commands if you're using Node.js or npm to check the versions.
4. Authentication > if/when prompted for authorization, ensure that local OAuth callbacks are not blocked by security software

Some resources might be helpful when talking about MCP:

• Help Center / Atlassian MCP 
• Atlassian Rovo MCP Server (forum discussion group) 

Cheers,
Tobi

[Dorin_Goldin]

Hi Tobi,

Thank you for your replay!

1. Checked network configs - also added our company certificate to the configuration to prevent certificate issue. 

In vs code the problem did not reproduced.

2. url is a remote server url to Atlassian's mcp : https://mcp.atlassian.com/v1/sse

3. latest always! :)

4. Authentication triggers (not every start ) 

Any other though or ideas? 

Dorin

[Tomislav Tobijas]

Thanks for the info provided @Dorin_Goldin !

I'm out of ideas, unfortunately :/
TBH, I haven't worked with MCP extensively - I only did the initial setup and tested it briefly.

There's only this troubleshooting article that potentially might help: Troubleshooting and verifying your setup

But, in the end, I would probably recommend using those official support channels related to MCP, as the official support team can probably help you out 👨‍🔧