Herald — Notify • Route • Execute

Built for people who run agents in production

If your coding agent should read ops events and alert the right channel — without a custom MCP server or a hundred tools in context.

Builders on Cursor, Claude, and MCP IDEs

Pain

The agent finishes a long job or waits for input — and nobody gets a ping.

With Herald

Scoped Discord / Slack / PagerDuty tools so the agent can notify when it matters.

Agent job done → Herald tool → channel ping

Events in. Agent decides. Alerts out.

Herald is not another Zapier catalog. Your agent gets an inbox for webhooks, a few scoped tools from a job pack, and audited delivery to Discord, Slack, or PagerDuty.

Inbox

Real webhooks land as normalized events — Stripe, GitHub Actions, Sentry, Web3, or a custom Herald URL. Agents list and read them before acting.

Scoped tools

Job packs install a few MCP tools and a scoped key. Your IDE only sees what that pack needs — not every template in the gallery.

Delivery & audit

Structured alerts with severity, title, and dashboard links. Every invocation logged — test from the dashboard, then trust production agents.

Any MCP client

Paste config once — Cursor, Claude, VS Code, Windsurf, Zed, JetBrains, and more. Same scoped tools and inbox in local chat or background agents.

Where Herald works best

Agent-driven ops — not Zapier replays. Each use case maps to a job pack: few tools, real webhooks, structured alerts.

CI & deploy guardrails

Failed builds and deploys page the right channel — with severity, run URL, and context.

TriggerGitHub — CI completed (failed) or Pull request opened

FlowInbox event → agent decides → Discord CI alert / PagerDuty

Error triage

Sentry spikes become Slack alerts — and Statuspage incidents when customers feel it.

TriggerSentry — Issue created (via Herald webhook) or cron every 15 minutes

FlowSentry webhook → inbox → Slack alert → optional Statuspage

Payment & billing ops

Failed charges get triaged by an agent, not a blind Zapier forward.

TriggerStripe webhook (via Herald inbox) or scheduled billing check

FlowStripe webhook → inbox → structured billing alert

Security review alerts

Critical findings on a PR or in chat ship as structured Discord embeds with file path and severity.

TriggerGitHub — Pull request opened, or local Agent chat

FlowPR opened / agent finds bug → security alert

Web3 incident response

On-chain monitors land in the inbox; the agent triages, then alerts with explorer links.

TriggerHerald inbox webhook (Alchemy / Tenderly / Forta) or cron monitor

FlowAlchemy / Tenderly / Forta → inbox → Web3 alert

Agent completion & on-call ping

Ping Discord or page when the agent finishes a long job — or when impact is real.

TriggerPagerDuty incident, cron health check, or manual webhook

FlowAgent needs input / severity high → Discord + PagerDuty

Prefer browsing packs first? See job packs · Connect IDE · Cursor Automations

Set up in three steps

Pick a job pack, point a webhook at Herald, connect your IDE. Your agent can read events and send alerts in minutes.

1Job packFew scoped tools
2Event sourceWebhook → inbox
3Your IDEAgent → alert

1

Pick a job pack

Ship Guard, Stripe Ops, Status Room, On-call, or Web3 Watch — a few tools and a scoped key for one job, not the whole gallery.

2

Hook an event source

Point Stripe, GitHub Actions, Sentry, or a custom Herald URL at Inbox. Events show up ready for the agent to read.

3

Connect your IDE

Paste config into your IDE or agent — Cursor, Claude, VS Code, Windsurf, Zed, JetBrains, and more. Copy agent instructions so the model knows when to alert Discord, Slack, or PagerDuty.

Step 1 — Job pack

Stripe Ops pack → scoped tools on one key

list_recent_eventsget_eventdiscord_send_stripe_alertslack_send_stripe_alert

One pack = few tools. Your agent never sees the whole gallery.

Connect IDE wizard

Per-client setup for every major MCP IDE and agent — plus scoped keys and copy-paste agent instructions for the tools you enabled.

Connect IDE docs →

Wire it into your IDE or agent

After the job pack is installed, paste MCP config once into any MCP client. Use a Bearer key or OAuth — details live in the Connect IDE wizard.

MCP config — Streamable HTTP

{
  "mcpServers": {
    "herald": {
      "url": "https://gateway.herald.services/v1/your-workspace/mcp",
      "headers": {
        "Authorization": "Bearer mcp_live_..."
      }
    }
  }
}

Cursor

Codex

Claude

Windsurf

VS Code

Zed

JetBrains

Cline

For developers

Stop pasting Discord webhooks into every agent prompt

Herald gives your IDE agent a small, safe toolset: read ops events, decide, send a real alert — no MCP server to maintain.

Without Herald

A noisy webhook dump in Discord — or nothing until someone checks Actions.

With Herald

Your agent reads the failed run from the inbox, decides severity, and pages Discord or PagerDuty with the job URL.

Problem: Main is red and nobody knows until standup.

GitHub Actions / Vercel deploy webhook lands in Herald Inbox.

inboxworkflow_run.completed

ship.yml · main · conclusion: failure

Starts from Ship Guard job pack

Start free Connect your IDE See job packs

Built for production agent workflows

Enterprise-grade security without the enterprise complexity.

Encrypted secrets

Webhook tokens and API credentials stored with AES-256-GCM.

SSRF protection

Outbound requests blocked from private networks and metadata endpoints.

OAuth 2.1 + Bearer keys

MCP-spec auth with PKCE for one-click clients, or scoped Bearer keys stored as secure hashes.

Per-key tool ACL

Restrict each MCP key to selected tools — ideal for bundles and least privilege.

IP allowlists

Optional workspace CIDR allowlists on the gateway for production lockdown.

Full audit trail

Every tool invocation logged with status, duration, auth type, and redacted args.

Rate limiting

Per-workspace limits protect your channels from runaway agents.

Multi-tenant isolation

Each workspace gets its own tools, keys, hooks, and MCP endpoint.

Signed inbound hooks

Webhook signatures verified by default — unsigned hooks blocked in production.

Sources in, destinations out

Event sources feed the inbox; job packs expose a few delivery tools on a scoped key. Herald sits in the middle — agent in the loop, not a blind forwarder.

Herald

Ops loop: webhook → agent → alert

Cursor

OpenAI Codex

Claude

Windsurf

Visual Studio Code

Zed Industries

JetBrains

Cline

GitHub Copilot

Google Gemini

Replit

Continue

Model Context Protocol

Discord

Slack

Microsoft Teams

Google Chat

Mattermost

Rocket.Chat

ntfy

Gotify

Pushover

Alchemy

Tenderly

OpenZeppelin Defender

Forta

GitHub

PagerDuty

Product & automation templates

LinearWordPressResendNotionAirtableZendeskIntercomStripeSentryZapierMakeTwilioCal.comOpsgenieStatuspage

AI clients & IDEs

Cursor

OpenAI Codex

Claude

Windsurf

Visual Studio Code

Zed Industries

JetBrains

Cline

GitHub Copilot

Google Gemini

Replit

Continue

Model Context Protocol

Cursor

OpenAI Codex

Claude

Windsurf

Visual Studio Code

Zed Industries

JetBrains

Cline

GitHub Copilot

Google Gemini

Replit

Continue

Model Context Protocol

Team chat

Discord

Slack

Microsoft Teams

Google Chat

Mattermost

Rocket.Chat

Discord

Slack

Microsoft Teams

Google Chat

Mattermost

Rocket.Chat

Mobile push

ntfy

Gotify

Pushover

ntfy

Gotify

Pushover

Web3 inbound

Alchemy

Tenderly

OpenZeppelin Defender

Forta

Alchemy

Tenderly

OpenZeppelin Defender

Forta

Actions & APIs

GitHub

PagerDuty

Model Context Protocol

GitHub

PagerDuty

Model Context Protocol

Job packs for common ops jobs

Each pack is a small kit — a few tools and a scoped key — so your agent only sees what that job needs.

On-call

Page on-call via PagerDuty and notify the team on Discord — scoped MCP key without inbox tools.

2 tools on the key

Web3 watch

Discord + Slack Web3 alerts plus inbox access so agents can read Alchemy/QuickNode/Moralis/Safe events.

2 tools on the key

Solana watch

Discord Solana alerts plus inbox access for Helius (and other) Solana events.

1 tools on the key

Stripe ops

Discord + Slack Stripe payment alerts plus inbox access for Stripe webhook events.

2 tools on the key

Ship guard

Discord CI alerts and PagerDuty page plus inbox for GitHub Actions / Vercel deploy failures.

2 tools on the key

Status room

Slack Sentry alerts and Statuspage incidents plus inbox for Sentry / Better Stack events.

2 tools on the key

More packs and browse-all tools in the dashboard — sign up free

Simple pricing for every stage

Free to try in your IDE. Pro when agents go to production.

Inbound hooks are hosted URLs Herald receives events on — Stripe, GitHub Actions, Sentry, Web3 sources, and custom Herald URLs. Agents read them via inbox tools, then send structured alerts on scoped tools.

Free

$0

Try Herald in your IDE

1,000 invocations / month
2 inbound hooks
All templates & bundles
Team workspaces
Multi-IDE MCP config

Get started

Pro

$29

per month · 14-day trial when billing is enabled

50,000 invocations / month
20 inbound hooks
Custom domain + DNS verify
OpenAPI import
Email support

Start 14-day Pro trial

Trial when billing is enabled · upgrade anytime in Settings

Platform

Custom

For teams at scale

500,000 invocations / month
100 inbound hooks
Everything in Pro
Platform REST API
Priority support

Upgrade in app Or email support@herald.services

Free to try every template in your IDE. Pro adds production volume, custom domain, and OpenAPI. Platform is for high-volume teams — support@herald.services.

Frequently asked questions

Quick answers — or start the guided tour for a full walkthrough.

What is Herald?

Herald wires your coding agent for ops alerts. Webhooks land in an inbox, the agent reads them, then sends structured Discord, Slack, or PagerDuty alerts — without you writing an MCP server. Start with a job pack (a small kit of tools + a scoped key).

How is this different from Zapier?

How is this different from Slack MCP?

How is this different from Helius Discord bots?

What is a job pack?

Which IDEs and agents work with Herald?

Does Herald work with background agents like Cursor Automations?

Where should I use Herald?

Your coding agent, wired for ops alerts

Inbox events (24h)

Tools on this key

Delivery trend

Built for people who run agents in production

Events in. Agent decides. Alerts out.

Inbox

Scoped tools

Delivery & audit

Any MCP client

Where Herald works best

CI & deploy guardrails

Error triage

Payment & billing ops

Security review alerts

Web3 incident response

Agent completion & on-call ping

Set up in three steps

Pick a job pack

Hook an event source

Connect your IDE

Connect IDE wizard

Wire it into your IDE or agent

Stop pasting Discord webhooks into every agent prompt

Built for production agent workflows

Encrypted secrets

SSRF protection

OAuth 2.1 + Bearer keys

Per-key tool ACL

IP allowlists

Full audit trail

Rate limiting

Multi-tenant isolation

Signed inbound hooks

Sources in, destinations out

Job packs for common ops jobs

On-call

Web3 watch

Solana watch

Stripe ops

Ship guard

Status room

Simple pricing for every stage

Free

Pro

Platform

Frequently asked questions

Start free. Wire your agent for ops alerts.