WhatsBuddy
WhatsApp from the tools you already use
Claude, ChatGPT, your API, or a terminal. Same company, same number, no extra inbox.
Claude
Send and schedule WhatsApp from the Claude chat you already live in.
ChatGPT
Build an agent in ChatGPT and put it on your linked WhatsApp number.
REST + CLI
Same company token. Scripts, CRMs, and `whatsbuddy` in the terminal.
MCP
Tool-calling clients talk to your WhatsApp data without a custom wrapper.
Claude
WhatsApp via Claude
Ask Claude to message a client, set a weekly reminder, or check a chat — WhatsBuddy does the send.
- Link WhatsBuddy to Claude in a few steps
- Send WhatsApp without leaving the Claude thread
- Schedule follow-ups from the same conversation
ChatGPT
WhatsApp via ChatGPT
Draft the agent where you already write prompts. Run it on the WhatsApp account you linked in WhatsBuddy.
- Create agents in ChatGPT
- Use them on your linked number
- Schedule and send from the ChatGPT side
Builders
REST, CLI, and MCP — one company scope
Automations, internal tools, and agents all use the same token on company_settings. No public WhatsApp manager. No extra tenancy model.
- REST API for accounts, chats, messages, schedules
- `whatsbuddy` CLI for dumps and day-to-day ops
- MCP tools for clients that speak the protocol
For developers
Same token. Three doors.
Company REST, CLI, and MCP never cross tenants. Rotate tokens in company settings.
REST
API reference — accounts, chats, messages, schedules, collections.
CLI
Download whatsbuddy — dump, accounts, and settings from the terminal.
Developer account
Create a developer account if you ship this for other companies.
Wire it once. Keep chatting in WhatsApp.
Start a trial, or book a demo if you want Claude / ChatGPT / API walked through live.