Unverified50% confidenceFactExact time
The per-server lock was introduced in MCP 1.x to address the problem that one failed request could cancel other requests on the same connection (PR 2682).
1
Sources
50%
Confidence
Long-term
Relevance
11/8/2026
First Seen
Sources
OpenAI Agents SDK Parallel MCP Calls Turning Serial? Testing and Fix
youtubeLali Publications11/7/2026
Related Entities
Related Claims
UnverifiedUsing this workaround on MCP 1.x versions is not recommended, because the lock exists to prevent all in-flight calls from failing together when the connection drops.78% similarUnverifiedIn actual MCP deployments, permission revocation typically has two granularities: the user revokes the token in the service provider's backend, causing subsequent calls to fail immediately, or disconnects a server connection on the client side to stop initiating requests.76% similarUnverifiedExplicit guardrails can be used to restrict MCP server operation permissions, for example by setting a database MCP server to read-only to prohibit destructive operations.72% similarUnverifiedThe root cause of the serialization is a per-server lock introduced in the MCP 1.x era, which is controlled in the SDK by the `_serialized_session_requests` flag and defaults to true.72% similarUnverifiedYou can use the /mcp command to disable unused MCP servers to save tokens.71% similar
Cite This Claim
Stable URI
https://kongchang.com/claim/1148210API
curl https://kongchang.com/api/v1/knowledge/claims/1148210MCP
get_claim(id=1148210)