About MCP SSE demo
MCP SSE demo is a reproducible example for developers investigating an SSE connection issue with the bun runtime. It demonstrates the same MCP server connection succeeding with nodejs for comparison.
Key features
- 01Reproduces an SSE connection issue
- 02Runs the server with bun and nodejs
- 03Tests connections with MCP Inspector
- 04Supports network and log inspection
Use cases
- 01Investigate SSE behavior under bun
- 02Compare bun and nodejs server runs
- 03Inspect MCP connection traffic and logs
MCP support
Provides a demo MCP SSE server for connection testing with MCP Inspector. The example compares behavior when run with bun and nodejs.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEMCP SSE demo
reproducible demo that shows an MCP SSE server fails using the bun runtime but succeeds using nodejs.
steps
- install dependencies
# or npm | yarn | pnpm install, same effect
bun install
- run the MCP inspector
npm run inspect
-
open the inspector http://localhost:5173
-
select SSE as the transport and enter
http://localhost:3500/sseas the url -
open dev tools network tab to inspect traffic
-
in another terminal tab / session run the server using bun
npm run start:bun
-
try to connect to the server using the inspector, observe the network (pending SSE connection), server and inspector logs
-
kill the bun server then run the server using nodejs
npm run start:node
- try to connect to the server using the inspector, observe the network (successful SSE connection and message posting), server and inspector logs
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.