DripRaven WhatsApp campaigns
Server Details
Run WhatsApp Business campaigns from any AI assistant: contacts, segments, and broadcasts.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- OAuth
- Works in Glama
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 34 tools
Most tools target a distinct resource+action (create_template vs update_template vs set_template_variables, send_broadcast vs preview_broadcast vs cancel_campaign), and descriptions explicitly steer between near-neighbours (get_started vs account_status, whatsapp_status vs billing_status). The remaining overlap is in the four status/setup tools that echo each other's fields (plan, whatsapp_health), and the two connection paths (connect_whatsapp vs whatsapp_connect_link), which are distinguishable but easy to misselect at a glance.
Predominantly consistent verb_noun snake_case: list_*, get_*, create_*, update_*, delete_*, send_*, plus search/buy/release_phone_number and sync_templates. Minor deviations are the noun-first tools account_status, billing_status, whatsapp_status and whatsapp_connect_link, which break the pattern but stay readable.
34 tools is heavy, but the surface spans many real sub-domains (contacts, templates, segments, campaigns, automations, phone numbers, billing, connection), so most tools earn their place. Still, four status/setup tools and five phone-number tools push it past the comfortable range, and a few could be merged or folded into parameters.
Strong lifecycle coverage: full template CRUD plus sync and variable mapping, automation create/update/delete/list, campaign send/preview/list/stats/cancel, contact add/import/list, segments, billing and phone rental. Gaps are minor but real — no delete_contact, no update/delete_segment, no get-single-campaign detail, and no way to read inbound replies or message history, which agents must work around.
Available Tools
34 toolsaccount_statusARead-onlyIdempotentInspect
Identify which DripRaven account/workspace this MCP connection is linked to. Returns { workspace_id, workspace_name, owner_email, owner_name, created_at, plan, subscription_status, whatsapp_connected, whatsapp_health }. whatsapp_health.ok false means Meta reported an account-level problem and sends will fail; relay its message and remediation. Call this when the user asks who/which account or workspace they are connected as, to confirm they are operating on the right account before making changes, or to state the account out loud. owner_email is the human who owns the workspace; plan/subscription_status mirror billing_status. For "what is this" or "what can you do", call get_started instead.
Inputs: no named parameters.
add_or_update_contactAIdempotentInspect
Add or update a contact. Idempotent on phone — updates name, tags, and fields if the contact already exists. Phone must be E.164 format (+49171234567). source and external_id enable CRM sync. Set opted_out: false to RE-SUBSCRIBE a contact who previously opted out (only with genuine consent), or true to unsubscribe them; omit it to leave their opt-out status unchanged. If this creates a NEW contact whose tag matches an enabled automation (list_automations), it is queued for that automation's message.
Inputs: phone (required), name, tags, fields, +3 more.
billing_statusARead-onlyIdempotentInspect
Check whether this workspace can send broadcasts. Returns { billing_enabled, plan, subscription_status, active, usage: { period, message_count, limit }, plans }. Call this before send_broadcast when the user expects real delivery. When active is false, sending is blocked with SUBSCRIPTION_REQUIRED — use get_subscribe_link to get a checkout link. plans lists the available tiers (key, name, monthly_price_cents, messages_per_month) so you can show the user the options and prices before they subscribe.
Inputs: no named parameters.
buy_phone_numberAInspect
Rent one of the numbers from search_phone_numbers for this workspace, so the user has a number to register with WhatsApp. Call this ONLY with a number the user explicitly chose from search_phone_numbers results, after telling them the monthly price. Returns { checkout_url, phone_number, monthly_price_cents, instructions }: give the user checkout_url — nothing is bought and nothing is charged until they complete that Stripe checkout. Afterwards call list_phone_numbers; the number is usable once its status is active, and then whatsapp_connect_link hands over the signup link with no further phone-number confirmation needed. In Meta's signup the user must verify the number by Phone call, not SMS: we answer the call and email them the code.
Inputs: phone_number (required), country, number_type.
cancel_campaignAInspect
Cancel a scheduled broadcast so it never sends. Pass the campaign_id (from send_broadcast or list_campaigns). Only works while the campaign is still 'scheduled': once it has started sending or finished you cannot cancel it, and messages already sent cannot be recalled. On success returns the campaign with status 'cancelled'. If it is not scheduled, the call fails with CAMPAIGN_NOT_CANCELLABLE and the error message names its current status — check with list_campaigns or get_campaign_stats. To stop an in-flight or completed send instead, the only lever is to disconnect the WhatsApp number (disconnect_whatsapp).
Inputs: campaign_id (required).
connect_whatsappAIdempotentInspect
Connect this workspace's WhatsApp by providing credentials the user generated in THEIR OWN Meta app (the 'bring your own credentials' alternative to the browser signup popup). Use this to connect a workspace's WhatsApp number entirely in chat: ask the user for the three values from their Meta app's WhatsApp API setup — a permanent access_token, the phone_number_id, and the waba_id (WhatsApp Business Account id) — then call this tool with them. DripRaven validates the token against Meta and, on success, sends real broadcasts from that number. Returns { connected, status, phone_number, verified_name }. Fails with VALIDATION_ERROR if the credentials are wrong. Note: for credentials from your own Meta app, delivery/read stats won't update (they require webhook wiring in your own app); outbound sending works.
Inputs: waba_id (required), access_token (required), phone_number_id (required).
create_automationAInspect
Automatically send an approved template to every NEW contact with a tag, e.g. a welcome message whenever a lead tagged "new-lead" is added (by add_or_update_contact, import_contacts, the REST API, or a Zapier/Make integration calling it). Only contacts created AFTER the automation qualify, each at most once: re-importing or tagging existing contacts never triggers it. To message existing contacts, use a broadcast; the response's existing_tagged_contacts says how many already have the tag. Only add contacts who agreed to receive WhatsApp messages. The template must be APPROVED with every {{n}} placeholder mapped (set_template_variables). One automation per tag. delay_minutes (0 to 10080) waits before sending. Returns the automation with live stats and any warnings (e.g. no WhatsApp number connected) that would make sends fail.
Inputs: template_id (required), trigger_tag (required), name, delay_minutes.
create_segmentAInspect
Create a named reusable segment from combined filters (tags + country + custom field + signup date range). Segments are live — they always reflect current contacts. Returns { segment_id, contact_count }.
Inputs: name (required), filter (required).
create_templateAInspect
Create a new WhatsApp message template on the connected WhatsApp Business Account. Placeholders in body/header/URL use positional {{1}}, {{2}} … syntax. IMPORTANT — personalisation: for EVERY body placeholder you MUST set variable_mapping so it fills with each contact's real data at send time. Map {{1}} to a contact field: { "1": "name" } fills {{1}} with the contact's name; { "1": "name", "2": "fields.plan_tier" } maps a custom field. Without a mapping the placeholder sends as a blank space to everyone — NOT the sample value. body_examples is a SEPARATE thing: one sample value per placeholder (e.g. a name like Alex) used ONLY to satisfy Meta's approval review; it is never sent to a contact. Meta REQUIRES body_examples when the body has placeholders, so supply BOTH body_examples (for approval) and variable_mapping (for real personalisation). name must be lowercase letters, numbers and underscores. category is MARKETING, UTILITY, or AUTHENTICATION. New templates start PENDING Meta review — only APPROVED templates can be broadcast (poll with sync_templates / list_templates). VIDEO HEADER: pass header_video_url with a public link to an .mp4 to attach/embed a video at the top of the message; it is uploaded to WhatsApp for approval and re-sent with every broadcast. A template has ONE header, so set header_text OR header_video_url, not both. Returns the stored template row (or { id, status }).
Inputs: body (required), name (required), category (required), buttons, +6 more.
delete_automationADestructiveInspect
Delete an automation so it stops sending. Messages already sent are not affected. To pause it temporarily instead, use update_automation with enabled: false.
Inputs: automation_id (required).
delete_templateADestructiveIdempotentInspect
Permanently delete a message template from the connected WhatsApp Business Account and from DripRaven. This removes ALL languages of that template name and cannot be undone; confirm with the user before calling. Returns nothing on success.
Inputs: template_id (required).
disconnect_whatsappADestructiveIdempotentInspect
Disconnect this workspace's WhatsApp number. After this, broadcasts are NOT delivered to real phones until a number is reconnected. Use this when the user wants to stop sending from their connected number or to re-run the signup with a different number. Synced templates and contacts are kept and re-sync on reconnect. The workspace can reconnect anytime via connect_whatsapp (own credentials) or whatsapp_connect_link (hosted signup). Confirm with the user before calling. Returns { connected: false, disconnected }.
Inputs: no named parameters.
get_campaign_statsARead-onlyIdempotentInspect
Get live delivery stats for a campaign: { sent, delivered, read, failed, delivery_rate, read_rate, status }. Updates in real time as Meta delivery webhooks arrive. When sends have failed, also includes recent_errors: up to 5 recent distinct failure reasons, covering both send-time API errors and post-send delivery failures reported by Meta (prefixed with the Meta error code, e.g. 'Meta error 131049: ...'). Always relay recent_errors to the user when failed > 0; if it is absent, say the reason is not known yet rather than guessing.
Inputs: campaign_id (required).
get_phone_verification_codeARead-onlyInspect
Read the WhatsApp verification code Meta sent to a number this workspace rents. Only works for rented numbers — a number the user owns delivers the code to their own phone. Call this during the Meta signup, once the user requested the code for the rented number by Phone call (always the call, never SMS). The code is also emailed to the workspace owner about a minute after the call. Returns { code, code_received_at, messages, instructions }; code is null when nothing has arrived yet, in which case wait for the user to request it and call again rather than retrying in a tight loop. messages holds the raw texts so you can read one out verbatim if the code could not be parsed (voice transcripts especially). Codes expire within minutes.
Inputs: phone_number.
get_startedARead-onlyIdempotentInspect
Check whether this workspace is set up to send real broadcasts, and what is still missing. Returns { about, ready, checklist, summary, warnings }. warnings lists problems that do not block scheduling but will make every send fail (e.g. Meta locked the WhatsApp Business Account); always relay them. Each checklist item has { key, label, done, blocking, next_tool, instructions }. Call this FIRST whenever a user asks to send or schedule a campaign on a new or unfamiliar workspace, and when a user asks to get started or set up: if ready is false, do NOT attempt send_broadcast (it would fail or, worse, not be delivered) — instead walk the user through each not-done blocking step using its next_tool and instructions (connect WhatsApp, get a template approved, add contacts, subscribe), then proceed once ready. Also call it when the user greets you, asks what DripRaven is or what you can do, or has just connected DripRaven: about says how to introduce it.
Inputs: no named parameters.
get_subscribe_linkARead-onlyInspect
Get the link the user opens to subscribe (or upgrade) so broadcasts can be sent. By default (no plan) returns { subscribe_url, plans, instructions } where subscribe_url is the DripRaven plans page — the pricing table where the user compares every tier and picks the one they want. Prefer this: hand the user subscribe_url rather than choosing a plan for them. Only pass plan when the user has already told you which tier they want (starter, growth, or scale); that additionally returns checkout_url, a direct one-click Stripe Checkout link for that plan (no DripRaven login needed). Either way the subscription activates automatically right after payment, then retry send_broadcast. billing_status also returns the same plans list if you want to describe tiers and prices in chat.
Inputs: plan.
import_contactsAInspect
Bulk import contacts from a CSV string. Required columns: "phone", "name". Any additional columns become custom fields. Optional tag is applied to all imported contacts. If the tag matches an enabled automation (list_automations), each NEWLY created contact is queued for that automation's message; existing contacts are not. Returns { total, created, updated, failed, errors, automations_queued }.
Inputs: csv_data (required), tag, source.
list_automationsARead-onlyIdempotentInspect
List the workspace's automations with their trigger tag, template, delay, enabled flag and live stats { sent, delivered, read, failed, delivery_rate, read_rate }. When sends failed, stats.recent_errors gives up to 5 recent reasons.
Inputs: no named parameters.
list_campaignsARead-onlyIdempotentInspect
List broadcast campaigns, most recent first. Optionally filter by status (draft / scheduled / sending / done / failed / cancelled). Paginated: pass the returned next_cursor to fetch the next page. Each campaign includes its id — use that with get_campaign_stats. Returns { data: campaigns[], next_cursor, has_more }.
Inputs: limit, cursor, status.
list_contactsARead-onlyIdempotentInspect
List contacts, most recent first. Optionally filter by tag, country (ISO-2 custom field), opt-out status, or an exact phone (E.164) to look up a single contact. Paginated: pass the returned next_cursor to fetch the next page. Returns { data: contacts[], next_cursor, has_more }.
Inputs: tag, limit, phone, cursor, +2 more.
list_phone_numbersARead-onlyIdempotentInspect
List the phone numbers this workspace rents from DripRaven, with the status of each: pending_payment (reserved, the user has not paid yet), active (ours, ready to register with WhatsApp), provision_failed (paid but the number could not be bought — billing was stopped, see last_error), released. Use it to check whether a purchase has completed after the user says they paid, and to find the number to use in the WhatsApp signup.
Inputs: no named parameters.
list_segmentsARead-onlyIdempotentInspect
List all saved segments in this workspace, each with its live contact_count. Use this to find an existing segment's id to pass to preview_broadcast or send_broadcast, rather than recreating a segment you already made. Segments always evaluate live, so contact_count reflects current contacts. Returns an array of { id, name, filter, contact_count }.
Inputs: no named parameters.
list_templatesARead-onlyIdempotentInspect
List all WhatsApp message templates synced from Meta, including approval status (APPROVED / PENDING / REJECTED). Only APPROVED templates can be broadcast.
Inputs: no named parameters.
preview_broadcastARead-onlyIdempotentInspect
Render exactly what a broadcast would send, using real contacts from the segment, BEFORE you send it. Call this before send_broadcast and show the user the result so they can confirm the personalisation is right (this is how you catch a template that says "Hi Alex" instead of the contact's real name). Returns { template, segment, contact_count, variables (each placeholder → the contact field it maps to, or null if unmapped), unmapped_placeholders, previews (per-contact rendered message), warnings }. If unmapped_placeholders is non-empty or a preview shows a blank/wrong value, fix the mapping with set_template_variables and preview again before sending.
Inputs: segment_id (required), template_id (required), limit.
release_phone_numberADestructiveIdempotentInspect
Give a rented phone number back and stop billing for it immediately. Use this when the user no longer wants the number, or when WhatsApp would not accept it. Confirm with the user before calling: the number is released for good, and if it is the number their WhatsApp is connected on, that connection stops working and they would have to register a different number. Returns { phone_number, released, instructions }.
Inputs: phone_number (required).
search_phone_numbersARead-onlyIdempotentInspect
Find phone numbers the user can rent from DripRaven to register with WhatsApp. Use this when the user says they do NOT have a spare phone number for the WhatsApp signup (the number Meta registers cannot already be on WhatsApp). Returns { numbers, monthly_price_cents, purchasable, instructions } — each number has its country and locality. Nothing is reserved or charged here. Show the user the options and the monthly price and let THEM pick; then call buy_phone_number with their choice. If the user does have a number of their own, use that instead — it is cheaper and more reliable than renting.
Inputs: country (required), limit, contains, area_code, +1 more.
send_broadcastADestructiveInspect
Send or schedule a broadcast: one approved template to every contact in a segment. Omit scheduled_at to send immediately. Validates the template is APPROVED and that every body placeholder is mapped to a contact field — a template with any unmapped placeholder is REJECTED with TEMPLATE_VARIABLES_UNMAPPED (the error's meta.unmapped_placeholders lists which). If you hit that, map them with set_template_variables, then retry. Call preview_broadcast FIRST to show the user the rendered message and catch this before sending. Returns { campaign_id, contact_count, scheduled_at } — use campaign_id with get_campaign_stats. If the response has warnings, relay each one to the user: a warning about the WhatsApp Business Account (locked, unpaid, restricted) means the schedule stands but sends will fail until the user fixes it in WhatsApp Manager. For a new or unfamiliar workspace, call get_started FIRST and complete any missing setup steps before scheduling — otherwise the broadcast will not be delivered. On failure the error's meta field explains the fix: CHANNEL_NOT_CONNECTED means no WhatsApp number is connected (use whatsapp_connect_link); SUBSCRIPTION_REQUIRED or MONTHLY_LIMIT_REACHED means no active plan (use get_subscribe_link). Give the user the link, then retry.
Inputs: segment_id (required), template_id (required), scheduled_at, timezone_mode.
send_feedbackAInspect
Pass a message from the user to the DripRaven team, who read every one. Offer this when the user wants something DripRaven cannot do yet, hits a problem you cannot solve, or says what they like or dislike about it; only call it once the user has agreed to send it. Write the message in the user's own words, as they would want the team to read it. Leave out their contacts' names, phone numbers and message text unless the user asks to include them. Returns { received: true }.
Inputs: message (required), category.
set_template_variablesAIdempotentInspect
Wire an existing template's {{1}}, {{2}} … placeholders to contact fields so broadcasts personalise. This is the fix when a message went out with a blank or wrong value (e.g. it said "Hi Alex" to a contact named Josef): that means the placeholder was never mapped. variable_mapping REPLACES the whole mapping — pass an entry for every placeholder, e.g. { "1": "name", "2": "fields.plan_tier" }. Values are a top-level contact field (name) or fields. for a custom field. Does not re-submit the template to Meta (content is unchanged), so no re-approval is needed. Use preview_broadcast afterwards to confirm the rendered message. Returns the updated template row.
Inputs: template_id (required), variable_mapping (required).
sync_templatesAIdempotentInspect
Pull the latest message templates (and their approval status) from the connected WhatsApp Business Account into DripRaven. Runs automatically on connect, but call this to refresh after creating or getting a template approved in WhatsApp Manager. Returns { synced }. Then use list_templates to see them.
Inputs: no named parameters.
update_automationAIdempotentInspect
Change an automation: pause or resume it (enabled), switch its template, trigger tag, delay or name. Pass only the fields to change. Contacts who already received it are not messaged again, even with a new template.
Inputs: automation_id (required), name, enabled, template_id, +2 more.
update_templateAIdempotentInspect
Edit an existing template's category and/or content (body, header, footer, buttons). Meta only allows editing templates that are APPROVED, REJECTED, or PAUSED (not PENDING); approved templates are limited to a few edits per day. name and language cannot be changed. Same placeholder/example rules as create_template. Pass header_video_url to attach/replace a video header, or header_text to switch to (or keep) a text header — one header only, so not both. After editing, the template re-enters review. Returns the updated template row.
Inputs: template_id (required), body, buttons, category, +4 more.
whatsapp_connect_linkARead-onlyIdempotentInspect
Get the link the user opens to connect their WhatsApp number so broadcasts reach real phones. Two steps, because connecting registers a phone number with Meta and that number must NOT already be in use with WhatsApp: call this tool first with no arguments — it returns no link, only confirmation_question — ask the user that question and wait for their reply; then, once they confirm they have such a number, call it again with phone_number_confirmed: true to get connect_url. Returns { connect_url, connected, configured, phone_number, phone_number_confirmation_required, confirmation_question, instructions }; connect_url is null until confirmed. Connecting then requires a one-time Facebook login in the browser (a Meta requirement the agent cannot do for them) — surface connect_url to the user and ask them to finish it there. Everything after that (token exchange, number registration) is automatic. If connected is already true, the workspace is live and no action is needed.
Inputs: phone_number_confirmed.
whatsapp_statusARead-onlyIdempotentInspect
Check whether this workspace has a connected WhatsApp number. Returns { connected, status, phone_number, verified_name, configured, health }. When connected is false, broadcasts are a preview and are NOT delivered to real phones. health.ok false means Meta reported an account-level problem (e.g. business account locked, no payment method, number restricted): the number is connected but every send will fail; read health.message and health.remediation to the user and do not resend until it is fixed. Call this before send_broadcast if the user expects real delivery; if not connected, use whatsapp_connect_link, which first has you confirm the user has a spare phone number not already on WhatsApp and then returns the link that connects their number.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
WhatsApp Business inbox for AI apps: read and answer chats, run campaigns, deploy automations.
WhatsApp CRM: inbox, contacts, deals, campaigns, AI agents, automations, ads and reports.
Send WhatsApp messages and templates, manage chats, contacts, broadcasts and AI agents.
WhatsApp CRM on the official Meta API: inbox, contacts, deals, campaigns, automations, AI agents.
Related MCP Servers
- AlicenseBqualityCmaintenanceEnables AI assistants to manage WhatsApp business operations including chatbots, broadcasts, campaigns, and contacts through 120+ MCP tools.10046 npmMIT
- AlicenseAqualityDmaintenanceConnects AI assistants to the official Meta WhatsApp Cloud API for managing conversations and sending various message types through natural language. It provides tools for media management, template messages, and real-time webhook processing without the risk of account bans.1827MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI assistants to interact with WhatsApp by sending messages, triaging urgent conversations, scheduling messages, and managing automated replies with safety controls and human approval.-

ChatDesq MCP Serverofficial
AlicenseBqualityBmaintenanceConnects Claude, Cursor and other AI assistants to a WhatsApp Business API workspace so they can search contacts and tags, read inbox conversations, check template approval and message delivery status, review broadcast and CRM deal data, and send single opt-in messages or create contacts and deals. Bulk broadcasts, drips and deletes are deliberately excluded, keeping assistants limited to safe, individual actions.17245 npmMIT
Glama MCP Gateway
Add one secure layer between your agents and this server.