Which runtime causes the MCP SSE server to fail?
The bun runtime causes the SSE connection to remain pending and fail.
@the-vampiire
基本情報
demo of MCP SSE server limitations using the bun runtime
ツール一覧はまだありません
この掲載には表示できるツール一覧がまだありません。サーバーにツールがないという意味ではありません。対応機能はプロジェクトのドキュメントをご確認ください。
ツールは README から自動的に抽出されます。メンテナーは ## Tools という見出しの下に記載することで、このタブに反映できます。
A reproducible demo that shows an MCP SSE server fails when run with the bun runtime but succeeds when run with Node.js.
Install dependencies with bun install (or npm/yarn/pnpm). Run the MCP inspector with npm run inspect and open it at http://localhost:5173. Select SSE as the transport and enter http://localhost:3500/sse as the URL. In a separate terminal, start the server with npm run start:bun to observe the failure, then kill it and run npm run start:node to see the success.
The bun runtime causes the SSE connection to remain pending and fail.
Node.js works correctly, showing a successful SSE connection and message posting.
The demo uses the SSE (Server-Sent Events) transport.
The MCP inspector, opened at `http://localhost:5173`, is used to test the connection.
Open the browser’s developer tools network tab while using the MCP inspector.

Model Context Protocol Servers
🚀 The fast, Pythonic way to build MCP servers and clients.
A one-of-a-kind resume builder that keeps your privacy in mind. Completely secure, customizable, portable, open-source and free forever. Try it out today!
Hindsight: Agent Memory That Learns
A curated list of references for MLOps
コメント