mirror of
https://github.com/mudler/LocalAI.git
synced 2026-11-06 04:23:15 -05:00
A tool call through an MCP connector was cut after the connector package default of 60 seconds, while the model's own MCP servers allow 360 seconds. Research and document tools behind a connector take minutes, so a saved agent lost them mid-turn with "connection closed: calling tools/call: client is closing" and the model fell back to a weaker tool. The connector service now gets the MCP tool timeout the rest of LocalAI uses (DistributedConfig.MCPToolTimeoutOrDefault, 360 s by default). The package default and the per-call output cap are unchanged. Tests in core/application start the connector service on JSON stores against a slow MCP server: the timeout defaults to the MCP tool timeout, a tool slower than the old cap but within the timeout returns, and a tool past the timeout is still stopped. Docs: chats-connectors.md, "How chats use them". Assisted-by: Claude Code:claude-opus-5-5 Signed-off-by: Stefan Walcz <stefan.walcz@walcz.de>