Kenso MCP tools

Slack Alerts slack_alerts

Proactive Slack alerts: Kenso posts in a channel on its own when a hot reply comes in, a meeting is booked, a campaign's bounce rate passes a threshold, a campaign stops sending or a domain is blacklisted. List, set up (create) or stop (delete) one.

Call it from an MCP client connected to https://mcp.ken.so/mcp: reads go through slack_alerts_read and changes through slack_alerts_write. Each takes operation plus that operation's parameters, and your workspace role decides which operations you see.

Each operation with a route calls the Kenso API at https://api.ken.so with Authorization: Bearer <Kenso API key>, Ken-Version: 1.1 and X-Ken-Workspace-Id: <workspace id>. You can call that route directly with the same headers.

Operations: create, delete, list

create

Write. POST https://api.ken.so/v1/integrations/slack/alerts

Body (json): campaignId integer, channel string, kind string, threshold number

Set up a proactive Slack alert: from then on Kenso posts in the channel without being asked. kind: hot_reply, meeting_booked, bounce_rate (threshold percent, default 3), sending_stopped or domain_blacklisted.

POST /api/v1/integrations/slack/alerts. Internal. Sends Ken-Version 1.1.
- hot_reply: a lead's reply is classified interested. One post per lead and campaign.
- meeting_booked: a meeting counts as booked. Takes no campaign_id.
- bounce_rate: a campaign's bounce rate over the last 7 days goes above threshold percent (0.1 to 50,
  default 3), on at least 50 sends. One post per breach, again only after it recovers.
- sending_stopped: a sending campaign sends nothing for 3 business days. One post per stall.
- domain_blacklisted: a domain of the workspace is listed on a blacklist in its daily domain health
  check. One post per domain and blacklist, again only after it was delisted. Takes no campaign_id.
campaign_id narrows every kind but meeting_booked and domain_blacklisted to one campaign. channel is a
Slack channel name (#sales) or id; leave it out for the person's own Kenso notification channel
("alert me").
Kenso first posts a short setup note in the channel, which proves it can post there; nothing is saved
when it cannot. Returns the alert (201): id, kind, trigger, preview, howToStop. validation_failed names
the field: channel with required, invalid, slack_not_connected or channel_unreachable (invite the Kenso
app to the channel); kind with limit_reached past 20 alerts. not_found when the campaign is not in the
workspace, or while proactive alerts are off for the workspace. An identical live alert is returned
instead of a second one.

delete

Write. DELETE https://api.ken.so/v1/integrations/slack/alerts/{alertId}

Path: alertId

Stop a proactive Slack alert. Returns 204. Find alert_id with slack_alerts(operation="list").

DELETE /api/v1/integrations/slack/alerts/{alertId}. Internal. Sends Ken-Version 1.1.
Kenso stops posting it at once. not_found unless it is a live alert in this workspace.

list

Read. GET https://api.ken.so/v1/integrations/slack/alerts

List the workspace's proactive Slack alerts: what fires each, where it posts and how to stop it. Use it for "what alerts do I have?" and to find the alert_id to stop.

GET /api/v1/integrations/slack/alerts. Internal. Sends Ken-Version 1.1.
Items, oldest first, at most 20: id, kind (hot_reply, meeting_booked, bounce_rate, sending_stopped,
domain_blacklisted),
campaignId, threshold (percent, bounce_rate only), channelId, channelName, trigger (what fires it, in
words), preview (a sample post), howToStop and createdAt. not_found while proactive alerts are off
for the workspace.