[BUG] Claude Desktop: 4-minute hard timeout on remote/hosted MCP tool calls — not configurable

Preflight Checklist

• [x] I have searched existing issues and this hasn't been reported yet
• [x] This is a single bug report (please file separate reports for different bugs)
• [x] I am using the latest version of Claude Code

What's Wrong?

Claude Desktop enforces a hard 4-minute wall-clock timeout on MCP tool calls for Anthropic-hosted remote connectors (Chrome, Facebook Ads, Shopify, Klaviyo, Supermetrics, Pinterest, Adobe, etc.). When a tool call hits the wall, Claude reports "No result received from the Claude Desktop app after waiting 4 minutes" and the call fails.

Unlike locally-bundled MCP servers (where DEFAULT_REQUEST_TIMEOUT_MSEC can be patched in protocol.js), these remote connectors have no locally accessible SDK files. A full filesystem search confirms this:

find ~ /Applications -name "protocol.js" -path "/modelcontextprotocol" 2>/dev/null

Returns nothing for remote connectors

The timeout is enforced inside the Claude Desktop binary itself and is not configurable by the user through any mechanism. The timeout field in claude_desktop_config.json is also ignored for remote connectors.

Affected connectors: Claude in Chrome, Facebook Ads MCP, Pinterest, Shopify, Klaviyo, Supermetrics, Adobe for creativity.

Related issues: #5221, #22542, #43791, #44032

What Should Happen?

MCP tool call timeouts should be configurable for remote/hosted connectors, consistent with how Claude Code CLI handles MCP_TOOL_TIMEOUT. At minimum, the default timeout should be increased to 10 minutes for remote connectors performing complex operations like DOM inspection and JS execution.

Error Messages/Logs

No result received from the Claude Desktop app after waiting 4 minutes

Steps to Reproduce

1. Open Claude Desktop (macOS) with any remote/hosted MCP connector enabled (Chrome, Facebook Ads, Shopify, Klaviyo, Pinterest, Adobe, Supermetrics)
2. Trigger a tool call that involves DOM inspection, JS execution, or any multi-step operation
3. Wait — the call will hard-fail at exactly 4 minutes regardless of whether the server has responded
4. Observe error: "No result received from the Claude Desktop app after waiting 4 minutes"

Note: This cannot be fixed by patching protocol.js as remote connectors have no locally bundled SDK files. A full filesystem search (find ~ /Applications -name "protocol.js" -path "/modelcontextprotocol") returns nothing for these connectors.

Claude Model

Sonnet (default)

Is this a regression?

No, this never worked

Last Working Version

_No response_

Claude Code Version

Claude 1.9659.2 (390d6c) 2026-05-28T21:50:01.000Z

Platform

Other

Operating System

macOS

Terminal/Shell

Terminal.app (macOS)

Additional Information

This bug affects Claude Desktop's built-in remote MCP connectors, not Claude Code CLI. The Platform dropdown above doesn't have a "Claude Desktop" option so "Other" is selected.

Filesystem investigation confirmed no patchable protocol.js exists for remote connectors:

find ~ /Applications -name "protocol.js" -path "/modelcontextprotocol" 2>/dev/null
(returns empty — only the Clarity Desktop Extension has a local SDK)

The issue is reproducible consistently on every complex tool call across Chrome, Facebook Ads, Pinterest, Shopify, Klaviyo, Supermetrics, and Adobe connectors. The timeout hits at exactly 4 minutes every time.

Related issues: #5221, #22542, #43791, #44032