Your agent can set up and run your Tawked account with you: create WhatsApp templates and tell you when Meta approves them, add members and support team members, add an e-mail sending domain and check its DNS, run campaigns, read the wallet. It acts as you, never more, and it stops to ask you when a step is yours.
There are two ways in, and both end in the same place:
Either way the agent holds an account token that acts as you: the same rules as the console, within the permissions and applications you chose. See Security.
Before you start
- A Tawked account with its setup finished. Signing up takes your phone’s code, so it is yours to do at tawked.com. Everything after it, the agent can do.
- For a token: open Settings → Account API in the console and choose Create token. Name it after the agent, choose its permissions and applications, keep Ask me first under Before a consequential action, and choose Create token. The token is shown once: copy it. Its reveal also shows the commands below with the token filled in (the Claude Code command, the MCP client’s settings, and the REST tab’s
export TAWKED_TOKEN=…), which go in a terminal or a settings file, never a chat; and Give this to your agent, the prompt for an agent that calls the API, which holds no secret.
Connect your agent
Claude Code
Claude
ChatGPT
Cursor
Codex
A script
Sign in (nothing to copy):Then type /mcp in Claude Code, choose tawked, then Authenticate. Your browser opens on Tawked: sign in, choose the applications and what it can do, and choose Allow.Or with a token (for a token you made, with its approvals):Then start Claude Code and give it the prompt for an assistant. For Claude on the web and Claude Desktop:
- Open Settings → Connectors, then Add custom connector.
- Name it Tawked, paste
https://tawked.com/mcp, then Connect.
- Tawked opens: sign in, choose the applications and what it can do, and choose Allow.
- In a new chat, turn on the Tawked connector from the chat’s tools menu, and give Claude the prompt for an assistant.
- Open Settings → Apps & Connectors → Advanced settings, and turn on Developer mode.
- Choose Create, name it Tawked, paste
https://tawked.com/mcp, and choose OAuth authentication.
- Tawked opens: sign in, choose the applications and what it can do, and choose Allow.
- In a new chat, add the Tawked connector, and give ChatGPT the prompt for an assistant.
-
Add the server to
~/.cursor/mcp.json:
-
In Cursor’s settings, open MCP and choose Connect beside tawked.
-
Tawked opens: sign in, choose the applications and what it can do, and choose Allow.
-
In the agent chat, give Cursor the prompt for an assistant.
To use a token instead, give the server a header and skip the sign-in:
-
Add the server and sign in:
-
Your browser opens on Tawked: sign in, choose the applications and what it can do, and choose Allow.
-
Start Codex and give it the prompt for an assistant.
A script, or an agent of your own that calls HTTP, uses the Account API directly with a token. Keep the token in an environment variable:GET /v1/me answers who the token acts for, its permissions and applications, and next_steps: what is left to set up, each step with the operation that does it or the human_action you take. Then find an operation and call it:Every answer that needs you carries human_action, and a consequential call with Ask me first answers 428 approval_required. A script handles both like this:For an agent that writes its own calls, give it the prompt for an agent that calls the API.
On the consent page, choose Everything you can do for an agent that sets things up (it shows you a preview and waits for your yes before anything that sends, deletes or spends), or Read only for one that reports. Choose the applications it works on, or every application. The assistant’s token then shows under Settings → Account API, marked Assistant: open it to change its permissions, applications or approvals, or revoke it there (or on an application’s AI assistants page) to disconnect it.
The prompt to give your agent
Paste it at the start of the chat, or into the agent’s own instructions (Claude Code’s CLAUDE.md, Codex’s AGENTS.md, Cursor’s rules), so the agent knows how to work with Tawked and when to stop for you.
For Claude Code, Claude, ChatGPT, Cursor or Codex connected to the MCP server: For an agent that calls the Account API over HTTP, with the token in its environment as TAWKED_TOKEN:Give this to your agent, on the token’s reveal in the console, is this same text. It holds no secret, so it is safe to paste into a chat: put the token in the agent’s environment as TAWKED_TOKEN first.
Ask it something
Start with what it can see, then give it a job:
- “What can you do in my Tawked account, and what is left to set up?”
- “Create a WhatsApp utility template that tells a customer their order shipped, with their name and the order number, and tell me when Meta approves it.”
- “Add Sara, 0500000000, to the support team of my store’s application.”
- “Add the sending domain mail.example.com and tell me which DNS records to add.”
- “How much is in my wallet, and how many WhatsApp messages did we send this week?”
When a step is yours, the agent stops and tells you what to do, with a link: connect your WhatsApp number in Meta’s window, top up by card, approve a send. Do it, tell the agent you are done, and it checks and goes on. Every such moment is listed in The person in the loop.
Next
Last modified on October 15, 2026