Overview
What is SSE MCP Server?
SSE MCP Server is a sample implementation of a Model Context Protocol (MCP) server using Server-Sent Events (SSE). It is designed to be deployed on Netlify Edge Functions and provides a simple client interface for real-time communication.
How to use SSE MCP Server?
Clone the repository, install dependencies with npm install, then start the development server with npm run dev. For deployment, install the Netlify CLI, log in, initialize the site, and run npm run deploy. After deployment, access the site URL; the top page shows “SSE MCP Server is running. Access /sse to connect.” A demo page lets you test SSE connections and message sending/receiving.
Key features of SSE MCP Server
- Real-time communication via Server-Sent Events.
- Server-side implementation for Netlify Edge Functions.
- Simple client interface with a demo page.
- Periodic ping messages to maintain SSE connections.
- Fix for 502 errors on Netlify Edge Functions.
Use cases of SSE MCP Server
- Testing SSE connections from a web client.
- Sending and receiving messages through an MCP server.
- Verifying periodic ping messages and connection stability.
- Deploying an MCP server on Netlify’s edge infrastructure.
FAQ from SSE MCP Server
How can I verify that the deployment is working?
After deployment, open the site URL. The top page displays a confirmation message. Use the demo page to click “Connect” – a successful connection shows “接続中” (connecting) and a connection ID. Send a test message to confirm send/receive works. Check the browser’s developer tools for /sse and /message endpoints.
What dependencies or runtime are required?
The server requires Node.js and npm locally for development. For deployment, the Netlify CLI and a Netlify account are needed. The runtime is Netlify Edge Functions.
Where does the data live?
Data is processed in real-time via SSE streams; the README does not specify persistent storage. The server is stateless in the provided sample.
What transport and authentication are used?
Transport is HTTP-based Server-Sent Events (SSE). No authentication mechanism is described in the README.
Is there a known limit or caveat?
The README mentions a previous 502 error on Netlify Edge Functions, which was fixed by adding periodic ping messages. No other limits are stated.
