Reason Network — MCP illustration

Reason Network MCP Server

Connects teammates’ coding-agent sessions through a local daemon with peer messaging and MCP team-directory tools.

Published by reason-machinesreason-machines/reason-network

What you are opening

Lists team sessions and routes messages between supported agents, including Claude Code and Codex. This is a persistent team integration: names, repository and branch activity are visible to teammates.

How to set it up

  1. Build the pinned source with cargo build; do not pipe a remote installer into a shell.
  2. Run the resulting reason-network binary interactively to choose the standalone team setup.
  3. Connect only an intended team and review the hook and background-service changes before starting sessions.

Requirements and third-party terms

Dual licensed MIT OR Apache-2.0; both license files are present. Rust is required for source builds. The default installer can chain to reasonmachines.com for the optional Reason CLI; use the pinned source build below to avoid that mutable second stage. Peer connections use iroh; an encrypted relay may be used. Setup installs background services and client hooks, and auto-updates are documented.

Before you add it

  • Read the instructions and review any scripts before running them.
  • Check tool access, required credentials and third-party network requests.
  • The source license and any resource-specific terms take precedence.