cyberneticlibrary

Transport MCP servers over HTTP

transport-httpmcp_serversetup L30
paoloricciuti/tmcp
What it does

Transport MCP servers over HTTP with Server-Sent Events (SSE)

Best for

Web-based MCP clients (serverless, browser, load-balanced) that cannot use stdio.

Inputs
  • · HTTP requests with MCP message format
  • · custom session IDs
  • · POST body with tool call params
Outputs
  • · SSE stream of MCP responses
  • · session metadata (capabilities, info, log levels)
Requires
  • · HTTP server (Node.js, Fastify, Bun, Deno, etc)
  • · Optional: Redis for multi-server sessions
Preconditions
  • · Node.js v18+
  • · @modelcontextprotocol/sdk installed
  • · HTTP server framework integration
Failure modes
  • · Serverless environments kill SSE after timeout
  • · Session data lost if not using Redis in multi-server setup
  • · Malformed MCP requests cause transport errors
Trust signals
  • · Framework-agnostic design (Fastify, Bun, Deno support)
  • · Redis session manager for multi-server deployments
  • · Session metadata persistence