Herald
Sync context and handoffs between Claude Chat in the browser and Claude Code in the terminal without manual copy-paste.
Overview
Herald is a MCP server for the Build phase that bridges Claude Chat and Claude Code so agents can exchange context without copy-pasting.
What is this MCP server?
- MCP bridge aimed at Claude Chat ↔ Claude Code continuity
- Remote streamable-http transport (self-hosted Herald instance URL)
- Version 1.0.0 server manifest on the MCP registry schema
- Eliminates manual copy-paste of prompts, logs, and decisions between surfaces
- Fits solo builders who split planning in web Chat and execution in terminal Code
- Server version 1.0.0 in registry manifest
- Transport type: streamable-http remote MCP
- Single primary remote URL pattern: /mcp on your Herald host
Community signal: 43 GitHub stars.
What problem does it solve?
Splitting work between Claude Chat and Claude Code forces you to manually copy prompts and outcomes, which breaks continuity and slows solo shipping.
Who is it for?
Solo builders who routinely start ideas in Claude Chat and finish implementation in Claude Code and want a dedicated bridge MCP.
Skip if: Teams that use only one Claude surface, or anyone unwilling to host and secure their own Herald HTTP endpoint.
What do I get? / Deliverables
After you register your Herald MCP remote, your coding agent can pull or push session context across Chat and Code through one protocol instead of the clipboard.
- Registered remote MCP connection to your Herald instance
- Reduced manual transfer of prompts and results between Chat and Code
- Repeatable agent handoff path across your Claude tooling
Recommended MCP Servers
Journey fit
Herald sits on the build shelf because its core job is wiring two Claude workflows together while you are actively coding and iterating with an agent. agent-tooling is the canonical facet for MCP bridges that extend how Claude Code receives prompts, artifacts, and session continuity from another Claude surface.
How it compares
MCP integration for Claude workflow continuity, not a brainstorming or planning agent skill.
Common Questions / FAQ
Who is Herald for?
Herald is for indie and solo developers who use both Claude Chat and Claude Code and want MCP-mediated handoffs instead of manual copy-paste.
When should I use Herald?
Use Herald whenever you split planning or debugging in Chat and implementation in Code and need the same context available to your terminal agent.
How do I add Herald to my agent?
Deploy or obtain a Herald instance, then add the remote streamable-http URL (for example https://your-herald-instance.example.com/mcp) in your MCP client configuration per Herald’s GitHub setup.