Skip to main content
Glama

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.

Related MCP server: Infinite Code Next

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:

https://raw.githubusercontent.com/zarcherlot/code-relay/main/install.md

npm fallback

npx -y code-relay-mcp@latest install --client codex

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:

npx -y code-relay-mcp@3.1.0

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

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.

Available Tools

10 tools
analyzeC
Read-only

Analyze a runbook receipt and determine the next state.

Inputs: runbook_id (required), root.

bind_projectC
Destructive

Bind the current project and branch to Code Relay.

Inputs: role (required), ref, root.

create_checkpoint_inviteC

Create a short-lived checkpoint join link.

Inputs: root, expires, one_time.

doctorC
Read-only

Run non-mutating local health checks.

Inputs: root.

fetch_receiptC
Read-only

Load and validate a runbook receipt.

Inputs: runbook_id (required), root.

join_checkpointC
Destructive

Join a branch-scoped checkpoint subscription.

Inputs: url (required), root, destination.

publish_runbookB
Destructive

Validate and publish a runbook.md.

Inputs: markdown (required), root, force, no_git.

statusC
Read-only

Show runbook and receipt status.

Inputs: root.

stop_watcherC
Destructive

Stop the legacy local watcher state.

Inputs: root.

watcher_statusC
Read-only

Show the legacy local watcher state.

Inputs: root.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools target distinct actions and resources, such as bind_project, publish_runbook, and fetch_receipt. The main ambiguity is between status and watcher_status, though their descriptions clarify that one covers runbook/receipt status and the other legacy watcher state.

    Naming Consistency3/5

    Most tools follow a verb_noun pattern like create_checkpoint_invite and publish_runbook. However, doctor and status are bare nouns, and analyze is a bare verb, creating a mixed convention that is readable but not consistently patterned.

    Tool Count5/5

    With 10 tools, the server is well-scoped for its domain. Each tool appears to cover a meaningful part of the project binding, checkpoint, and runbook workflow without unnecessary bloat.

    Completeness3/5

    The runbook and receipt workflow is well covered with publish, status, fetch, and analyze. However, lifecycle gaps exist: there is no unbind_project, no checkpoint leave/revoke tool, and no way to start the legacy watcher, only to stop it.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers