MCP Server Timeout not working

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!

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?

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

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

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

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

#7067 the same problem

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

@uinstinct

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

@jamesev15

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.

Thanks!

Any new about this issue?

we have a PR which in in review. so it should be merged soon

@uinstinct

@uinstinct thanks for that! I've checked that the PR was merged into the submodule(¿?) config-yaml. That is the same of continue extension in vscode? I've tried the 1.2.3 release version, but it seems the PR you've done is still missing in that version

I have not checked the pre-release yet but I think it should be on the pre-release.

Navigation Menu

Repository navigation

MCP Server Timeout not working #7509

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

MCP Server Timeout not working #7509

Description

Activity

uinstinct commented on Sep 2, 2025

matirojasg commented on Sep 2, 2025

matirojasg commented on Sep 2, 2025

uinstinct commented on Sep 2, 2025

harmonietrindal commented on Sep 2, 2025

bigXiXi9202 commented on Sep 4, 2025

uinstinct commented on Sep 4, 2025

jamesev15 commented on Sep 4, 2025

uinstinct commented on Sep 4, 2025

matirojasg commented on Sep 4, 2025

matirojasg commented on Sep 10, 2025

uinstinct commented on Sep 10, 2025

jamesev15 commented on Sep 12, 2025

uinstinct commented on Sep 15, 2025

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions