Overview

The Spanly gateway is a hosted endpoint in front of your MCP server that captures traffic with no code changes.

The gateway is a hosted reverse proxy you put in front of your MCP server. Your end users connect to a Spanly endpoint, the gateway proxies every request to your server, and you get full observability with no SDK and no code changes.

When to use the gateway

	Gateway	SDK	CLI
Code changes	none	wrap your server	none
Distribution	you point users at a Spanly URL	ships in your app	runs beside your server
Transport	streamable HTTP	any the SDK supports	HTTP
Edge features	rate limit, IP rules, client keys, custom domains	no	no

Choose the gateway when you want observability without touching your server, or when you need edge controls (auth, rate limiting, IP rules) in front of a server that has none.

How it works

end user / MCP client
        │  HTTPS to <slug>.gateway.us.spanly.com
        ▼
Spanly regional gateway  ──►  your MCP server
        │
        └──►  capture (side path) ──► your Spanly dashboard

The gateway runs one service per region (US in Oregon, EU in Frankfurt) and is pinned to your environment's region. Capture is a side path: if any part of Spanly is degraded, your traffic keeps flowing and only the observability copy is affected.

Overview

When to use the gateway

How it works

On this page