WhatsAble agent skill
One SKILL.md that teaches Claude Code, Cursor and other coding agents how to connect the WhatsAble MCP server and what to know about WhatsApp. It replaces the old Notifyer script skills.
The WhatsAble agent skill is one short SKILL.md file in the open Agent Skills format. An agent that loads it knows how to connect the WhatsAble MCP server, and what to know about WhatsApp before it sends anything.
SKILL.md
The skill itself, served from this site. Read it, or point your agent at it.
What the skill tells your agent
- How to connect. The server URL,
https://api.whatsable.app/mcp, and the two ways to sign in: an OAuth connection that a person approves, or an API key in a header. - To ask the server first. The skill holds no tool list. It tells the agent to call
get_guide, which answers from what this connection may do: its tools, the suggested workflows and the WhatsApp rules. New tools reach the agent without a new skill. - How WhatsApp works. The 24-hour window and when a template is required, Meta's approval of templates, the AI agent and a person taking over, and why a connection can use only the numbers it was given.
- What the MCP server does not do, and why. It does not create an account or sign in for a person, show an API key, connect or refresh a number's Meta connection, buy a plan, or change the team. Webhooks are planned. The skill sends the person to the right page in WhatsAble for each.
You can connect the MCP server without the skill: Connect your AI app is enough. The skill helps coding agents, which load skills by themselves, use the server well.
Install it
The skills command installs it for Claude Code, Cursor, Codex, GitHub Copilot and the other agents that read Agent Skills:
npx skills add whatsable/whatsapp-business-agent-skillsAdd -g to install it for every project instead of the current one.
The skill is not the connection. The agent still needs the MCP server connected, by an owner or an admin on a plan that includes the API. See What you need.
Moving from the old Notifyer skills
Until version 0.4.0, the same repository shipped three skills, setup-notifyer, automate-notifyer and chat-notifyer, made of about 60 Node scripts. They signed in with an email and a password and called the legacy Notifyer system. Accounts that moved to the new WhatsAble app are no longer served by that system, so those scripts act on the wrong system or fail.
Version 1.0.0 replaces them with this one skill:
Remove the old skills
Delete the setup-notifyer, automate-notifyer and chat-notifyer folders from your agent's skills folder.
Remove the old variables
Delete NOTIFYER_API_BASE_URL, NOTIFYER_API_TOKEN and NOTIFYER_CHAT_ORIGIN from your shell profile, your .env files and your app's secrets.
Install the new skill and connect
Install the skill as above, connect the MCP server, and ask your agent "What can you do with WhatsAble?".
| The old scripts did | Now |
|---|---|
| Read and send messages, labels, notes, handoff, scheduled sends | The MCP server's tools. Ask the agent, which calls get_guide. |
| Templates, broadcasts, AI bots | The MCP server's tools. Creating a template or a broadcast, or changing an AI agent, needs Full access. |
| Sign up, log in, fetch the API key, team, plans | In the WhatsAble app. An agent never holds your password or reads a key. |
| Webhooks for Make, Zapier and n8n | In the WhatsAble app, under Settings > Webhooks, or by the Zapier, Make and n8n integrations themselves. |
Next steps
- Connect your AI app: each app, step by step.
- Access and connections: what an agent may do, and how to revoke it.
- Suggested workflows: what to ask.
Access and connections
Choose what an AI app can do in WhatsAble and which numbers it can use, see every connected AI app, and revoke one. Removing the app on the AI side does not revoke it.
Troubleshooting
What to do when your AI app cannot connect to WhatsAble, a tool is missing, a message comes back Not sent, or the app suddenly asks you to sign in again.