8000 Support for Server-Sent Events (SSE) · Issue #1 · acryldata/mcp-server-datahub · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Support for Server-Sent Events (SSE) #1

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

Open
HannesHil opened this issue Apr 16, 2025 · 2 comments
Open

Support for Server-Sent Events (SSE) #1

HannesHil opened this issue Apr 16, 2025 · 2 comments

Comments

@HannesHil
Copy link
HannesHil commented Apr 16, 2025

First off, thanks for the amazing project—it's come at the perfect time for our LLM <> DataHub integration!

We're currently discussing our deployment strategy for the MCP server. The plan is for our central Data Mesh team to host a single MCP server instance, which downstream consumers would connect to using Server-Sent Events (SSE).

As far as we can tell, SSE is not currently supported.
Is SSE support on the roadmap, or are there any plans to add it in the near future?

@hsheth2
Copy link
Contributor
hsheth2 commented Apr 21, 2025

This is definitely on my mind - the main question is how to handle authentication and authorization in a reasonable way. If you've got thoughts on this, I'd love to hear them :)

If you're not really concerned about auth - we're using the FastMCP (v1) sdk, which supports exposing the MCP server via SSE via an ASGI server (familiar if you already use FastAPI / uvicorn): https://github.com/modelcontextprotocol/python-sdk#mounting-to-an-existing-asgi-server. It's not quite plug-and-play, but is pretty close to it

@liangjun-jiang
Copy link

I have sent a PR for this:
#8

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

No branches or pull requests

3 participants
0