Check project status
Ask Codex to inspect auth, project state, connected numbers, customer count, and next setup steps.
Use Codex with WhatsApp
Connect Codex to Kapso WhatsApp MCP for live WhatsApp operations, or use the Kapso CLI when Codex is working inside a terminal session.
Let Codex inspect the WhatsApp layer
Kapso gives Codex controlled access to the product state around WhatsApp: numbers, conversations, messages, templates, webhooks, customers, and setup links.
Read conversations
List recent conversations and messages so Codex can understand what happened before suggesting a change.
Manage webhooks
Create, list, update, or delete WhatsApp webhooks for connected numbers.
Create setup links
Let Codex generate customer setup links when your platform needs customer-owned WhatsApp onboarding.
Use CLI with shell access
When Codex has a terminal, it can use @kapso/cli for the same operational tasks.
Keep humans in control
Use explicit approval for real-user sends and production customer operations.
Connect Codex to Kapso WhatsApp MCP
Kapso WhatsApp MCP runs at https://api.kapso.ai/mcp and authenticates with a project API key.
Use Authorization: Bearer when the MCP client supports bearer token env vars.
Use a project API key from the Kapso dashboard.
Do not print the API key in chat output or logs.
Use the CLI instead when Codex should operate through shell commands.
What Codex should operate
The safest Codex workflow is read first, propose next, then perform production writes only with approval.
Read state
Status, numbers, conversations, messages, templates, webhooks, customers, and setup links.
Edit code
Use docs, CLI output, and MCP state to update your application without guessing WhatsApp behavior.
Guard credentials
Keep project API keys, webhook secrets, and production sends behind explicit boundaries.
Give Codex the current WhatsApp context
Connect Kapso WhatsApp MCP, ask Codex to check project status, and let it work from live state instead of stale assumptions.