MCP integration · Available in the Orchard CLI
Orchard, inside
Claude Code and Codex.
Keep using your assistant. Give it tools to remember project decisions, share context and coordinate through Orchard.
For Claude Code and Codex on your computer, with Orchard running and signed in.
Connect Claude or ChatGPT Local Claude Code / Codex setup
Remember together
Store a decision in one session. Recall it when another agent picks up the work.
Coordinate the work
Find Orchard sessions and send directed messages with context for the next agent.
Stay with the project
Read project context, inspect proposals and update tracked tasks from your assistant.
Connect in three steps
Bring Orchard into your next session.
Tool access and BEAM activity are separate. This MCP connection lets your assistant call Orchard tools. It does not automatically send your prompts, replies or every tool action to the BEAM log. Automatic activity capture requires Orchard’s host hooks to be installed, enabled and trusted.
Start Orchard and sign in
Keep Orchard running on your computer, with your project registered. Install the Orchard CLI and the assistant you want to use.
First time here? Set up OrchardConnect your assistant
Open a terminal in your registered project folder. Run the command for your assistant on that computer. These commands use a macOS or Linux shell.
Claude Code
claude mcp add orchard --scope local --transport stdio --env ORCHARD_PROJECT_ROOT="$PWD" -- "$(command -v orchard)" mcp serveCodex
codex mcp add orchard --env ORCHARD_PROJECT_ROOT="$PWD" -- "$(command -v orchard)" mcp serveClaude Code’s connection is local to this project. Codex saves a user-level entry bound to this folder; update it when connecting another project.
Check the connection
Start a new assistant session and approve the Orchard tools you want it to use. Ask:
Use Orchard’s
project_currenttool and tell me which project we’re in.Once the project is correct, ask the assistant to recall shared decisions, update a proposal or coordinate with another session. Some tools make changes; the host’s permissions and Orchard’s authorization still apply.
Connection troubleshooting and native plugins
If tools appear but calls fail, check that the Engine is running and signed in, the project folder is registered, and the host permits the tool call. A noninteractive “never approve” policy can refuse execution even when discovery succeeds.
These instructions use the shipped orchard mcp serve connection. The newer native plugin package, with automatic lifecycle hooks and standalone setup, still needs release verification and published packages.
Remote MCP · Early access
Connect Claude to your Orchard.
Add Orchard to Claude, then authorize access to your computers and projects. Your computers run the agents; Claude connects through Orchard’s relay.
Connect to ClaudeOpens Claude’s setup with Orchard filled in. Review and confirm the connection, then sign in to Orchard.
- Keep Orchard running and signed in on your computer. It must stay awake, online and reachable through Orchard’s relay.
- Sign in with the same Orchard account. Check which assistant is requesting access. The connection covers all computers and projects your account can access, including ones you add later.
- Tap Authorize to allow the assistant to read sessions, start agents and send instructions.
Existing connections keep their previous access. Start a new connection to authorize full account access. Claude supports remote connectors on mobile; Orchard’s phone connection and session actions are still being verified end to end.
Prefer Orchard’s own mobile interface? Open Orchard web to use Chat and Terminals through your phone browser.