Skip to main content
Glama
Whatify MCP Server

Whatify MCP Server

by ashusingh1

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

whatify_ping

GET /ping

Connectivity/auth check

whatify_send_message

POST /send-message

Free-form text

whatify_send_template

POST /send-template

Approved templates only

whatify_send_flow

POST /send-flow

WhatsApp Flow (interactive form)

whatify_message_status

GET /messages/{id}

Delivery status

whatify_list_templates

GET /templates

whatify_list_flows

GET /flows

whatify_list_contacts

GET /contacts

whatify_get_contact

GET /contacts/{id}

whatify_create_contact

POST /contacts

whatify_update_contact

PUT /contacts/{id}

whatify_list_conversations

GET /conversations

whatify_get_conversation_messages

GET /conversations/{id}/messages

whatify_list_campaigns

GET /campaigns

whatify_get_campaign

GET /campaigns/{id}

Includes delivery/read rate

whatify_wallet_balance

GET /wallet/balance

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

  1. 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).

  2. Install dependencies:

    cd mcp-server
    npm install
  3. Configure environment variables:

    • WHATIFY_API_KEY — the key from step 1 (required)

    • WHATIFY_API_BASE_URL — defaults to http://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 start

then send newline-delimited JSON-RPC (initialize, tools/list, tools/call) on stdin. Easier: use the MCP Inspector:

npx @modelcontextprotocol/inspector node src/index.js

Available Tools

16 tools
whatify_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

    B3.2/5.0

    Scored across 16 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness3/5

    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

    Related MCP Servers

    • F
      license
      Not graded
      quality
      D
      maintenance
      OpenWA 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.
      -
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables 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