Tool Timeout Persists Despite Increased MCP Timeout Settings

[DoiiarX]

My xxx.tools.yyy tool consistently times out after 15 seconds with the error: MCP operation on 'tools:http' timed out after 15s.

Context:
I have attempted to increase the MCP timeout settings.

Configuration Attempts:

1. Global env in UTCP file:

   "env": {
     "MCP_TIMEOUT": "600000",
     "MCP_SERVER_TIMEOUT": "60000"
   }

2. Tool-specific config and timeout:

   {
     "name": "xxx",
     "call_template_type": "mcp",
     "config": {
       "mcpServers": {
         "tools": {
           "transport": "http",
           "url": "zzzz",
           "env": {
                   "MCP_TIMEOUT": "600000",
                   "MCP_SERVER_TIMEOUT": "60000"
                 }
         }
       }
     },
     "timeout": 600000
   }

Expected Result:
The tool should respect the configured MCP_TIMEOUT and MCP_SERVER_TIMEOUT values, allowing for a longer execution time than 15 seconds.

Actual Result:
The timeout consistently occurs after 15 seconds, indicating that the new timeout configurations are not being applied or are being overridden.

[DoiiarX]

#15

and the name xxx.tools.yyy not follow this

[pro-vi]

I have a PR up to fix this. For a workaround before it gets merged:

Point your MCP server config to a local build with the fix applied (use my fork or make your own)

1. Clone https://github.com/pro-vi/typescript-utcp (branch fix/configurable-mcp-timeout)
2. bun install && bun run build
3. Update code-mode-mcp/package.json to use "@utcp/mcp": "file:/path/to/typescript-utcp/packages/mcp"
4. Rebuild and point your .claude.json or .mcp.json to the local dist/index.js
5. Add "timeout": 300 or smth to your server config in .utcp_config.json
6. Restart Claude Code and test