Who Herald is for
Target audiences, the pains Herald removes, and how the ops loop works — without another Zapier catalog or custom MCP server.
Pick your seat
Herald is hosted MCP for ops: inbox for events, few scoped tools, structured alerts out.
Who. You use Cursor, Claude, VS Code, or another MCP client and want ops alerts without maintaining an MCP server.
Pain. You paste Discord webhooks into prompts, juggle one-off notifier MCPs, or drown the model in too many tools.
How Herald helps. Install a job pack, hook one event source, paste MCP config once. Your agent gets a few scoped tools + inbox — structured Discord/Slack/PagerDuty alerts when it decides action is needed.
- Minutes to first alert — not a weekend of glue code
- Few tools on the key (context stays usable)
- Works in any MCP-compatible IDE
What issues does Herald solve?
Without Herald
GitHub + Slack + Playwright + 40 other tools burn context before work starts.
With Herald
Job packs put a few tools on a scoped key — only what that ops job needs.
The loop
- 1Event sourceWebhook → inbox
- 2Your agentFew scoped MCP tools
- 3Structured alertDiscord · Slack · PagerDuty
Herald hosts the inbound URL, normalizes events in the inbox, and exposes a small set of MCP tools on a scoped key. Your agent decides; Herald delivers and audits.
Compared to…
- Zapier — fixed if-then automations. Herald keeps the agent deciding after each inbound event.
- Slack / Discord MCP — expose the chat app itself. Herald is the ops control plane: sources → inbox → few delivery tools.
- Blind Discord bots — forward events straight to chat. Herald normalizes for triage, then structured alerts with severity and links.