Ask HN: Has anybody gotten a Node.js MCP server to work with HTTP?
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 did 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).
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).
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.
Everything I tried was a dud.
I avoid LLMs so I have not bothered with MCP, but what you need is trivial. Node provides multiple ways to connect to local services like IPC channels, network sockets, child process and more.
I recommend using the child process spawn method to create the MCP service behind your node based web server. You would write to stdin.write of your spawned process and you would read from the stdout and stderr data events.
MCP is a broken spec.