Trusted by 40,000+ developersOne endpoint gives any MCP client tools for your WhatsApp numbers, conversations, messages, templates, and webhooks.
Any MCP client can call these tools: Claude Code, Codex, Cursor, or your own agent. They run against your Kapso project, so answers come from your real numbers and conversations.
>Which conversations have been open longer than a day?
Two conversations have been open for more than 24 hours without a reply from you.
-Diego Morales: invoice question (31h)
-Sofía Herrera: warranty claim (26h)
>Close the ones that are resolved
kapso · whatsapp_conversations set_status ended
Paste the prompt into your agent, or run the commands yourself.
Your agent follows the setup guide for its own client and asks before creating keys.
>Set up WhatsApp for this project with Kapso. Follow the steps at kapso.com/whatsapp-mcp-server and ask me before creating any keys.
Any client that supports remote MCP servers over HTTP.
Create one in your Kapso dashboard. Or skip it and sign in through the browser.
export KAPSO_API_KEY="your_project_api_key"
In Cursor this goes in .cursor/mcp.json. Other clients take the same URL and header.
{
"mcpServers": {
"kapso": {
"url": "https://api.kapso.ai/mcp",
"headers": { "Authorization": "Bearer ${env:KAPSO_API_KEY}" }
}
}
}Try a read-only request first.
> Which of my WhatsApp numbers are connected?
npm install -g @kapso/cliCoding agents can read this page and set themselves up. Or copy the instructions and paste them into any agent.
You are reading https://kapso.com/whatsapp-mcp-server. Kapso is the WhatsApp API for developers. Its MCP server gives you tools for the WhatsApp numbers, conversations, messages, templates, and webhooks in the user's Kapso project. Follow these steps to add those tools to the MCP client you are running in.
Check for an API key.
Check that KAPSO_API_KEY is set, without printing it. If it is not, ask the user for a Kapso project API key, or use browser sign-in if your client supports MCP OAuth. Never create keys, sign up, or approve access on their behalf.
Register the MCP server in your client.
Claude Code and Codex have their own pages: kapso.com/whatsapp-claude-code and kapso.com/whatsapp-codex. For Cursor, add this to .cursor/mcp.json:
{ "mcpServers": { "kapso": {
"url": "https://api.kapso.ai/mcp",
"headers": { "Authorization": "Bearer ${env:KAPSO_API_KEY}" }
} } }Reference the variable, never the key itself, in any file that can be committed.
Load the tools.
Most clients start MCP servers when a session starts. If the Kapso tools do not appear, ask the user to restart the client or reload its MCP servers.
Verify before you continue.
Call the status tool. If it fails, stop and tell the user the error it shows. A 401 means the key is missing or invalid. Do not carry on as if the tools were there.
Start read-only, then report back.
Use whatsapp_numbers and whatsapp_conversations to look before you act, and confirm with the user before sending messages or changing templates, webhooks, or setup links. Tell them which project and numbers you can reach.
Yes. Kapso WhatsApp MCP runs at https://api.kapso.ai/mcp over streamable HTTP. MCP clients connect with a project API key or by signing in through the browser.
It can inspect connected numbers and their health, read conversations and messages, send messages, manage templates and webhooks, search logs, and create customers and setup links for customer-owned WhatsApp accounts.
Any client that supports remote MCP servers over HTTP, including Claude Code, Codex, and Cursor. Send the key as an Authorization: Bearer header or an X-API-Key header.
Yes. Kapso is a Meta Business Partner and uses the official WhatsApp Business Platform, so your numbers and messages go through Meta directly.
The free plan includes a sandbox number and 2,000 messages a month.