CERBERUS/LibreChat
1
0
Fork 0
mirror of https://github.com/danny-avila/LibreChat.git synced 2026-07-01 11:53:55 +00:00
Code Issues Projects Releases Packages Wiki Activity Actions 7

fix(mcp): keep app tool calls alive on progress and always send tool input

Browse source 
Sets resetTimeoutOnProgress on app-initiated tool calls so a long-running tool
that keeps streaming MCP progress is not aborted at the fixed connection timeout,
matching the model-initiated callTool path.

Always sends the tool-input notification before the result, even when the tool
has no arguments. MCP Apps expect ui tool-input exactly once before the result,
so apps that initialize from ontoolinput no longer stay blank for no-argument
tools.
This commit is contained in:
Dustin Healy 2026-06-25 11:09:43 -07:00
parent c9f5441b0d
commit 4261adcd5d
2 changed files with 6 additions and 6 deletions
Download patch file Download diff file Expand all files Collapse all files

10
client/src/hooks/MCP/useAppBridge.ts
View file

@ -155,11 +155,11 @@ export function useAppBridge(
bridge.oninitialized = async () => {
const args = toolArgsRef.current;
const result = toolResultRef.current;
if (args) {
await bridge!
.sendToolInput({ arguments: args })
.catch((err: unknown) => logger.error('[MCP App] sendToolInput failed', err));
}
// MCP Apps expect tool input exactly once before the result, even for no-argument tools,
// so apps that initialize from ontoolinput always receive it.
await bridge!
.sendToolInput({ arguments: args ?? {} })
.catch((err: unknown) => logger.error('[MCP App] sendToolInput failed', err));
if (result) {
await bridge!
.sendToolResult(result as never)

2
packages/api/src/mcp/MCPManager.ts
View file

@ -966,7 +966,7 @@ Please follow these instructions when using tools from the respective MCP server
},
},
CallToolResultSchema,
{ timeout: connection.timeout },
{ timeout: connection.timeout, resetTimeoutOnProgress: true },
);
return result;