Notifications and coding agents

Slack, Microsoft Teams and email

In the console, open Settings → Notifications, add a destination, then add a rule that chooses what to send there.

Destination	What you need
Slack (incoming webhook)	A https://hooks.slack.com/services/… URL from a Slack app
Slack (app)	A bot token (xoxb-…) with chat:write, and the channel to post in
Microsoft Teams	An incoming webhook or Workflows URL
Email	Up to 20 addresses (self-hosted installations need SMTP configured)

Rules apply to every repository or to one, with a minimum severity (major and above by default). You can send:

• Findings posted: a review found issues at or above the minimum severity.
• Reviews paused: the plan allowance, overage limit or budget stopped reviews.
• Indexing failed: a repository could not be indexed.
• Weekly digest: every Monday, the week’s reviews, issues caught, addressed rate, spend and top open findings.

Each event is sent once per destination, with automatic retries. Webhook URLs and tokens are encrypted and never shown again; MergeHarbor only calls Slack and Microsoft hosts. Use Send test to check a destination.

Coding agents (MCP)

MergeHarbor is a Model Context Protocol server. Your coding agent can list the findings on a pull request, fix them in your checkout, and mark them addressed or dismiss them with a reason. It can also read your team’s rules and propose new ones for an admin to approve.

1. Open Settings → Coding agents (MCP) and choose Create API key for MCP. The agent acts with the permissions of the key’s role.
2. Copy the configuration for your client. For Claude Code:

claude mcp add --transport http mergeharbor https://<your MergeHarbor host>/mcp \
  --header "Authorization: Bearer $MERGEHARBOR_API_KEY"

For Cursor, add to .cursor/mcp.json:

{
  "mcpServers": {
    "mergeharbor": {
      "url": "https://<your MergeHarbor host>/mcp",
      "headers": { "Authorization": "Bearer ${env:MERGEHARBOR_API_KEY}" }
    }
  }
}

Clients that only start local servers can run mergeharbor mcp with MERGEHARBOR_URL and MERGEHARBOR_API_KEY set.

Then ask your agent something like “Fix the open MergeHarbor findings on PR 128”. Everything an agent changes is recorded in the audit log.