Relay

ai.relaytoPublished by relayto.aiOfficial publisherv0.1.1Updated Oct 29, 2026

Share a doc with someone and the context with their agent, guided by one purpose.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Relay is a remote MCP endpoint that lets an assistant share a document with someone and pass the surrounding context to their agent, guided by one purpose.

What you can do
  • Shares a document with another person and hands the related context to that person's agent.
  • Keeps the exchange guided by a single stated purpose.
  • No tool list is published, so the exact operations an assistant can call are not documented here.
When to use it
Consider it when you want an assistant to pass a document plus its context to someone else's agent rather than sending a plain file or link.
Requirements
A remote MCP endpoint at relayto.ai over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
OAuth access is required, and sharing sends documents and their context to another person and their agent, so check what is being disclosed before sharing. The available tools are not listed, so review the granted permissions after connecting.

Installation

In SourceWeft

  1. Open Relay in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/ai.relayto%2Frelay/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "relay": {
      "type": "http",
      "url": "https://relayto.ai/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

2
  1. v0.1.1LatestOct 29, 2026
  2. v0.1.0Oct 23, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.