MCP Server Timeout not working

[matirojasg]

Hey guys, is there any email contact to talk? Im Matias, from Latam Airlines, we are using Continue and an internal proxy to connect LLMs from different providers, and also custom MCP servers (+10). We have advanced MCP tools that want to use via continue, but we are facing a timeout problem. I think the timeout parameter for MCP server is not working and is limited to 60 seconds, so we cannot connect to our processes 🙁 Thanks!

[uinstinct]

I tried this now and connectionTimeout parameter seems to be working.

Just a note: If you are using ollama, ensure your ollama servers are running otherwise the mcp connection might abort. In that case, you would need to reload the mcp connection.

mcpServers:
  - name: memory mcp
    command: npx
    args:
      - -y
      - "@modelcontextprotocol/server-memory"
    connectionTimeout: 180000 // 3 minutes (try setting a little higher) <---- this were the connection timeout should be placed 

can you please give it another try?

[matirojasg]

We are using the streamable mode, is it working too in that case?

[matirojasg]

We tried using both modes (sse and streamable) and is not working.

[uinstinct]

can you post a screen recording with the webview console and the extension in the video? it help debug better and see what might be happening

[harmonietrindal]

i'm using codex on windows, and having the same problem🖐  MCP client for supabase failed to start: request timed out

[bigXiXi9202]

#7067 the same problem

[uinstinct]

Can you retry a few times with the reload options beside the MCP to see if it is timing out every time?

[jamesev15]

@uinstinct would you take a look on this video? It is the timeout issue, thanks!

[uinstinct]

Thanks @jamesev15 ! Appreciate the video.
I understand the issue now. connectionTimeout was initially meant only for connecting to the mcp servers.
Since your requirements are also for it to work for long running tasks, I will create a PR which adds this ability.

[matirojasg]

Thanks!