What runtime does bun-mcp-sse-transport require?
It requires Bun.
Bun MCP Sse Transport
@tigranbs
Basic information
About Bun MCP Sse Transport
Bun Server Transport implementation for MCP - MCP SSE
Bun MCP Sse Transport config
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryBun MCP Sse Transport tools
Tool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Overview
What is bun-mcp-sse-transport?
A Server-Sent Events (SSE) transport implementation for the Model Context Protocol (MCP) built specifically for the Bun runtime. It enables real-time, one-way communication from server to client using SSE, with client-to-server communication handled via HTTP POST requests. Designed for developers building MCP servers on Bun.
How to use bun-mcp-sse-transport?
Install the package and import the BunSSEServerTransport class. Create an MCP server with @modelcontextprotocol/sdk, connect it to the transport, then set up a Bun HTTP server with routes: /sse returns the SSE response and /messages handles incoming POST requests.
Key features of bun-mcp-sse-transport
- Built specifically for the Bun runtime
- Implements the MCP transport interface
- Manages SSE connections with proper headers
- Handles incoming JSON-RPC messages
- Simple integration with Bun.serve
- Real-time, one-way server-to-client communication via SSE
Use cases of bun-mcp-sse-transport
—
Frequently asked questions
How does the client communicate back to the server?
The client sends JSON-RPC messages via HTTP POST requests to an endpoint URL provided in the initial SSE connection.
What endpoints must a server expose?
The example shows `/sse` for establishing the SSE connection and `/messages` for receiving client POST requests.
What protocol does it implement?
It implements the Model Context Protocol (MCP) transport interface and handles JSON-RPC messages.
Does it support the standard MCP flow?
Yes. The server creates an SSE connection, sends the endpoint URL, receives JSON-RPC messages via HTTP POST, and sends responses back over the SSE connection.
More Other MCP servers
EverArt
modelcontextprotocolModel Context Protocol Servers
88.1K
Sequential Thinking
modelcontextprotocolModel Context Protocol Servers
88.2K
ICSS
chokcoco不止于 CSS
20.7K
Handl
Handl speaks the Model Context Protocol. Your whole billing operation — projects, invoices, clients, reports, approvals — as tools any AI assistant can call, inside your autonomy rules.
Screenpipe
screenpipeYC (S26) | Open Computer History | Continuously record your company computer work, map your workflows, help you find work worth automating, and power your agents' context
22.0K
Comments