Relay MCP
Self-hosted shared message threads so Claude Code, Cowork and Claude.ai can hand off state
- Pricing
- Open source
- Platforms
- self-hosted, API, Web
- Version
- 0.1.0
- Listing updated
- today
Similar MCP servers
About Relay MCP
Relay MCP is an open-source MCP server for agent tooling. It is available on self-hosted, API, Web and CLI.
The README says the relay gives separate Claude surfaces a common message thread, so context that lives in one session can be picked up in another without copy-paste. A coding session can post an error and a theory for a named thread, and a scheduled Cowork task can leave a note that a later Chat conversation reads. Each message is tagged with the surface it came from and an optional session tag, which keeps threads readable when many sessions run in parallel.
The server is a Cloudflare Worker speaking streamable HTTP MCP, with Supabase Postgres holding threads, messages and read cursors. Access is either a static bearer key for Claude Code, Cursor and Cowork, or an OAuth 2.1 flow for Claude.ai custom connectors, both keyed to a single configured user ID in v1. The repository is MIT licensed and the README states it is not actively maintained, with larger changes likely to be declined.
It suits developers who already run several Claude surfaces on one project and who are comfortable deploying their own Worker and database. The README is explicit that the relay is a transient conversation layer, not a memory store or secrets vault.
Tools this server provides (6)
Taken from the project documentation; the running server may differ.
- relay_list_threads
- List threads with last activity and message count.
- relay_create_thread
- Create a named thread.
- relay_post_message
- Post a message to a thread, auto-creating it if missing.
- relay_read_thread
- Read recent messages, newest first, with optional cursor update.
- relay_check_new
- Return only messages since this reader last checked.
- relay_archive_thread
- Soft-archive a thread while preserving history.
What it does
- Shared message threads
- Named threads that any connected Claude surface can post to and read from.
- Surface and session tagging
- Each message records whether it came from chat, cowork, code or another surface, plus an optional free-text session tag.
- Unread-only checks
- A check tool returns only messages posted since a given reader last looked.
- Soft archiving
- Finished threads can be archived and hidden from listings while their history remains queryable.
- Two auth paths
- Static bearer keys for coding clients and an OAuth 2.1 flow with dynamic registration for Claude.ai connectors.
Good for
- Hand debugging context from a Claude Code session to a Claude.ai chat
- Leave overnight notes from a scheduled Cowork task for the next morning's conversation
- Keep a running standup thread that several Claude sessions contribute to
- Share a working scratchpad across parallel coding sessions on one project
Pricing
Open source
MIT-licensed, self-hosted; requires your own Cloudflare Workers and Supabase accounts.
Relay MCP FAQ
Does the relay store memories or decisions?
No. The README describes it as a transient conversation layer, not a log, decision record or memory store, and says durable decisions should be written to a separate system of record.
Is it hosted for me?
No. The README directs users to deploy their own Cloudflare Worker and Supabase project, which takes about ten minutes according to the README.
Can multiple users share one deployment?
Not in v1. The server is bound to one hardcoded user UUID, and the README says multi-user support needs additional work.
Which clients are supported?
The README covers Claude Code, Cursor, Cowork scheduled tasks, Claude Desktop via the mcp-remote bridge, and Claude.ai custom connectors.
Is Relay MCP free?
Yes. Relay MCP is open source, so you can use and self-host it for free.
What are the best alternatives to Relay MCP?
The closest alternatives to Relay MCP are Senrelay (ContextCore), Seamless and OpenCrawl.
Where this comes from
- Description: written from the project's README and its MCP Registry entry.