Remote
Point Relay at a hosted MCP endpoint.
Streamable HTTP or SSE, with OAuth or bearer tokens.
Configure a single endpoint, connect upstreams through OAuth, and reach every tool behind it. Relay scopes the tool list per client and keeps credentials synced in the cloud, so nothing secret ever lands in your config.
relay --version 0.4.1
relay connect linear
upstreammcp.linear.appstreamable http · 31 tools
oauthgrantedtoken stored in relay cloud
toolslinear.*31 namespaced tools
relay client add cursor
clientcli_4c91active · scoped endpoint
endpointrelay.sh/mcp/ws_8f2a/cursor
scopesgithub.* · linear.read51 tools
relay status
ready3 upstreams · 102 tools3 clients · 0 tokens in config
Prompt awaiting input
01 / upstreams
Whatever shape the server takes, it becomes a prefixed set of tools behind the same endpoint. Nothing to rewrite on the client side.
Point Relay at a hosted MCP endpoint.
Streamable HTTP or SSE, with OAuth or bearer tokens.
Run a provider you own on our edge.
Bring a container or a function; we handle cold starts.
First-party connectors, pre-authorized.
Linear, GitHub, Vercel, Slack and a growing catalogue.
02 / how it works
Relay owns the handshake and the credential lifecycle. Your client only ever learns one URL and one scoped token.
Paste an MCP URL and claim a namespace. Every tool it exposes is prefixed with that slug, so two servers can never collide.
Relay runs the OAuth handshake and stores the credential in the cloud. Tokens refresh server-side, never in your client config.
One endpoint serves every client. Scope tools per client, revoke per client, and watch requests in the activity log.
03 / endpoint
The endpoint is stable for your account, and each client gets its own path. Scopes travel with the client, so a revoked token only affects that one.
https://relay.sh/mcpstreamable httpoauth 2.1tools/list/.well-known/oauth-protected-resource{
"mcpServers": {
"relay": {
"type": "streamable-http",
"url": "https://relay.sh/mcp/ws_8f2a/cursor",
"headers": {
"Authorization": "Bearer $RELAY_TOKEN"
}
}
}
}
Account path, no upstream URLs and no upstream tokens.
# 1. discover the resource metadata
GET https://relay.sh/mcp/.well-known/oauth-protected-resource
# 2. relay names itself as the authorization server
authorization_servers: ["https://relay.sh/mcp"]
# 3. your client opens the consent screen
GET /oauth/authorize?client_id=cli_4c91&scope=github.*
# 4. exchange the code for a scoped token
POST /oauth/token -> access_token (tools capped by scope)
Relay brokers every upstream token; the client only holds its own.
04 / pricing
Every plan includes the full gateway: upstream aggregation, OAuth brokering and per-client scoping. Limits are on upstreams and clients, never on tool invocations.
For one operator wiring up a personal toolchain.
Shared upstreams, scoped endpoints and an audit trail.
Private regions, SSO and a support agreement.
ready when you are
One account, every upstream, one URL.