Skip to content

Conversation

@Enucatl
Copy link

@Enucatl Enucatl commented Aug 10, 2025

These names are preferred by servers written in FastMCP >= 2.3.0 https://gofastmcp.com/deployment/running-server#streamable-http

They are fully supported aliases according to documentation.

Fix #267

These names are preferred by servers written in FastMCP >= 2.3.0
https://gofastmcp.com/deployment/running-server#streamable-http

They are fully supported aliases according to documentation.

Fix langchain-ai#267
@eyurtsev eyurtsev self-assigned this Sep 8, 2025
@eyurtsev
Copy link
Collaborator

eyurtsev commented Sep 9, 2025

I think we can revisit this in a few months. At the moment, all the aliases are likely more confusing than helpful. streamable http matches the MCP spec.

We can probably replace it with http in a few months (i suspect it'll become more generally adopted)

@eyurtsev eyurtsev closed this Sep 9, 2025
@eyurtsev eyurtsev reopened this Sep 9, 2025
@Enucatl
Copy link
Author

Enucatl commented Sep 9, 2025

In fact, this whole thing started because the MCP spec has streamable-http while this repo has streamable_http which was quite annoying to remember and also to have to specify differently

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.

Naming things: streamable-http vs. http

2 participants