Platform

One primitive.
A platform of tooling.

The Code is the atom — a unit of context you send and receive. Everything else is built on it, and all of it lives natively inside your agent.

Get access → How it works

One config block · any MCP client · no SDK.

The atom · one Code

send · receive · relay

The stack

Where Relay fits.

Three layers now share every agent pipeline. Each one moves something different. Only one carries the actual knowledge of what was done.

MCP

moves commands

A2A

moves tasks

Relay

moves what agents know

Why now

A2A reached v1.0 stable in April 2026 — 150+ organizations, GA across Copilot Studio, Azure AI Foundry, and Amazon Bedrock AgentCore. The protocol for agents to hand work to each other is now standard across every major cloud. Relay is the layer that carries context with that work.

Capabilities

Built on the Code.

Streams

A Code is a moment; a Stream is context that keeps flowing. Focus areas that stay current — they accumulate state, items, and contributions over time, so a project's context is always live, never a stale paste from last week.

relay_save · relay_search

Sessions

Package an entire working session — goals, decisions, state — and resume it later, on another machine, or hand it to the next agent. "Show up ready every time," made literal. Continuity, not re-briefing.

relay_session_*

Handoffs

The full working state of a session, wrapped to carry forward. Hand it to a teammate, the next agent, or future-you. Whoever receives it resumes mid-stride instead of starting cold.

relay_session_package

Series

A named, recurring relay — like weekly-sync. Drop context into the series; everyone subscribed receives the latest. One Code that keeps giving, instead of a fresh paste each time.

relay_series_*

Provenance

Every relay carries a timeline: who sent it, who received it, every hop, every timestamp. Org visibility controls, claim approvals, encryption, and retention — context you can audit and govern.

chain of custody

Connections

Sharing across people and orgs isn't a free-for-all. Cross-user claims go through request → approve → receive, so context lands with the right person, with consent — and durable connections skip the gate next time.

relay_request_*

The differentiator

The MCP toolset.

Relay isn't a website you visit — it's tooling your agent already has. Every capability above is exposed as an MCP tool directly inside Claude or any MCP client. No app-switching, no copy-paste. Context operations where the work happens.

relay_search relay_send relay_receive relay_request relay_save relay_session

Continuity

A Code moves context.
A platform keeps it alive.

The Code is the smallest unit — one thing you send, one thing someone receives. Streams, Sessions, Handoffs, and Series are what happen when a moment becomes a current: context that stays live, resumes whole, and carries forward to whoever comes next. We move it. We don't read it.

Integration

It lives where you work.

One block, any client

A single MCP config entry in Claude Desktop, Claude Code, or any MCP-compatible tool. No SDK, no build step.

The whole platform, in-agent

Streams, Sessions, Handoffs, Series, transfers, provenance — all callable as tools. Your agent operates on context without leaving the conversation.

Governed by default

Encryption, approvals, and org controls apply to every tool call — the same trust model whether a human or an agent is driving.

{
  "mcpServers": {
    "relay": {
      "command": "npx",
      "args": ["-y", "@relayctx/mcp-server"],
      "env": {
        "RELAY_API_KEY": "your-key-here"
      }
    }
  }
}

One primitive.A platform of tooling.

Where Relay fits.

Built on the Code.

A Code moves context.A platform keeps it alive.

It lives where you work.

Context in.Context out.

One primitive.
A platform of tooling.

A Code moves context.
A platform keeps it alive.

Context in.
Context out.