Whatify MCP Server
Provides tools for sending WhatsApp messages, templates, and flows, and managing contacts, conversations, campaigns, and wallet balance through the Whatify platform.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Whatify MCP Server send a WhatsApp message to +919876543210 saying your order is confirmed"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Whatify MCP Server
An MCP (Model Context Protocol) server that exposes Whatify's WhatsApp API — sending messages, templates, and Flows, plus reading contacts, conversations, campaigns, and wallet balance — as tools for MCP-compatible AI clients (Claude Desktop, Claude Code, etc.).
It's a thin wrapper around the existing v1/external REST API
(app/Http/Controllers/Api/ExternalApiController.php), authenticated the same way:
an API key generated from Settings → API Keys in the Whatify dashboard.
Tools
Tool | Maps to | Notes |
|
| Connectivity/auth check |
|
| Free-form text |
|
| Approved templates only |
|
| WhatsApp Flow (interactive form) |
|
| Delivery status |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| |
|
| Includes delivery/read rate |
|
|
send_flow and reading flows require the API key to have the send_flow /
read_flows permissions (added alongside this server — check the boxes when
generating a key in Settings → API Keys).
Related MCP server: Neuron MCP Server
Setup
Get an API key: log into Whatify → Settings → API Keys → generate a key with the permissions you want the AI tool to have (e.g.
send_message,send_template,send_flow,read_contacts).Install dependencies:
cd mcp-server npm installConfigure environment variables:
WHATIFY_API_KEY— the key from step 1 (required)WHATIFY_API_BASE_URL— defaults tohttp://localhost/api/v1/external; set this to your real app URL, e.g.https://whatify.in/api/v1/external
Using with Claude Desktop / Claude Code
Add to your MCP client config (e.g. claude_desktop_config.json, or via
claude mcp add for Claude Code):
{
"mcpServers": {
"whatify": {
"command": "node",
"args": ["C:/xampp/htdocs/whatify/mcp-server/src/index.js"],
"env": {
"WHATIFY_API_KEY": "wk_xxxxxxxxxxxxxxxx",
"WHATIFY_API_BASE_URL": "https://whatify.in/api/v1/external"
}
}
}
}Restart the client, then ask it to send a message, e.g.:
"Using Whatify, send a WhatsApp message to +91XXXXXXXXXX saying the order has shipped."
Manual test
You can talk to the server directly over stdio for debugging:
npm startthen send newline-delimited JSON-RPC (initialize, tools/list, tools/call) on
stdin. Easier: use the MCP Inspector:
npx @modelcontextprotocol/inspector node src/index.jsAvailable Tools
16 toolswhatify_create_contactC
Create a new contact, or update-and-return an existing one with the same phone number.
Inputs: phone (required), name, tags, email, +2 more.
whatify_get_campaignB
Get a single campaign with delivery/read rate stats.
Inputs: campaign_id (required).
whatify_get_contactC
Get a single contact by id.
Inputs: contact_id (required).
whatify_get_conversation_messagesC
Get the messages for a given conversation.
Inputs: conversation_id (required), per_page.
whatify_list_campaignsC
List broadcast campaigns.
Inputs: status, per_page.
whatify_list_contactsC
List/search contacts.
Inputs: tag, name, phone, status, +1 more.
whatify_list_conversationsC
List inbox conversations.
Inputs: status, per_page.
whatify_list_flowsC
List the account's WhatsApp Flows.
Inputs: status.
whatify_list_templatesB
List the account's WhatsApp message templates.
Inputs: status, category.
whatify_message_statusA
Get the delivery status of a previously sent message by its Whatify message id.
Inputs: message_id (required).
whatify_pingA
Check connectivity and API key validity against the Whatify API.
Inputs: no named parameters.
whatify_send_flowC
Send a WhatsApp Flow (interactive form) to a phone number via Whatify.
Inputs: phone (required), flow_id (required), flow_cta, whatsapp_account_id.
whatify_send_messageB
Send a free-form WhatsApp text message to a phone number via Whatify.
Inputs: phone (required), message (required), whatsapp_account_id.
whatify_send_templateB
Send an approved WhatsApp message template to a phone number via Whatify.
Inputs: phone (required), template_name (required), body_params, header_params, +1 more.
whatify_update_contactC
Update an existing contact.
Inputs: contact_id (required), name, tags, email, +2 more.
whatify_wallet_balanceB
Get the account's WhatsApp messaging wallet balance.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 16 tools
Each tool targets a distinct resource or action (e.g., contacts, campaigns, messages, flows) with no overlap. Tools like send_message, send_flow, and send_template are clearly different in purpose.
All tools use a consistent 'whatify_' prefix followed by an action_noun pattern (e.g., create_contact, list_campaigns, send_message). The naming is predictable and uniform.
16 tools provide a comprehensive yet focused set for a WhatsApp messaging server without being overwhelming. Each tool serves a clear purpose within the domain.
Core operations like sending messages and managing contacts are covered, but missing create/update/delete for campaigns, templates, and flows. This leaves gaps for full lifecycle management.
Related MCP Connectors
Send WhatsApp messages and templates, manage chats, contacts, broadcasts and AI agents.
Official WhatsApp Business API (Meta Cloud API) for your own CRM or SaaS, from WasapFlow, a Meta Tech Provider. Your AI can search the Bridge docs, list connected numbers, create Embedded Signup links so clients connect their own WhatsApp (Coexistence supported), send text and template messages, list templates, check and retry failed webhooks, see usage and open support tickets. Docs tools work without a key; account tools use the x-partner-key header.
WhatsMCP connects Claude and other MCP-compatible AI agents directly to WhatsApp. Send and receive text, images, documents, and voice notes; manage groups (create, add/remove members, promote admins); look up contacts and profiles; follow channels; and read call and message history — all through a standard MCP interface. For voice use cases, WhatsMCP offers SIP-based calling plans (inbound-only, or full inbound/outbound) so AI voice agents can answer and place WhatsApp calls, plus low-latency WebSocket integrations with voice agent providers like ElevenLabs. Multiple WhatsApp accounts can be paired and managed per workspace, with webhook support for real-time inbound message delivery to your own infrastructure.
Read, summarize and send your own WhatsApp messages from AI assistants (OAuth 2.1).
Related MCP Servers
- AlicenseBqualityBmaintenanceEnables sending messages, images, documents and more on WhatsApp directly from any MCP-compatible AI, with tools for chat management, groups, and webhooks.371MIT
- AlicenseBqualityCmaintenanceEnables AI assistants to manage WhatsApp business operations including chatbots, broadcasts, campaigns, and contacts through 120+ MCP tools.10060 npmMIT
- FlicenseNot gradedqualityDmaintenanceOpenWA MCP server that bridges AI agents to the OpenWA WhatsApp API, exposing 40 tools for sessions, messages, contacts, groups, and webhooks so agents can read and send WhatsApp messages through a self-hosted OpenWA gateway.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP-compatible AI clients to work with self-hosted, linked WhatsApp accounts by exposing eight tools for listing sessions, chats, contacts and groups, reading message history, checking numbers, inspecting account details, and sending text messages.MIT