The self-hosted MCP bridge between Claude Chat and Claude Code.
Herald
<strong>Code from your phone. Seriously.</strong>
<em>The self-hosted MCP bridge between Claude Chat and Claude Code.</em>
Documentation · Quick Start · How It Works · Features · Security · Roadmap
🇫🇷 Version française
You're on the couch. On your phone. You open Claude Chat and type:
"Refactor the auth middleware in my-api to use JWT instead of session cookies. Run the tests."
Four minutes later, it's done. Branch created, code refactored, tests passing, changes committed. Your workstation did all the work. You never opened your laptop.
That's Herald.
The Problem
Claude Chat and Claude Code are two brilliant tools that live in completely separate worlds.
| Claude Chat | Claude Code | |
|---|---|---|
| Where | Browser, phone, anywhere | Your terminal |
| What | Conversations, analysis, thinking | Reads, writes, and ships actual code |
| Gap | Can't touch your codebase | Can't leave your desk |
You've been copy-pasting between them. Or worse — you've been waiting until you're back at your desk. That's over.
The Solution
Herald is a self-hosted MCP server that bridges Claude Chat to Claude Code using Anthropic's official Custom Connectors protocol. One Go binary. Zero hacks.
You (phone/tablet/browser)
│
│ "Add rate limiting to the API"
▼
Claude Chat ──── MCP over HTTPS ────► Herald (your workstation)
│
▼
Claude Code
├── reads your codebase
├── writes the code
├── runs the tests
└── commits to a branch
You (terminal)
│
│ Claude Code calls herald_push
▼
Claude Code ──── MCP ────► Herald ────► Claude Chat picks it up
└── session context, summary,
files modified, git branch
The bridge is bidirectional. Claude Chat dispatches tasks to Claude Code, and Claude Code can push session context back to Herald for remote monitoring and continuation from another device.
Your code never leaves your machine. Herald just orchestrates.
How It Works
You (Claude Chat) Herald Claude Code
───────────────── ────── ───────────
"Refactor auth..." ──► start_task
→ creates branch
→ spawns Claude Code ──► reads codebase
refactors code
runs tests
commits changes
◄── task_id: herald-a1b2c3d4
"How's it going?" ──► check_task
◄── ✅ Completed (4m 12s)
4 files changed (+127/-23)
"Show me the diff" ──► get_diff
◄── auth/middleware.go
+func ValidateJWT(...)
-func CheckSession(...)
Three tools. That's the core loop. Start, check, get results — all from wherever you are.
Reverse flow: Claude Code → Herald
Working in your terminal and want to continue from your phone? Claude Code pushes its session to Herald:
You (terminal) Claude Code Herald
────────────── ─────────── ──────
"Push this to Herald" ──► herald_push
→ session_id, summary,
files, branch ──► linked task created
🔗 visible in list_tasks
You (phone, later) Claude Chat Herald
────────────────── ─────────── ──────
"What sessions are list_tasks
waiting for me?" ──► (statu
Tools (5)
start_taskInitializes a new task, creates a branch, and spawns Claude Code to execute the request.check_taskChecks the status and progress of an ongoing or completed task.get_diffRetrieves the code changes associated with a specific task.herald_pushPushes a local Claude Code session to Herald for remote monitoring and continuation.list_tasksLists all active or waiting tasks for the user.Configuration
{"mcpServers": {"herald": {"command": "herald", "args": []}}}