MCP SSE Server

Example Use Cases

• 1

  Call external MCP tools (like search or retrieval tools) with low-latency persistent connections instead of spawning processes on every request.

• 2

  A unified, authenticated HTTP/SSE endpoint to expose multiple local or remote MCP tools to clients such as Claude Desktop or Cursor.

• 3

  Run and test MCP tools locally or on a simple deployment platform (e.g., Coolify) with per-tool runtime API key injection and connection pooling.

Description

This project implements a Server-Sent Events (SSE) server for MCP tools, replacing the traditional stdio transport so tools can be accessed over HTTP/SSE. It provides a tool registry, connection pooling, authentication via an API key, and per-tool header support for passing runtime API keys. The README includes deployment instructions (Coolify) and local development workflows using Deno and Node.js, plus testing examples for health checks and SSE connections. Benefits include reduced startup latency for tools, persistent connections for long-running sessions, and simplified client integration for agents like Claude Desktop and Cursor.