Skip to content

Make streamable HTTP POSTs concurrent for client->server - #602

Closed
Agent-Hellboy wants to merge 7 commits into
evalstate:mainfrom
Agent-Hellboy:fix_blocking_response
Closed

Make streamable HTTP POSTs concurrent for client->server #602
Agent-Hellboy wants to merge 7 commits into
evalstate:mainfrom
Agent-Hellboy:fix_blocking_response

Conversation

@Agent-Hellboy

@Agent-Hellboy Agent-Hellboy commented Jan 6, 2026

Copy link
Copy Markdown
Contributor

No description provided.

@Agent-Hellboy Agent-Hellboy changed the title Make streamable HTTP POSTs concurrent so elicitation responses aren't… Make streamable HTTP POSTs concurrent for client->server Jan 6, 2026
@Agent-Hellboy
Agent-Hellboy marked this pull request as ready for review January 7, 2026 14:20
@Agent-Hellboy

Agent-Hellboy commented Feb 5, 2026

Copy link
Copy Markdown
Contributor Author

hi @evalstate , please check https://github.com/orgs/modelcontextprotocol/discussions/665, i think we should merge this.

@evalstate

Copy link
Copy Markdown
Owner

Hi @Agent-Hellboy -- I've tested the blocking_elicitation_server against the current 0.4.50 and both tools seem to work without needing this change. Would appreciate if you could re-test.

Reviewing this change as-is think there may be some issues with timeout/auth, but think it might not be necessary (maybe a fix in a more recent MCP library version?).

@evalstate

Copy link
Copy Markdown
Owner

Closing for the moment as cannot reproduce the defect in recent versions.

@evalstate evalstate closed this Feb 26, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants