请问HN：有没有人成功让Node.js MCP服务器与HTTP一起工作？
今天花了一整天尝试设置这个，但没有成功。想知道其他人发现了什么。似乎在支持的传输方式上存在一些不确定的共识，虽然我确实让STDIO传输工作了，但理想情况下，我想使用HTTP(S)（我希望能够部署一个独立的MCP服务器，以便可以连接到聊天/应用等）。<p>根据我所了解，这个技术还很新，几乎没有客户端真正支持流式HTTP的功能。SSE的替代方案也不是很清楚（显然已经被弃用）。<p>我是在犯傻，还是说这真的是如此前沿，以至于充满了问题和困惑？答案五花八门，似乎只有STDIO是稳定和可用的。<p>我尝试的所有方法都没有成功。
查看原文
Spent the day trying to set this up but no luck. Curious what others have found. It seems like there's iffy agreement on supported transports and while I <i>did</i> get the STDIO transport to work, ideally, I can use HTTP(S) (I'd like to just be able to deploy a standalone MCP server that I can hook into chats/apps/etc).<p>From what I can tell, this is so new that few clients really support the streaming HTTP stuff. The SSE-alternative isn't terribly clear either (and apparently has been deprecated).<p>Am I being a dum dum or is this just so bleeding edge that it's riddled with issues and confusion? There's a mishmash of answers and only STDIO seems to be stable/working.<p>Everything I tried was a dud.