Skip to main content
Project MCP gives AI agents live tools to send messages, read conversations, manage templates, and configure webhooks on your WhatsApp numbers. Use it when an MCP-capable agent should operate a WhatsApp number without shell access — read inbound messages, send replies, manage templates, configure webhooks, and provision new numbers. Endpoint:

Authentication

Choose the auth option your MCP client supports:
  • Browser sign-in: configure the MCP URL, sign in to Kapso, and choose one project.
  • API key: create a project API key in Kapso and pass it as a header.
Both options give the agent access to the same Project MCP tools. Accepted API key headers:
Use Authorization: Bearer for bearer-token clients. Use X-API-Key when your MCP client lets you configure custom headers.

Connect

Browser sign-in

For clients that support browser sign-in, configure only the MCP URL.
When Kapso opens in the browser, sign in and select the project the client should use.

API key

Set your project API key:

Use X-API-Key instead

Codex CLI has no --header flag, so X-API-Key goes in ~/.codex/config.toml. For Cursor and Claude Code, just swap the header.

Tools

Project MCP exposes grouped tools. Most tools accept an action and params. Use action: "help" on grouped tools to get required params, optional params, and examples.

Examples

Ask your agent to check setup:
Ask your agent to create a setup link:
Ask your agent to read and send WhatsApp messages:

Project MCP vs Docs MCP

Use the CLI when your agent has terminal access. Use Project MCP when your agent supports MCP and should operate Kapso directly.