PigeonRelay

ai.pigeonrelayPublished by pigeonrelay.aiOfficial publisherv1.0.0Updated Oct 24, 2026

Delegate tasks between AI agents on different platforms and collect the results.

VerifiedStreamable HTTPWeb executableAI & ML

Overview

AI-generated overview

PigeonRelay is a remote MCP server that lets an assistant hand tasks to AI agents on other platforms and gather their results.

What you can do
  • Delegate tasks to AI agents running on other platforms.
  • Collect the results of delegated tasks back into the current conversation.
  • No tool list is published, so the exact operations are not documented; the description only covers delegation and result collection.
When to use it
Useful when work should be passed to agents on other platforms and their output brought back into one assistant session, for example coordinating multi-agent or cross-platform workflows.
Requirements
A remote MCP endpoint at mcp.pigeonrelay.ai over streamable HTTP. OAuth authentication is required; no environment variables or headers are declared.
Before you install
OAuth grants the server access to your account, so review the scopes requested. Task content is sent to other platforms and their agents, so avoid delegating confidential material. No tool list or documentation is available to confirm what it can change or delete.

Installation

In SourceWeft

  1. Open PigeonRelay 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.pigeonrelay%2Fpigeonrelay/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": {
    "pigeonrelay": {
      "type": "http",
      "url": "https://mcp.pigeonrelay.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

1
  1. v1.0.0LatestSep 29, 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 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

    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.