Home / Fixes

MCP tool call times out on slow servers

Error: Tool call timed out

What causes it

Some tools are slow. In our runs DeepWiki ask_wiki_question took about 15 s, GitMCP docs fetch about 9 s, and Cloudflare Docs search 3 to 4 s. In batch 2, Cohere Docs took about 20 s per answer, GitMCP for Next.js about 19 to 27 s per docs search, and Jina about 7 s to read one page.

How to fix it

1. Raise your client tool timeout above 20 s for these servers.
2. Prefer the faster tool for the job (DeepWiki read_wiki_structure, GitMCP search_generic_code).

Where we hit it

• grep.app MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT
• GitMCP for Next.js MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT
• Cohere Docs MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT
• Jina AI MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT
• DeepWiki MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT
• GitMCP (generic docs endpoint) MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT
• Cloudflare Docs MCP test report (tested Oct 16, 2026). Setup: Claude, Claude Code, Cursor, VS Code, ChatGPT

Related fixes

• MCP tool results too large: context window blown by one call
• GitMCP returns "No documentation found."
• MCP error -32601 Method not found on resources/list
• MCP search returns results for nonsense queries
• MCP tool says "Please set your API key" on a no-signup server
• MCP error: "Error POSTing to endpoint: <!DOCTYPE html>"
• MCP URL reader returns a 404 page as a normal result

All MCP fixes | Setup guides | Hit a different error? Request a test