MCP SSE and Streamable HTTP Deployment: Production Transport Guide

SSE vs Streamable HTTP: What Changed and Why

The original MCP remote transport used Server-Sent Events (SSE) for server-to-client streaming and a separate HTTP POST endpoint for client-to-server messages. This dual-channel approach worked for simple deployments but created significant problems at scale.

The move to streamable HTTP is described by the MCP team as adopting a "sealed letter" model: each request is a self-contained message that can be inspected, authenticated, and routed independently. This enables standard HTTP security practices (CORS, CSP, rate limiting) and integrates with existing infrastructure without special configuration.

Deploying MCP with Streamable HTTP on osModa

osModa's mcpd daemon abstracts the complexity of streamable HTTP deployment. You define your MCP server and its transport configuration in mcpd.toml, and the daemon handles endpoint creation, TLS termination, session management, authentication, and connection lifecycle.

[server.api-tools]
command = "python"
args = ["-m", "my_mcp_server"]
transport = "streamable-http"
port = 8443
health_check = "/health"
health_check_interval = "30s"

[server.api-tools.http]
chunked_encoding = true
max_request_size = "10MB"
request_timeout = "300s"
keepalive_timeout = "60s"
max_concurrent_requests = 100

[server.api-tools.session]
enabled = true
timeout = "3600s"
max_per_client = 5
storage = "memory"  # or "redis" for distributed

[server.api-tools.tls]
auto_cert = true  # Let's Encrypt
domain = "mcp.example.com"

# SSH into your osModa server
ssh root@your-server.os.moda

# Place your MCP server code
git clone your-mcp-server /opt/mcp/api-tools

# Install dependencies
cd /opt/mcp/api-tools && pip install -r requirements.txt

# mcpd picks up the config and starts the server
systemctl restart mcpd

# Verify the endpoint is live
curl https://mcp.example.com/health
# {"status": "ok", "server": "api-tools", "transport": "streamable-http"}

mcpd handles TLS certificate provisioning via Let's Encrypt, sets up the streamable HTTP endpoint with proper headers (HSTS, CSP, X-Frame-Options, CORS), and begins monitoring the server process with the watchdog daemon. No nginx, no Caddy, no manual reverse proxy configuration required.

Connection Management and Session Handling

Streamable HTTP in MCP supports two session modes: stateless and stateful. Choosing the right mode depends on whether your tools need context across multiple requests.

Scaling MCP Server Deployments

As enterprise MCP deployments scale to thousands of daily requests, the infrastructure must scale with them. The approach depends on your session model and request volume.

For most teams, vertical scaling on osModa is sufficient. A single osModa Enterprise server can handle thousands of concurrent MCP tool calls. Horizontal scaling is relevant for high-traffic production APIs or multi-tenant MCP deployments. See pricing plans for server specifications at each tier.

Monitoring and Observability

Production MCP deployments require monitoring at three layers: transport health, server process health, and tool execution metrics. osModa's mcpd daemon provides observability at all three layers out of the box.

Beyond real-time monitoring, every metric is also captured in the tamper-proof audit ledger for historical analysis and compliance reporting. For a deeper look at observability capabilities, see Watchdog Auto-Restart.

Migrating from SSE to Streamable HTTP

If you have existing MCP servers deployed with SSE transport, migration to streamable HTTP is straightforward. The MCP server code itself does not change -- transport is handled at the framework layer. Here is the migration path.

1. 1

   Update your MCP SDK

   Ensure you are using an MCP SDK version released after June 2025 that supports streamable HTTP. The official TypeScript and Python SDKs both support it. If you are using FastMCP, update to the latest version.

2. 2

   Change transport in mcpd.toml

   Switch transport = "sse" to transport = "streamable-http". Configure the HTTP-specific settings (chunked encoding, request timeout, max request size). osModa can run both SSE and streamable HTTP endpoints simultaneously during migration.

3. 3

   Update client configurations

   Point MCP clients (Claude Desktop, Cursor, custom agents) to the new streamable HTTP endpoint. Most clients auto-detect the transport type. During the transition, keep the SSE endpoint running for clients that have not updated.

4. 4

   Deprecate SSE endpoint

   Once all clients have migrated, remove the SSE transport configuration. Monitor the SSE endpoint for any remaining connections before shutdown. NixOS atomic rollback provides a safety net -- if any client breaks, roll back to the dual-transport configuration instantly.

osModa vs Cloud Platforms for MCP Deployment

You can deploy MCP servers with streamable HTTP on various platforms. Here is how osModa compares to popular cloud alternatives.

Cloud Run and Azure Functions work well for stateless MCP tool calls. osModa is the better choice when you need persistent processes, stateful sessions, tamper-proof audit trails, full infrastructure control, or predictable flat-rate pricing. For a broader infrastructure comparison, see osModa vs Traditional VPS.

Frequently Asked Questions

Related Guides