Code Relay

io.github.zarcherlotPublished by GitHub account zarcherlotv3.1.0Updated Oct 24, 2026

Branch-scoped runbooks, remote checkpoints, and auditable verification receipts.

VerifiedSTDIODesktop onlyCloud & Infrastructure Developer Tools

Server details

Identifier: io.github.zarcherlot/code-relay
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account zarcherlot for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.zarcherlot%2Fcode-relay.svg)](https://sourceweft.com/mcp/io.github.zarcherlot%2Fcode-relay?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Lets a coding agent publish branch-bound runbooks from one machine and run verification on another, returning structured receipts.

What you can do: Code Relay is a local stdio MCP server for cross-machine coding-agent workflows. Tools include bind_project, create_checkpoint_invite, join_checkpoint, watcher_status, stop_watcher, doctor, publish_runbook, status, fetch_receipt, and analyze. A Dev Host sends a repository- and branch-bound runbook; a Target Host checks the exact source commit in its real environment and returns a receipt recording passed, failed, or blocked verification for the next repair iteration.
When to use it: Use it when development and verification happen on different machines or environments, such as developing on Windows or macOS and verifying on Linux or a production-like host. It also fits special hardware like CUDA/GPU machines or connected cameras and sensors, and real integrations such as payment callbacks, queues, databases, or browsers that cannot be reproduced locally.
Requirements: Runs as a local process over stdio, started with npx from the npm package code-relay-mcp. Desktop only; no web executable. No authentication, environment variables, or headers are declared. A checkpoint execution path uses a code-relay-checkpoint GitHub Actions self-hosted runner.

Before you install

The server binds repositories and branches and can publish runbooks and execute allowlisted validation commands on a target host, so review what commands are permitted and where they run. It creates short-lived join links that grant access to a checkpoint subscription. Verification runs against real environments and integrations, so failed or blocked runs may affect live services.

Installation

In SourceWeft

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

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[Image] Code Relay

English · Chinese

Build. Prove. Relay.

Code Relay lets your coding agent develop on one machine and prove the result on another.

Relay is an MCP-based coding-agent integration for cross-machine development and verification. AI on the Dev Host implements the request; the Target Host runs the real validation; a structured receipt comes back to guide the next repair iteration. It works with Codex, Claude Code, Cursor, VS Code, and other MCP-capable coding agents.

When Relay is useful

Different environments — develop on Windows or macOS, verify on Linux, a private network, or a production-like host.
Special hardware — send model code to a CUDA/GPU machine, or verify a camera, serial device, or sensor where it is connected.
Real integrations — exercise payment callbacks, queues, databases, browsers, or internal services that cannot be reproduced locally.
AI-driven iteration — return concrete expected/actual results so the coding agent can repair, republish, and retry.

What Relay provides

Branch-scoped project binding and short-lived join links.
Exact source-commit verification in an isolated worktree.
Checkpoint execution through a code-relay-checkpoint GitHub Actions self-hosted runner.
Safe, allowlisted validation commands with bounded output and timeouts.
Structured receipt.json and human-readable receipts for passed, failed, and blocked runs.

Quick start

AI client installation

Let your coding agent read and follow the instructions:

npm fallback

Replace codex with claude-code, cursor, vscode, or generic as needed.

MCP server details

Code Relay is a local MCP server that communicates over stdio. The npm package starts the server with:

The server implements the MCP JSON-RPC surface directly in Go (without a third-party MCP SDK). It supports initialize, ping, tools/list, and tools/call, and exposes these tools:

Tool	Purpose
`bind_project`	Bind a repository and branch to a relay role.
`create_checkpoint_invite`	Create a short-lived checkpoint join link.
`join_checkpoint`	Join a branch-scoped checkpoint subscription.
`watcher_status`	Read local watcher state.
`stop_watcher`	Stop the local watcher.
`doctor`	Run non-mutating local health checks.
`publish_runbook`	Validate and publish a runbook.
`status`	Read runbook and receipt status.
`fetch_receipt`	Load and validate a runbook receipt.
`analyze`	Analyze a receipt and determine the next state.

The implementation and transport loop are in internal/relay/mcp.go.

How it works

[Dev Host sends a runbook through Code Relay to a Target Host; the Target Host runs a checkpoint and returns a receipt with evidence]

the Dev Host sends a repository- and branch-bound runbook through Relay; the Target Host checks the exact source commit in its real environment and returns a Receipt recording the Checkpoint result.

Every runbook is bound to a repository, branch, and source commit. The Target Host acts as the Checkpoint, and the resulting receipt records passed, failed, or blocked verification for the next iteration.

Documentation

License

Code Relay is released under the MIT License.

Source: README.md at commit 45bc618

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v3.1.0LatestSep 16, 2026

Score

50% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
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
License10 pts