Kenso MCP tools

Onboarding Builds onboarding_builds

Call it from an MCP client connected to https://mcp.ken.so/mcp: reads go through onboarding_builds_read and changes through onboarding_builds_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: inputs-create, create, get

inputs-create

Write. POST https://api.ken.so/v1/onboarding/builds/{buildId}/inputs

Path: buildId

Body (json): accountIds array, choiceIds array, importId string, instruction string, kind string, off array, questionId string, reason string, target object, text string, value string

Send one input to an onboarding build: an answer, a brief, a chat turn, a correction or an edit. Answer Ken's questions with kind answer. Full docs: describe_tools(['api_onboarding_build_inputs_create'])

POST /api/v1/onboarding/builds/{build_id}/inputs. Internal, behind the onboarding_v5 flag.
Returns 202 {id: obi_<n>, kind, status: accepted}; Ken applies it as the build runs.
kind and its fields:
  answer: question_id, choice_ids (from the question's choices), optional text (the
    something-else answer). Use it for every question Ken asks.
  brief, message: text (at most 4,000 characters; a brief, or an answer to recruiting_role,
    on a recruiting build takes 8,000 for a pasted job description, and a sales build
    refuses more than 4,000).
  read_confirmed: nothing. read_corrected: off (product, buyer, market, size), optional text.
  experience: value never|some|pro|agency. goal: value accounts|campaigns|both.
  deal_size: value lt_1k|1k_5k|5k_25k|25k_100k|gt_100k.
  edit: target {type: plan|touch|brief|icp|voice|accounts, id}, instruction
    shorter|other_angle|swap_accounts|more_formal|free_text, text for free_text.
  skip_accounts: account_ids, optional reason customer|competitor|other.
  launch_approved: only after the person approved the first launch in the app; it records
    that approval and closes their approve_mcp_launch step.
import: import_id of a finished Settings > Import run; Ken adds its companies, grades its
sequences and rewrites the best one. A finished build takes only answer, message, edit,
skip_accounts, import and launch_approved, and a canceled build takes nothing (else build_closed).

create

Write. POST https://api.ken.so/v1/onboarding/builds

Body (json): brief string, entry any JSON, experience string, listInviteToken string, mode string, source string, targetClientId string, website string

Start the workspace's onboarding build, or get the one that exists for the source. An agent signing someone up uses source mcp. Full docs: describe_tools(['api_onboarding_builds_create'])

POST /api/v1/onboarding/builds. Internal, behind the onboarding_v5 flag. One build per
workspace and source: 201 when this call created it, 200 with the existing build.
source: live, claim, social, mcp, performance or agency_client.
brief: what the company sells, at most 4,000 characters (8,000 with mode recruiting, where
it is the role or a pasted job description). website: the company site when
the sign-in email is personal. entry: the attribution object ({"source": ...}).
mode: recruiting. experience: never, some, pro or agency.
list_invite_token: a shared list to turn into plans first.
target_client_id: agency_client and performance only, a workspace you are an Admin of
(any other role answers 403 forbidden). agency_client requires it, and it must be a
white-label child (client workspace) of your agency, else 403 forbidden. The build then lives in that workspace: pass
client_id=<target_client_id> to get and inputs-create, or they answer build_not_found.
Returns the build: id (obd_<n>), source, status, stage, stages, tier, lastEventId,
performanceOffer, read, fields, accounts, accountsTotal, plans, assets, sequence,
messages, createdAt. Poll onboarding_builds get for progress; show the person
https://app.ken.so/start?build=<id>.

get

Read. GET https://api.ken.so/v1/onboarding/builds/{buildId}

Path: buildId

Read one onboarding build: its stages, Ken's read, accounts, plans and messages. Poll this for progress; there is no stream tool. Full docs: describe_tools(['api_onboarding_builds_get'])

GET /api/v1/onboarding/builds/{build_id}. Internal, behind the onboarding_v5 flag.
build_id: obd_<n> or the bare number. Returns the snapshot: status (queued, running,
waiting_input, succeeded, failed or canceled), stage, stages [{key, status, ms,
startedAt}] (startedAt once the stage has started), tier, lastEventId, performanceOffer,
read {oneLiner, company, persona, product, buyer, market, size, confirmed}, fields,
accounts (no scores; the order is the ranking), accountsTotal, plans (committee names and
titles, no emails), assets, sequence, messages, wowAt, createdAt, completedAt, error. A
build of another workspace is build_not_found.