-
Notifications
You must be signed in to change notification settings - Fork 217
3/ Add support for HTTP Streamable MCP Transport #186
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
3/ Add support for HTTP Streamable MCP Transport #186
Conversation
🦋 Changeset detectedLatest commit: fa36b3f The changes in this PR will be included in the next version bump. This PR includes changesets to release 2 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
c01c998
to
414463e
Compare
d0595d2
to
93bf206
Compare
this is breaking types in the /mcp example. let's pair and figure it out. |
workerd/io/worker.c++:1020: info: console warning; message = An event handler returned a promise that will be ignored. Event handlers should not have a return value and should not be async functions
1e82664
to
2c14889
Compare
passed lints/typechecks, now running tests in CI too |
The tests pass, but seem to log this workerd error. Wonder what that's about
|
Note: Stacked on top of #200 *
This adds support for the new Streamable HTTP transport alongside the existing SSE transport. No code changes on the client should be necessary, and you can serve both at once with the same codebase.
This only supports
POST
requests for now. Resumability et al will come later, which should also not require any further changes to user code.Setting up a worker to serve these transports on different endpoints would look like this:
Initial testing with the unreleased MCP Inspector branch seems to work well!