Clickatell MCP. Send SMS, Track Status, Manage Global Messaging Workflows
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Clickatell manages your global SMS communication directly through any agent. Use this server to send single or bulk messages, track delivery status down to the carrier level, check API account balances, and manage complex inbound reply rules—all without switching apps.
It lets you build two-way messaging flows using natural conversation.
What your AI agents can do
Cancel queued message
Irrevocably deletes scheduled SMS blocks that haven't been sent yet.
Dispatch bulk sms
Sends multiple SMS messages at once, optimizing the sending process for bandwidth and speed.
Dispatch sms message
Sends a single outbound SMS message using a structured JSON payload over Clickatell.
Sends single or large batches of SMS messages using E.164 formatting.
Retrieves the final carrier status for a message ID, confirming physical delivery progress.
Provides real-time visibility into your API funding limits and account balance.
Identifies active, scheduled text blasts set up within the platform.
Creates, reads, and deletes keyword-based auto-reply rules (webhooks) for two-way conversations.
Ask AI about this MCP
Supported MCP Clients
Waiting for input…
Clickatell MCP Server: 10 Tools for Global Messaging
Manage all aspects of mobile communication—from sending single texts to setting up complex inbound reply rules and checking API balances.
019d7572cancel queued message
Irrevocably deletes scheduled SMS blocks that haven't been sent yet.
019d7572dispatch bulk sms
Sends multiple SMS messages at once, optimizing the sending process for bandwidth and speed.
019d7572dispatch sms message
Sends a single outbound SMS message using a structured JSON payload over Clickatell.
019d7572get account balance
Retrieves your current API balance and funding limits for the account.
019d7572get delivery status
Checks a message ID to determine its final carrier delivery status.
019d7572list inbound rules
Lists all current keyword-based rules that process incoming messages.
019d7572list scheduled campaigns
Shows a list of planned bulk messaging campaigns and their delivery windows.
019d7572test carrier coverage
Runs an automated check to see if SMS can be routed successfully to a specific phone number (MSISDN).
019d7572upsert inbound rule
Creates or updates a keyword-based reply rule, including setting up necessary webhooks.
019d7572wipe inbound rule
Deletes an existing inbound messaging rule that is no longer needed.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Clickatell, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You gotta connect your Clickatell account straight into any agent, and you get full control over global SMS messaging right through plain conversation. You don't have to jump between apps just to run a basic campaign.
When you need to send messages, the dispatch_sms_message tool lets you fire off a single outbound text using a structured JSON payload. If you got a big batch of texts ready to go, use dispatch_bulk_sms; that function sends multiple SMS messages at once, optimizing the whole sending process for speed and bandwidth.
You'll also find cancel_queued_message lets you irrevocably delete scheduled blocks of SMS before they even hit the air.
To keep your communication reliable, you use get_delivery_status to check a message ID; this tells you the final carrier delivery status, confirming if the text actually got through to the cell tower. Before launching anything new, run test_carrier_coverage. This automated check confirms whether SMS can successfully route to any specific phone number (MSISDN) in your target area.
You'll also see that Clickatell handles all of this using E.164 formatting for every message sent.
For managing money, you simply call get_account_balance to retrieve the current API balance and check your account funding limits. On the automation side—for handling two-way conversations—you've got full control over inbound reply rules. Use list_inbound_rules to see every existing keyword-based rule that processes messages coming in. If you need a new auto-reply flow, use upsert_inbound_rule; this tool either creates or updates the keyword rule and sets up any necessary webhooks.
And if a rule is dead weight, you can wipe it clean using wipe_inbound_rule.
When planning campaigns, you don't have to guess what's scheduled; run list_scheduled_campaigns to see all planned text blasts and their specific delivery windows. These tools let your agent manage everything—from sending the first word of a message to setting up complex reply logic for weeks down the line—without ever needing manual intervention or switching screens.
How Clickatell MCP Works
- 1 Subscribe to the server and paste your Clickatell API Key into the agent setup.
- 2 Reference a function by name, like
get_account_balance, or describe the action: 'Send an SMS blast of 50 numbers.' - 3 The agent executes the tool call via the MCP standard and returns the structured data (e.g., status codes, message IDs) to you.
The bottom line is that your AI client treats Clickatell's entire messaging API like a natural conversation thread.
Who Is Clickatell MCP For?
This is for the Operations Manager who needs constant visibility into global message failures, or the Marketing Specialist dealing with campaign timing. You shouldn't have to jump between your CRM, the carrier portal, and your messaging tool just to confirm one text actually landed.
Checks the get_delivery_status for a customer’s message ID when they complain about non-receipt.
Uses list_scheduled_campaigns to audit upcoming blasts and ensures compliance with campaign limits.
Manages inbound logic by calling upsert_inbound_rule to test new keyword triggers before deployment.
What Changes When You Connect
- Confirm Delivery: Stop guessing if a message went through. Use
get_delivery_statusto confirm the carrier status for any message ID. - Manage Costs: Don't run out of credits mid-campaign. Call
get_account_balanceanytime to check your real-time funding limits and available credit. - Automate Replies: Set up two-way conversations easily. Use
upsert_inbound_ruleto define what happens when a customer replies with a specific keyword. - Scale Sending: Need to blast 1,000 people? Instead of using the single send tool repeatedly, use
dispatch_bulk_smsfor efficient high-volume sends. - Audit Campaigns: Before launching a major push, run
list_scheduled_campaignsto see exactly what's already queued up and when it runs.
Real-World Use Cases
Customer Complaint: 'Did my order update text get lost?'
The customer support agent asks the agent to get_delivery_status using the message ID. The agent confirms if the status is 'Delivered to Gateway' or if it failed earlier in the chain, solving the complaint instantly.
Marketing Prep: Launching a new localized campaign.
The marketing team first uses test_carrier_coverage for the target region. Then, they use list_scheduled_campaigns to ensure no existing blast conflicts with the new launch window before calling dispatch_bulk_sms.
Developer Testing: Setting up automated support flow.
The developer calls upsert_inbound_rule to create a rule for the keyword 'HELP'. They then test it by sending a message, confirming the webhook triggers and updates the desired system record.
Cleanup: A scheduled blast was accidentally sent.
The operations manager uses list_scheduled_campaigns to find the ID of the misfired campaign. They immediately call cancel_queued_message, stopping the message before it ever hits the carrier network.
The Tradeoffs
Using single dispatch for mass outreach
Calling dispatch_sms_message 50 times in a row to send updates to 50 clients. This is slow, inefficient, and risks API rate limiting.
→
Instead, use the dedicated batch function: dispatch_bulk_sms. This tool is designed for optimizing high-volume sending across multiple recipients.
Assuming delivery means receipt
Thinking that because you sent a message via your app, it automatically reached the customer's phone. The system needs confirmation.
→
Always check get_delivery_status. This tool verifies if the message passed through all necessary carrier nodes and was handed off for final delivery.
Manually deleting rules via dashboard
Logging into the web portal just to disable a keyword rule because it's outdated. This is slow and doesn't create an audit log.
→
Use wipe_inbound_rule directly from your agent conversation. It deletes the mapped HTTP logic, keeping everything within your workflow history.
When It Fits, When It Doesn't
Use this server if your core requirement is managing SMS messaging and its operational status across multiple global carriers. The strength here is visibility: you can send (dispatch_sms_message), manage complexity (rules via upsert_inbound_rule), and confirm success/failure (get_delivery_status).
Don't use this if your primary communication method is email, WhatsApp, or anything outside of SMS. For those channels, you need a dedicated connector for that specific service type.
If you only need to send messages but never care about status, then dispatch_sms_message works, but you lose the critical safety net provided by get_delivery_status. Only use this when knowing where and why a message failed is as important as sending it.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Clickatell. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 10 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Tracking SMS Delivery Status Shouldn't Require Logging into Three Different Portals
Today, if you send an important notification, checking its status means logging into your primary messaging dashboard, then potentially logging into the carrier portal to see if it passed the network nodes, and finally cross-referencing a separate spreadsheet for compliance. It's slow, messy, and prone to human error.
With this MCP server, you just tell your agent: 'What is the status of msg_abc123?' The agent runs `get_delivery_status` and immediately gives you the final carrier hand-off point. You get the answer without leaving the chat window.
Clickatell MCP Server: Send Messages, Track Status, Manage Global Messaging Workflows
Manual campaign management means listing scheduled blasts in one UI, then having to jump into another system to check the actual delivery counts for that blast. It's a multi-step audit process.
Now, you can ask your agent to run `list_scheduled_campaigns` and get an immediate overview of all active arrays and their planned timings. Everything is centralized and actionable.
Common Questions About Clickatell MCP
How do I check if a message was successfully sent using dispatch_sms_message? +
You must use get_delivery_status after the send attempt. The status will show if the message passed through Clickatell nodes and was handed off to the local carrier for final delivery.
What is the difference between dispatch_bulk_sms and dispatch_sms_message? +
dispatch_bulk_sms handles sending many messages at once, optimizing throughput. Use this when you have a list of recipients; use dispatch_sms_message for single-target communications.
How do I set up a reply rule using upsert_inbound_rule? +
You call upsert_inbound_rule, specifying the keyword and the desired action. The tool handles creating or updating the structural parsing block, managing webhooks automatically.
Can I cancel a scheduled SMS using list_scheduled_campaigns? +
No. While list_scheduled_campaigns lets you see what's coming up, you must use the dedicated tool, cancel_queued_message, to stop a blast that hasn't been sent yet.
How do I check my current funding limits using the get_account_balance tool? +
The get_account_balance tool retrieves your active API metrics. It shows your total available credit and, crucially, estimates how many domestic SMS messages that balance supports based on recent usage patterns.
Should I use test_carrier_coverage before sending an important message? +
Yes, running test_carrier_coverage validates the MSISDN routes automatically. This step confirms if a specific destination number is reachable by the network before you send the actual message, preventing failed dispatches.
If I need to delete an inbound rule entirely, what should I use? Is it wipe_inbound_rule? +
wipe_inbound_rule completely removes mapped HTTP logic bounds. This is the proper way to clear a structure and avoid leaving behind any legacy routing rules that might interfere with future processes.
What does get_delivery_status tell me if my message fails? Does it just say 'Failed'? +
The get_delivery_status tool performs structural extraction of the properties driving the final carrier status. It doesn't just report failure; it pinpoints exactly where in the network—which nodes or carriers—the message stopped processing.
Can my agent confirm if an international number is reachable via Clickatell? +
Yes. Use the 'test_carrier_coverage' tool. Provide the destination number in international format, and the agent will check Clickatell's network traces to confirm if the route is active and supported.
How do I monitor my remaining SMS credits through the agent? +
Ask your agent to get the account balance. It retrieves the explicit funding limits from your Clickatell profile, helping you prevent zero-balance halts during critical messaging flows.
Can I automate replies based on incoming keywords? +
Absolutely. You can use the 'upsert_inbound_rule' tool to define keyword triggers and webhook URLs. This allows your agent to configure automated two-way communication schemas without manually editing portal settings.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
Telegram Bot Alternative
Control and manage your Telegram bots — send messages, photos, and audit chats via AI.
Discord Bot
Control and manage your Discord bots — audit guilds, channels, and messages via AI.
WhatsApp Business Alternative
Automate your customer communication — send templates and manage profiles via AI.
You might also like
Bookeo
Manage bookings, customers, products, payments, and availability for your Bookeo-powered fitness or activity business through natural conversation.
PDF.co
Parse, generate, merge, and convert PDF documents programmatically with an API that handles complex document processing tasks.
All Digital Rewards
Incentive and reward orchestration — manage participants, points, and catalogs via AI.