Herald MCP Server

Connect Herald to Claude, Cursor or any other MCP client and it stops being a tab you switch to. Stop copy-pasting between Claude Chat and Claude Code. The herald mcp server is what makes that connection.

What the server does

The self-hosted MCP bridge between Claude Chat and Claude Code.

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• start_task — Launch a Claude Code task. Returns an ID immediately. Supports priority, timeout, session resumption, and Git branch options
• check_task — Check status and progress. Optionally include recent output
• get_result — Get the full result of a completed task (summary, full, or json)
• list_tasks — List tasks with filters — status, project, time range
• cancel_task — Cancel a running or queued task. Optionally revert Git changes
• get_diff — Git diff for a task's branch or uncommitted changes
• list_projects — List configured projects with Git status
• read_file — Read a file from a project (path-safe — cannot escape project root)
• herald_push — Push a Claude Code session to Herald for remote monitoring and continuation from another device
• get_logs — View logs and activity history
• Core — The Core tool exposed by this server
• Operations — The Operations tool exposed by this server

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Credentials and setup notes

Configuration is passed through the environment: HERALD_CLIENT_SECRET. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Where it fits

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Herald's toolset — start_task, check_task, get_result and 10 more — is a fair guide to whether it matches your workflow. It is maintained by btouchard; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Herald's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 13 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Herald.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.