The latest updates on your projects. Learn more about Vercel for GitHub.

1 Skipped Deployment

Project	Deployment	Actions	Updated (UTC)
docs	Skipped		Feb 1, 2026 1:36am

Greptile Overview

Greptile Summary

Added timeout parameter to the MCP SDK's callTool method to override its hardcoded 60-second default timeout with the configured timeout value (defaults to 600000ms/10 minutes if not specified).

Key Changes:

• Modified McpClient.callTool() to pass timeout options as the third parameter to this.client.callTool()
• Uses this.config.timeout || 600000 to ensure a sensible fallback
• Addresses issue where long-running MCP tool calls were timing out prematurely at 60s despite server configs having different timeout values (typically 30s default or custom values)

Confidence Score: 5/5

• This PR is safe to merge with minimal risk
• The change is a straightforward bug fix that correctly passes the timeout parameter to the SDK method. The implementation follows the SDK's API signature, uses existing configuration values with a sensible fallback, and addresses a real issue where tool calls were timing out prematurely.
• No files require special attention

Important Files Changed

Sequence Diagram

sequenceDiagram
    participant Service as McpService
    participant Client as McpClient
    participant SDK as MCP SDK Client
    participant Server as MCP Server
    
    Note over Service: Config has timeout: 30000ms or custom
    Service->>Client: createClient(config)
    Note over Client: Stores config with timeout
    Client->>SDK: new Client()
    Service->>Client: callTool(toolCall)
    Note over Client: Uses this.config.timeout || 600000
    Client->>SDK: callTool(params, undefined, {timeout})
    Note over SDK: Overrides 60s DEFAULT_REQUEST_TIMEOUT_MSEC
    SDK->>Server: HTTP Request with configured timeout
    Server-->>SDK: Tool result
    SDK-->>Client: sdkResult
    Client-->>Service: McpToolResult