Platform — RelayCTX

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 nowA2A hit 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.

Living context

Pulses

A Code is a moment; a Pulse is a heartbeat. Pulses are focus areas that stay current — they accumulate state, items, and contributions over time, so a project's context is always live, not a stale paste from last week.

relay_pulse_create · relay_pulse_update · get · list

Resume anything

Sessions

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

relay_session · package, log, browse, aftercare

Continuity

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. Use relay_forward to route it further down the chain.

relay_send · relay_receive · relay_forward

Standing streams

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 every time.

relay_series_* · claim, expire, update

Re-engagement

Cue

A relay that wakes itself up. Set a date, a condition, or an unblocker — when it fires, the context arrives with the re-engagement. Not a notification about something. The something itself, delivered when it matters.

relay_pulse_update · schedule · unblocker condition

Trust & control

Provenance

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

chain of custody · approvals · org policy · encryption

The graph

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_* · connect, approve, receive

The differentiator

The MCP toolset

Relay isn't a website you visit — it's tooling your agent already has. 7 MCP tools expose every capability above 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_forward · relay_pulse_create · relay_pulse_update · relay_session

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

Pulses, 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.

It lives where you work.

Context in.
Context out.

One primitive.A platform of tooling.

Where Relay fits.

Built on the Code.

It lives where you work.

Context in.Context out.

One primitive.
A platform of tooling.

Context in.
Context out.