Get the FREE Ultimate OpenClaw Setup Guide →

express -sse

MCP server from yunusemredilber/express-mcp-sse-server

Installation
Run this command in your terminal to add the MCP server to Claude Code.
Run in terminal:
Command
claude mcp add --transport stdio yunusemredilber-express-mcp-sse-server node src/index.ts \
  --env PORT="Port for the HTTP server (default 3001)" \
  --env NODE_ENV="development or production"

How to use

This MCP SSE server implements the Model Context Protocol over Server-Sent Events (SSE) using Express. It provides a real-time communication channel to manage and stream model context updates to connected clients. The server exposes an SSE endpoint at /sse for establishing persistent connections and a /messages endpoint for sending messages to the MCP server, enabling clients to exchange model context events efficiently in real time. With the MCP SDK, applications can subscribe to resource changes, receive updates, and interact with templated resources in a standardized way.

How to install

Prerequisites:

  • Node.js v14 or higher (recommended)
  • Yarn package manager (or npm as an alternative)

Install steps:

  1. Clone the repository: git clone git@github.com:yunusemredilber/express-mcp-sse-server.git
  2. Navigate into the project: cd express-mcp-sse-server
  3. Install dependencies: yarn install

    or using npm:

    npm install

  4. Configure environment (optional):
    • PORT: Port to run the server (default 3001)
    • NODE_ENV: development or production
  5. Run the server in development mode (with MCP inspector if available): yarn dev

    or to run in production:

    yarn start
  6. Access the endpoints:

Additional notes

Tips:

  • The SSE endpoint /sse maintains a persistent connection for real-time updates. Clients should connect with an EventSource in the browser or a compatible SSE client.
  • The /messages endpoint can be used to push messages to the MCP server or to trigger model context events depending on the server implementation.
  • If you change the PORT environment variable, ensure any reverse proxy or load balancer is updated accordingly.
  • For production deployments, consider running behind a process manager (e.g., PM2) and enabling proper TLS termination.
  • If you encounter issues, check that your Node version matches the compatibility noted in the README and that dependencies are correctly installed.

Related MCP Servers

Sponsor this space

Reach thousands of developers