Kenso MCP tools

Claim Links claim_links

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

accept

Write. POST https://api.ken.so/v1/claim-links/{token}/accept

Path: token

Claim the workspace Kenso pre-built for you, from the token in its claim link. You become its owner and admin; workspaces you already have stay as they are.

POST /api/v1/claim-links/{token}/accept. Sends Ken-Version 1.1. Needs a person's sign-in, not an API key, and
works before the caller has any workspace. The claim binds only when the signed-in email is verified and is the
address the link was sent to or an address at the company's own domain (never a free-mail domain), or, for a
social link, when the sign-in is the LinkedIn account that got the message.

Returns {workspaceId, buildId (omitted when the workspace has no build), boundBy (email, domain or linkedin),
additionalWorkspace}. Errors: claim_not_bound 403 (the sign-in does not match the link), claim_accepted 409
(already claimed), claim_expired 410 (expired or withdrawn), not_found 404 (unknown token, deleted workspace, or
claim links are off).

Example: claim_links(operation="accept", token="<token from the claim link>")