Increase MCP timeout from 60secs to 5mins Or make it configurable ( Chat agent with MCP errors out )

We have MCP’s that does code execution and on fly resource creation. Tool we have can execute more than 60 secs . While building the chat agent and linking the action, If the Tool execution takes more than a min , we ‘ll get internal server error with 500 code.
There are lot of IDE tool which make MCP client timeput value configurable. Can quicksuite also provide the same ?

Hi @szkaran

Welcome to the Quick community!

Quick’s Model Context Protocol (MCP) integration has a fixed execution timeout of 60 seconds for MCP operations. If a tool execution exceeds this 60 second limit, it automatically fails (often with internal server error 500 or HTTP 424 error). Currently, this timeout is not configurable or extendable within Quick.

I will mark this as a feature request to promote visibility to the support team.

Please refer to the below documentation this might be helpful for you.

Will the Quicksuite MCP client listen to partial updates from MCP tools ? like process update and keep this connection active ?
Trying to check if we can stream some output from MCP server to client and keep this session active

Hi @szkaran

No, Quick’s MCP client does not support partial updates or process streaming from MCP tools to maintain active connections during long executions, which aligns with the fixed 60-second timeout limitation.

Similar behavior has been discussed in the community forum on streaming support.