Kapso for AI agents
Kapso provides APIs for WhatsApp messaging, customer and contact management, broadcasts, and workflows, letting businesses run structured conversations and campaigns over WhatsApp at scale. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Kapso.
List recent conversations
List recent WhatsApp conversations to find a customer thread that needs a reply.
Check a phone number's health
Check a WhatsApp business number's health status before a large broadcast send.
Look up a workflow's configuration
Pull a workflow's configuration to confirm it routes messages the right way.
10 Kapso actions, graded by risk.
Every Kapso action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
10Look things up. Allowed by default.
- kapso.get_functionGet Function
- kapso.get_workflowGet Workflow
- kapso.list_messagesList Messages
- kapso.list_customersList Customers
- kapso.list_functionsList Functions
- kapso.list_workflowsList Workflows
- kapso.get_phone_numberGet Phone Number
- kapso.list_conversationsList Conversations
- kapso.list_phone_numbersList Phone Numbers
- kapso.get_phone_number_healthGet Phone Number Health
write
0Create and change things. Allow, or ask the user first.
- No write actions.
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Kapso in three steps.
- 01Your users connect KapsoThey add their Kapso api key on Arc0 Connect, under your brand. It goes straight into the vault.
- 02You set the rulesReads run, and writes like “updates” can wait for the user to approve.
- 03Any agent can actYour agent calls Kapso through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('kapso', { read: 'allow', write: 'ask', destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Kapso connects.
Users add their Kapso api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
The same Kapso connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- API key
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Kapso from any agent.
ClaudeChatGPTCursor
Codex
VS CodeOpenAI Agents SDKClaude Agent SDK
Vercel AI SDK
Mastra
LangGraph
Kapso and Arc0, answered.
Can I use Kapso with Claude, ChatGPT or Cursor?
Yes. Connect Kapso to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Kapso actions you allow.
How do users connect Kapso?
Users add their Kapso api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.
Which Kapso actions can my agent take?
10 in total: 10 read, 0 write and 0 destructive. Your policies decide which of them each agent may call.
Can I make my agent read-only in Kapso?
Yes. Allow read actions and deny writes in the Kapso policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Kapso too?
Yes. The same Kapso connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Kapso into your agent.
Your users connect Kapso once, under your brand. Your agent gets 10 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan