Kenso MCP tools

Outbound Event Posts outbound_event_posts

People going to an outbound event, found in public LinkedIn posts: check-posts looks again (once per event a day) and Kenso adds them in the background at a price per person, up to the event's spend limit. Read where it stands in outbound_events get (posts), the people with outbound_events attendees-list source=linkedin_post, and set the limit with outbound_events update (post_spend_limit_millicredits).

Call it from an MCP client connected to https://mcp.ken.so/mcp: changes through outbound_event_posts_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: check-posts

check-posts

Write. Early access: needs accounts, event_outbound on for the workspace. POST https://api.ken.so/v1/outbound-events/{eventId}/check-posts

Path: eventId

Look again for people whose public LinkedIn post says they go to the event. Once per event a day. Kenso adds them in the background at a price per person, up to the event's spend limit.

POST /api/v1/outbound-events/{eventId}/check-posts. Staff. Sends Ken-Version 1.1 and
X-Ken-Actor: agent. No body. Links the event to Kenso's shared search for the same
real-world event and queues a new search, unless that search ran in the last day for another
workspace (then the people it found are added). People are added in the background, each at
its price in millicredits (1,000 = 1 credit), until posts.spendLimitMillicredits; change the
limit with outbound_events(operation="update", event_id=..., changes={
"post_spend_limit_millicredits": ...}). A second call within a day is validation_failed
("This event was checked in the last 24 hours."), and so is a call while finding people
from LinkedIn posts is switched off. Returns 200 with the event and its posts block {status,
lastCheckedAt, addedCount, spentMillicredits, spendLimitMillicredits, waitingCount,
waitingMillicredits, checkAgainAt}. Read the people with outbound_events(
operation="attendees-list", event_id=..., source="linkedin_post"); each carries proof
{url, postedAt, quote} and confidence (0-100). Another workspace's event is not_found.