SendKuy MCP server
OfficialSendKuy MCP server lets AI assistants send and manage WhatsApp, SMS, and email through a SendKuy account.
Read account details: plan, credits, usage, rate limit, and API key scopes.
Send one message to up to 100 recipients or a contact group on WhatsApp, SMS, or email.
Send a batch of up to 500 individualized messages with per-row results.
Check message statuses, list recent messages by filters, and cancel unsent messages.
Send OTP verification codes and check codes users enter.
Check whether phone numbers are registered on WhatsApp.
Find contacts, list templates, and list contact groups.
List, start, inspect, pause, resume, or cancel campaigns.
Inspect webhook delivery attempts and failures.
Enables sending WhatsApp messages and campaigns through a SendKuy account, checking which phone numbers are on WhatsApp, and managing message delivery and campaign status.
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., "@SendKuy MCP server send a test OTP to +1 555 123 4567 via WhatsApp"
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.
SendKuy MCP server
Give AI assistants and agents a way to reach people: send WhatsApp, SMS and email, verify OTP codes and run campaigns through your SendKuy account.
Use it while you build an integration ("send a test OTP to my number", "why is my webhook failing?"), or as the notification step of an agent that runs on its own: an on-call alert, a daily revenue summary, an order update per customer.
Full guide with scenarios: docs.sendkuy.com/mcp
Get a key
Create an API key at app.sendkuy.com/user/api. Give it account:read plus the scopes of the tools you want, and nothing more. The server lists only the tools your key can use, so a key with read scopes never sees a tool that sends.
Related MCP server: SendAPI MCP Server
Install
Claude Code:
claude mcp add --transport stdio --env SENDKUY_API_KEY=sk_live_YOUR_API_KEY sendkuy -- npx -y @sendkuy/mcpCursor (.cursor/mcp.json), Windsurf and Claude Desktop:
{
"mcpServers": {
"sendkuy": {
"command": "npx",
"args": ["-y", "@sendkuy/mcp"],
"env": { "SENDKUY_API_KEY": "sk_live_YOUR_API_KEY" }
}
}
}VS Code (.vscode/mcp.json):
{
"inputs": [
{
"type": "promptString",
"id": "sendkuy-key",
"description": "SendKuy API key",
"password": true
}
],
"servers": {
"sendkuy": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@sendkuy/mcp"],
"env": { "SENDKUY_API_KEY": "${input:sendkuy-key}" }
}
}
}Claude Desktop can also install sendkuy-mcp.mcpb from the latest release with one click.
Tools
Tool | What it does | Scopes |
| Plan, credits per channel, usage this period, the key's scopes |
|
| One body to 1–100 recipients, contacts or a group, on one channel |
|
| Up to 500 messages with different content, answered row by row |
|
| Status of up to 20 messages by id |
|
| Recent messages by channel, status and time |
|
| Cancel a message not sent yet |
|
| Send an OTP code |
|
| Check the code a user typed |
|
| Which numbers are on WhatsApp |
|
| A contact by phone or |
|
| Saved message templates |
|
| Contact groups and their size |
|
| Campaigns prepared in the dashboard |
|
| Start a campaign |
|
| Progress and delivery stats |
|
| Pause, resume or cancel |
|
| Webhooks and their latest delivery attempts |
|
Tools that send really send and spend credit. They take an optional dedupe_key: an agent that repeats a step with the same key gets the first answer back instead of sending twice.
Examples
On-call alert. "When the health check fails, WhatsApp the on-call group with the service name and the error." The agent sends to the group's
grp_id withdedupe_keyset to the incident id.Daily revenue summary. "Every evening, send each branch manager their own numbers." One
sendkuy_send_batchcall, a different body per manager.Debugging an integration. "Which WhatsApp messages failed in the last hour, and why?"
sendkuy_list_messages, thensendkuy_list_webhook_deliveries.
Configuration
Variable | |
| Your API key. Without it, or when the key is invalid or SendKuy can't be reached at start-up, the server still starts and lists its tools, and every call answers with the reason until you fix it and restart the client. |
| Only for a proxy or a mock server in tests. Defaults to |
License
MIT
Available Tools
17 toolssendkuy_cancel_messageCancel a messageAIdempotent
Cancel a message that has not been sent yet, such as a scheduled one or one still queued in a batch. A message already handed to the provider cannot be called back.
Inputs: id (required). Returns: message
sendkuy_check_verificationCheck an OTP codeA
Check the code a user typed against a verification from sendkuy_send_verification. status approved means the code was right. A wrong code answers verification_code_invalid and uses up one of checks_remaining.
Inputs: id (required), code (required). Returns: verification
sendkuy_check_whatsapp_numbersCheck WhatsApp numbersARead-onlyIdempotent
Check whether up to 50 phone numbers are registered on WhatsApp before you send to them. Numbers must be E.164 with the leading +; a local number without the country code comes back registered: null. Limited to 10 calls a minute per key.
Inputs: numbers (required), gateway_id. Returns: numbers
sendkuy_control_campaignPause, resume or cancel a campaignBIdempotent
Pause a running campaign, resume a paused one, or cancel it for good. Pause is the emergency brake when a campaign is going out wrong: messages not yet sent stay unsent until you resume. Cancel cannot be undone.
Inputs: id (required), action (required). Returns: campaign
sendkuy_find_contactsFind a contactARead-onlyIdempotent
Find one saved contact by phone number (E.164) or by external_id, the id your own system gave the customer. Returns contact: null when nobody matches. Use the contact id (con_...) as a recipient in sendkuy_send_message.
Inputs: phone, external_id. Returns: contact
sendkuy_get_accountGet SendKuy accountARead-onlyIdempotent
Read the SendKuy account behind this API key: plan, remaining credits per channel (WhatsApp, SMS, email), messages used this billing period, the rate limit, and the scopes this key holds. Check credits before a large send. plan, credits and usage are null for SendKuy staff keys.
Inputs: no named parameters. Returns: name, plan, type, email, +4 more
sendkuy_get_campaignGet campaign progressARead-onlyIdempotent
Read a campaign: status, progress (processed_contacts of total_contacts), why it is paused, and delivery stats (sent, delivered, failed, opened, replied, unsubscribed) overall and per channel.
Inputs: id (required). Returns: stats, campaign
sendkuy_get_messagesGet message statusARead-onlyIdempotent
Read the current status of 1 to 20 messages by id (msg_...): queued, scheduled, sending, sent, delivered, read, failed, cancelled and so on, with the error when one failed. Use it after a send to confirm delivery, or to find out why a message failed.
Inputs: ids (required). Returns: messages
sendkuy_list_campaignsList campaignsARead-onlyIdempotent
List campaigns, newest first, with their status and audience size (total_contacts). Campaign content is written in the SendKuy dashboard; a draft found here is ready to run with sendkuy_start_campaign.
Inputs: limit, cursor. Returns: has_more, campaigns, next_cursor
sendkuy_list_groupsList contact groupsARead-onlyIdempotent
List the contact groups in SendKuy with how many contacts each holds. Put a group id (grp_...) in the to field of sendkuy_send_message to send to every member; check contact_count first, because every member is charged.
Inputs: limit, cursor. Returns: groups, has_more, next_cursor
sendkuy_list_messagesList recent messagesARead-onlyIdempotent
List recent messages, newest first, filtered by channel, status and creation time. Use it to answer "which WhatsApp messages failed in the last hour?" while debugging an integration. To check specific messages, use sendkuy_get_messages.
Inputs: limit, cursor, status, channel, +2 more. Returns: has_more, messages, next_cursor
sendkuy_list_templatesList message templatesARead-onlyIdempotent
List the message templates saved in SendKuy, with their channel, subject and body. Variables in a body are written as placeholders the template fills in. Pass a WhatsApp template id as template_id to sendkuy_send_message.
Inputs: limit, cursor. Returns: has_more, templates, next_cursor
sendkuy_list_webhook_deliveriesList webhook deliveriesARead-onlyIdempotent
Show the webhooks on this account and their latest delivery attempts: the HTTP status your endpoint answered, the error, an excerpt of the response, and when the next retry is due. Use it to answer "why is my webhook failing?". Without webhook_id it reads the first five webhooks.
Inputs: limit, webhook_id. Returns: webhooks
sendkuy_send_batchSend a batch of messagesA
Send up to 500 independent messages in one call, each with its own channel, recipient and body. Use it when the content differs per recipient: a revenue summary per branch, a notification per order, a reminder per invoice. Every row is answered on its own: one bad number or a channel out of credit fails that row only, and the rest still go out. The answer lists the message id of every row in input order (null where the row failed) and each failed row with its error. Messages are queued and sent in the background, paced per number. This really sends and spends SendKuy credit. A recipient on the suppression list or who unsubscribed still gets a message id and fails later; read the final status with sendkuy_get_messages. Pass dedupe_key so a retried step does not send the batch twice.
Inputs: messages (required), dedupe_key. Returns: ids, failed, accepted, failures
sendkuy_send_messageSend a messageA
Send one message body to 1 to 100 recipients on one channel: WhatsApp, SMS or email. Use it for an alert, a summary or a one-off notification where everyone gets the same text. To reach a saved contact group, put its grp_ id in to. When each recipient needs different content (a summary per branch, a notification per order) use sendkuy_send_batch. A campaign prepared in the SendKuy dashboard is started with sendkuy_start_campaign and can be paused or cancelled midway. Phone numbers must be E.164 with the leading + (for example +6281234567890). This really sends and spends SendKuy credit. A recipient on the suppression list or who unsubscribed still gets a message id and fails later; read the final status with sendkuy_get_messages. One recipient is sent while you wait; several are queued and sent in the background, paced per number. Pass dedupe_key so a retried step does not send twice. The answer counts every message per status and lists the first 20; read the rest with sendkuy_list_messages.
Inputs: to (required), body (required), channel (required), media, +7 more. Returns: count, messages, by_status, truncated
sendkuy_send_verificationSend an OTP codeA
Send a one-time code to a phone number or email address and get a verification id (vrf_...). SendKuy generates the code, sends it, and falls back through the channels you list in order. Check what the user typed with sendkuy_check_verification. This really sends and spends SendKuy credit. Pass dedupe_key so a retried step does not send a second code.
Inputs: to, ttl, brand, email, +4 more. Returns: verification
sendkuy_start_campaignStart a campaignAIdempotent
Start a draft or scheduled campaign. An instant campaign starts sending to every eligible contact in its group, is refused with insufficient_credits when the balance does not cover them, and spends real SendKuy credit. A scheduled or recurring campaign waits for its time. If a person is in the conversation, tell them the campaign name and total_contacts before you start it. Pause or cancel it with sendkuy_control_campaign.
Inputs: id (required). Returns: campaign
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Every tool targets a distinct resource+action, and the descriptions explicitly cross-reference each other to draw the boundaries (send_message vs send_batch by uniform vs per-recipient content, get_messages vs list_messages by id vs filter, start_campaign vs control_campaign by lifecycle stage). The only surface overlap — sending to a group via send_message's `to` field versus starting a dashboard campaign — is called out in both descriptions, leaving little room for misselection.
All 17 tools use the same `sendkuy_` prefix plus a consistent snake_case verb_noun pattern (send_message, list_messages, get_campaign, control_campaign, check_whatsapp_numbers). No mixed casing or stray verb styles anywhere in the set.
17 tools is on the heavier side of the ideal band, but the surface genuinely spans several sub-domains — messaging, verification, contacts/groups/templates, campaigns, and webhook diagnostics — and each tool maps to a real operation rather than a thin wrapper. Nothing appears redundant enough to remove.
The send/read/cancel lifecycle for messages and full campaign control are well covered, but most supporting resources are read-only: contacts, groups, templates, and webhook subscriptions can only be listed or found, never created or updated, and campaign content must be authored in the dashboard. These are workable gaps for a send-focused agent but leave notable dead ends in the management surface.
Maintenance
Related MCP Connectors
Run WhatsApp Business campaigns from any AI assistant: contacts, segments, and broadcasts.
Build and send email, SMS, and push straight from your AI agent.
Send WhatsApp messages and templates, manage chats, contacts, broadcasts and AI agents.
Communication stack for AI agents: SMS, AI voice calls, phone numbers, and account events.
Related MCP Servers
- 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

SendAPI MCP Serverofficial
AlicenseAqualityDmaintenanceEnables any MCP-compatible AI agent to send WhatsApp messages, SMS, OTP codes, and email through a single REST API.18MIT- AlicenseBqualityCmaintenanceEnables AI assistants to manage WhatsApp business operations including chatbots, broadcasts, campaigns, and contacts through 120+ MCP tools.10046 npmMIT
- 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.-