Mcp Relay

io.github.runrelayPublished by GitHub account runrelayv0.1.0Updated Oct 24, 2026

RunRelay MCP relay — AI agent threads, HITL confirmations, and travel capability discovery.

VerifiedSSEWeb executableLocation & LifestyleProductivity & WorkflowAI & ML

Overview

AI-generated overview

RunRelay's remote MCP relay exposes AI agent threads, human-in-the-loop confirmations, and travel capability discovery to an assistant.

What you can do
RunRelay is a remote MCP relay reached over SSE at a hosted endpoint. According to its registry description, it covers AI agent threads, human-in-the-loop (HITL) confirmations, and travel capability discovery. No individual tools are listed in the manifest, so the exact operations available are not documented here.
When to use it
Consider it when you want an assistant to work with RunRelay agent threads, route actions through human confirmations, or look up travel capabilities. Because the tool list is not published, verify the available operations before relying on it.
Requirements
A remote SSE endpoint at mcp.runrelay.io; no local package or runtime is declared. An Authorization header carrying a RunRelay API key (starts with rr_) is required, and the manifest points to the provider's site for obtaining one. Network access to the endpoint is needed.
Before you install
The server asks for a RunRelay API key in the Authorization header; treat it as a secret and do not share it. The description mentions human-in-the-loop confirmations, which suggests some actions may need approval, but the manifest lists no tools, so what the server can read, write, send, or delete is not documented. Review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open Mcp Relay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via SSE. 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/io.github.runrelay%2Fmcp-relay/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.

{
  "mcpServers": {
    "relay": {
      "type": "sse",
      "url": "https://mcp.runrelay.io/sse"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

60% 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 listedRequired15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.