MCP.so
Sign In
R

RelayLink MCP ServerVerifiedFeatured

Basic information

Transport

Streamable HTTP

Authentication

OAuth

Category

Communication

Submitted by

PillarStack

About RelayLink MCP Server

RelayLink lets your AI assistant send briefings to other people's AI assistants. Draft a package from your current conversation, attach files, approve the note, and the recipient's AI gets the full context: decisions, open questions and your caveats. Nobody has to re-explain a thread or forward a transcript. It also gives you a private notebook for notes, tasks and decisions that never leave your account. People without RelayLink still receive packages by email. It's a hosted remote server. Connect with OAuth, or use an API key for clients that need one.

Connection details

https://relaylink.ai/mcp

Setup

claude mcp add relaylink --transport http https://relaylink.ai/mcp

RelayLink MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

Conversations for the AI era. RelayLink lets your AI assistant correspond with other people through their AI assistants.

Instead of forwarding a transcript or re-explaining a thread, your assistant drafts a package from your current conversation: your note, the ask, a TL;DR, and the full context, including decisions, rejected options, open questions and your caveats. You approve the note before anything is sent. The recipient's AI reads it with full context and can answer the questions they actually have.

What you can do

  • Send briefings to people: draft, approve and send packages; read your inbox and whole threads; search past correspondence by decision, question or option.
  • Hand off work between assistants: save a handoff in one AI and resume it in another.
  • Keep a private notebook: notes, tasks, decisions and routines for yourself. Nothing in it reaches anyone else.
  • Attach documents: include Markdown or text files with a package.
  • Track follow-ups: track items, set reminders, tag threads, and see what's waiting on you.
  • Manage contacts and groups: invite people, create groups, block or rename contacts.

Built-in safeguards

  • Nothing is sent without your explicit approval of the note and wording.
  • Your private session is never shared. Only the briefing you approve is sent.
  • Inbound packages are treated as information, never as instructions to your assistant.

Connect

Endpoint: https://relaylink.ai/mcp (Streamable HTTP)

  • Claude Code: claude mcp add --transport http relaylink https://relaylink.ai/mcp, then run /mcp to sign in.
  • Claude (web/desktop): Customize → Connectors → Add custom connector → paste the URL.
  • ChatGPT: enable Developer mode, create an app, paste the URL, choose OAuth.
  • Grok: Connectors → New Connector → Custom.
  • Gemini CLI: add the URL as httpUrl in settings.json.
  • Other MCP clients: sign in with OAuth (emailed code, no password), or send the header X-RelayLink-Key: <your-key> using a key from your account page.

Full setup guides: https://relaylink.ai/docs

Frequently asked questions

1

What is the RelayLink remote MCP server?

The RelayLink remote MCP server is a hosted Model Context Protocol endpoint at https://relaylink.ai/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the RelayLink MCP server?

Add the endpoint https://relaylink.ai/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the RelayLink MCP server require authentication?

Yes. RelayLink uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the RelayLink MCP server use?

RelayLink exposes a Streamable HTTP endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments