PulseAugur
EN
LIVE 05:10:02

MCP Go implementation bug caused 45-second tool call deadlocks

A bug in the Model Context Protocol (MCP) implementation in mcp-go caused a 45-second deadlock for tool calls that required user input. The issue arose because the server incorrectly sent elicitation requests (which require user input) over a separate GET stream instead of the primary POST stream. This routing mismatch led to a circular wait: the client was blocked waiting for the POST response, while the server was blocked waiting for the client to process the elicitation on the GET stream. The bug has been fixed in a pull request, but the underlying issue highlights potential complexities with MCP's Streamable HTTP transport, especially with the upcoming spec release. AI

IMPACT This bug fix in the Model Context Protocol implementation could improve the reliability of AI agent tool calls that require user interaction.

RANK_REASON Bug report and fix for a specific software implementation.

Read on dev.to — MCP tag →

AI-generated summary · Google Gemini · from 1 sources. How we write summaries →

MCP Go implementation bug caused 45-second tool call deadlocks

COVERAGE [1]

  1. dev.to — MCP tag TIER_1 English(EN) · Yusuf İhsan Görgel ·

    One Request, Two Streams: Debugging a 45-Second Deadlock in MCP's Streamable HTTP

    <p>A tool call freezes for exactly 45 seconds, then fails. The user gets a permission popup 45 seconds too late, answers it, and the answer goes nowhere. Nothing crashed and no error was logged on the way in. That is the bug report that landed in <a href="https://github.com/mark3…