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.
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.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 anaction and params.
| Tool | Actions |
|---|---|
status | Shows auth, project status, customer count, WhatsApp number count, and next steps |
search_docs | Searches Kapso and WhatsApp docs |
customers | help, list, get, create, update, delete |
setup_links | help, list, create, update, revoke |
whatsapp_numbers | help, list, get, resolve, health, start_setup, create, update, delete |
whatsapp_conversations | help, list, get, set_status |
whatsapp_messages | help, list, get, send, mark_read |
whatsapp_templates | help, list, get, create |
whatsapp_webhooks | help, list, get, create, update, delete |
action: "help" on grouped tools to get required params, optional params, and examples.
Examples
Ask your agent to check setup:Project MCP vs Docs MCP
| Server | Endpoint | Use it for |
|---|---|---|
| Project MCP | https://api.kapso.ai/mcp | Operating WhatsApp numbers with browser sign-in or an API key |
| Docs MCP | https://docs.kapso.ai/mcp | Documentation lookup only |

