Relai MCP

Unified control plane for outreach accounts.

Relai gives teams a clean account layer, a local cache, and a stable MCP interface so agents can work against one consistent system instead of provider-specific APIs.

Search cached messages...
Force Sync
Live Sync Last updated 12s ago

Message State Layer

All outbound and inbound communications are normalized and stored in the local cache for immediate agent retrieval via MCP.

mcp_response.json
"status": "success",
"provider": "linkedin",
"data": [
{
"content": "Let's sync."
}
]
Connected

John Doe (Operator)

provider: linkedin
status: healthy sync

Last sync: 2m agoDisconnect
Connected

hello@company.com

provider: google_workspace
status: healthy sync

Last sync: 1m agoDisconnect
Core Engine

Accounts,sync, billing,MCP.

Connect Accounts

Connect operator-controlled outreach accounts seamlessly. One hosted flow to link multiple providers without custom integration code.

Cache State

Cache chats and messages into one workspace state layer. No more rate-limiting or duplicate API calls from your agentic workflows.

Issue MCP Tokens

Issue scoped MCP tokens per workspace. Agents authenticate through one standard protocol to read contexts and push actions.

Gate Usage

Gate usage with a simple subscription and account limits. Focus on your agent logic while Relai handles workspace quotas.

The Advantage

Buildlogic,notcachelayers.

Relai provides the missing infrastructure between raw provider APIs and stateful agent workflows.

Agent-first architecture natively.

Stop writing complex provider rate-limit backoffs in your agent logic. Relai handles the messy real-world communication layer globally.

agent_sync.ts
import { RelaiClient } from "@relai/mcp";

// Automatically handles rate limits and caching
const client = new RelaiClient(process.env.MCP_TOKEN);

Strict workspace isolation.

Each operator gets a local cache preventing cross-tenant leakage.

Zero-friction.

Hosted auth flows.

Standardized.

Plug-and-play MCP.

About

Built for teams running outreach through agents.

The product is intentionally narrow. It gives operators one place to connect accounts, sync communication data, and expose those workflows to coding agents through MCP without leaking low-level provider details into every client.

1Unified API
0Provider Leaks
// Agent connecting to Relai
const mcp = new RelaiMCP(token);

await mcp.connect();
const inbox = await mcp.getUnifiedInbox();

// Relai handles provider specifics
await mcp.send({
to: "target_uuid",
content: "Following up."
});
Testimonials

Trustedbyoperatorteams.

"We were constantly battling provider rate limits in our LangChain setup. Relai abstracts all of that away so our agents just read from a clean local cache."

Alex Rivera
Alex Rivera
CTO, LeadGenius

"The MCP token issuance is brilliant. We spin up a new workspace for every client, issue a token, and our agents immediately have isolated context."

Sarah Chen
Sarah Chen
VP Engineering, ScaleAI

"Finally, a control plane that understands agent workflows. It saved us weeks of writing boilerplate integration and sync logic."

Marcus Johnson
Marcus Johnson
Founder, Agentic Labs
Pricing

Startsimple.

One default plan for now, with a direct path to custom setups when limits or workflows need to change.

Starter

EUR20/ month
  • Up to 2 connected accounts per workspace.
  • Hosted account connection flow.
  • Message and chat cache.
  • MCP token issuance and workspace isolation.
Create account

Custom

Contact us

For more accounts, custom sync requirements, or higher-volume outbound workflows. We can tailor the setup to your specific agentic pipeline needs.

Contact us