DocsMCPSSE Transport

SSE Transport

The SSE (Server-Sent Events) transport connects to remote MCP servers over HTTP. Use this for servers running on other machines or in containers.

Configuration

[mcp.servers.remote]
transport = { type = "sse", url = "http://localhost:3001/sse" }
auto_connect = true
timeout_secs = 120

Fields

FieldRequiredDescription
urlYesThe SSE endpoint URL

How It Works

  1. Ryvos opens an HTTP connection to the SSE endpoint
  2. The server streams events (JSON-RPC) via Server-Sent Events
  3. Ryvos sends requests via HTTP POST to the server's message endpoint
  4. Tool lists and results are exchanged over the event stream

Use Cases

  • Remote servers — MCP servers running on other machines
  • Containerized servers — MCP servers in Docker/Kubernetes
  • Shared servers — Multiple agents connecting to the same MCP server
  • Cloud services — Hosted MCP servers

Example

# Remote MCP server
[mcp.servers.production_db]
transport = { type = "sse", url = "https://mcp.internal.company.com/sse" }
auto_connect = true
tier_override = "t3"      # Production DB = high risk
timeout_secs = 30

Security Considerations

SSE connections are unencrypted over HTTP. For production use:

  • Use HTTPS endpoints
  • Set appropriate tier_override for remote servers
  • Consider network-level access controls

CLI

ryvos mcp add remote --url http://localhost:3001/sse
Stdio TransportOverview