Skip to content

BUG REPORT: HTTP errors are being silently swallowed in the StreamableHTTP client #1010

Description

@Kulaxyz

Initial Checks

Description

When an MCP server returns HTTP 5xx errors (e.g., when the server is down) after initial connection, these errors are not being propagated to the caller. This makes it impossible for client applications to detect and handle server failures appropriately. More than that, clients which are waiting for response stream, like Strands SDK, are hanging forever since no response is returned

Example Code

Python & MCP Python SDK

Any

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    P2Moderate issues affecting some users, edge cases, potentially valuable featurebugSomething isn't workingready for workEnough information for someone to start working on

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions