bun-mcp-sse-transport

@tigranbs

Repository

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.

Repository

Tools

No tools detected

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

—

FAQ from bun-mcp-sse-transport

What runtime does bun-mcp-sse-transport require?

It requires Bun.

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.

Frequently asked questions

What runtime does bun-mcp-sse-transport require?

It requires Bun.

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.

Comments

Basic information

More Other MCP servers

Peekaboo MCP – lightning-fast macOS screenshots for AI agents

steipete

Peekaboo is a macOS CLI & optional MCP server that enables AI agents to capture screenshots of applications, or the entire system, with optional visual question answering through local or remote AI models.

4.8K