Clickatell MCP. Manage all SMS sends, tracking, and rules.
Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Clickatell MCP manages your global SMS communications directly from any AI agent connection. Send single or bulk messages, track real-time delivery status, check account balances, and automate two-way inbound replies without touching a dashboard.
What your AI agents can do
Cancel queued message
Permanently deletes a scheduled SMS block that hasn't been sent yet.
Dispatch bulk sms
Sends many SMS messages at once, maximizing throughput for large campaigns.
Dispatch sms message
Sends a single SMS message to one recipient using the required format.
Send single SMS messages or massive batches of texts while respecting complex routing rules.
Get the final status for a message, confirming if it reached the local carrier nodes.
Check your current API balance and validate international network coverage before launching campaigns.
Create and modify keyword triggers so that incoming messages automatically follow a predefined response path.
List campaigns set to run in the future, or cancel scheduled drops immediately.
Ask AI about this MCP
Supported MCP Clients
OAuth 2.0 CompatibleWaiting for input…
Clickatell: 10 Tools for Mobile Messaging
These tools let you manage every aspect of global text messaging. You can dispatch messages, track delivery status, check balances, and automate keyword responses.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Clickatell on Vinkius019d7572cancel queued message
Permanently deletes a scheduled SMS block that hasn't been sent yet.
019d7572dispatch bulk sms
Sends many SMS messages at once, maximizing throughput for large campaigns.
019d7572dispatch sms message
Sends a single SMS message to one recipient using the required format.
019d7572get account balance
Checks your current API funding limit and usage metrics.
019d7572get delivery status
Retrieves the final status of a sent message from carrier nodes.
019d7572list inbound rules
Lists all active keyword-based rules designed to handle incoming messages.
019d7572list scheduled campaigns
Shows all future text blasts that are currently queued up for sending.
019d7572test carrier coverage
Runs a validation check to see if a specific phone number is serviceable in a given location.
019d7572upsert inbound rule
Creates or updates the structural rules that process incoming messages and webhooks.
019d7572wipe inbound rule
Deletes an existing keyword-based rule entirely, stopping its automated response flow.
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,800+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,800+ 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
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.
Dealing with manual campaign tracking is a nightmare.
Today, if your marketing team runs a big text blast, someone has to log into the portal. Then they have to click through several tabs: one for scheduled campaigns, another for delivery logs, and maybe a third just to check the account balance before reporting on success rates. It's a series of clicks, copies, and manual cross-referencing.
With this MCP, you skip the dashboard entirely. You simply prompt your agent—telling it to 'Audit last week’s campaign delivery.' The process runs in the background, aggregating status updates and balance checks for you. All you get is one clear answer: a summary of what happened.
Getting Inbound Messaging Status with Clickatell MCP
Before this, if a customer replied to an automated message, the support rep had to manually check which reply rules were active and what keyword was triggered. This meant checking different sections of the portal just to see if the chat flow was working.
Now, you can manage those flows entirely through your agent. You use `list_inbound_rules` to view everything, then call `upsert_inbound_rule` to tweak or create a new automated response block instantly. It’s immediate control.
What you can do with this MCP connector
You use this connector to manage all aspects of mobile messaging through natural conversation. Instead of logging into a web portal to manually send out blasts or audit message failures, you simply tell your agent what needs doing—whether that's sending one notification or triggering a multi-stage campaign flow.
For instance, if you need to coordinate an automated customer service response (like confirming an order status), the agent handles the entire sequence. It verifies if the number is active and then sends the message. Because your messaging needs often involve coordinating multiple platforms—say, sending an SMS confirmation after updating a record in a separate CRM system—the platform runs everything inside its V8 isolate sandbox with 34+ security rules enforced on every single call.
This means you can build complex automations that span different services using one AI agent connection.
This gives your team full control over outbound campaigns, the ability to manage keyword-based replies for two-way chat, and immediate visibility into account usage without ever needing to leave your main workspace.
019d7572-1699-73b5-8397-d6233d976c4e How Clickatell MCP Works
- 1 Subscribe to this MCP and provide your Clickatell API Key.
- 2 Connect your AI agent (like Claude or Cursor) using that single key. The connection runs through a zero-trust proxy, meaning the keys are only used in transit.
- 3 Tell your agent the task: 'Send SMS to +123...' or 'What is my balance?'. The MCP executes the request and returns the status immediately.
The bottom line is that you manage complex global messaging workflows using natural language prompts, not API calls.
Who Is Clickatell MCP For?
Marketing leads who get frustrated having to copy-paste campaign results from a dashboard into a spreadsheet. Customer support managers tired of manually checking message delivery logs for every customer complaint.
Runs scheduled text blasts and checks the success rate before reporting out on quarterly KPIs.
Sends individual notifications to customers and verifies the status of messages when a user reports non-receipt.
Verifies international carrier coverage for new markets or checks account balances before global rollout.
What Changes When You Connect
- Stop guessing on delivery. Use
get_delivery_statusto confirm if a message passed the gateway and was handed off to the local carrier for final receipt. - Avoid manual balance checks. Run
get_account_balanceanytime to see your current funding limits and estimate remaining messages, keeping campaigns running smoothly. - Scale messaging without coding. Use
dispatch_bulk_smsto run large-scale marketing blasts, or usedispatch_sms_messagefor targeted individual notifications. - Build automated conversations. Manage two-way chat flows by listing rules with
list_inbound_rulesand setting up new ones usingupsert_inbound_rule. - Plan ahead. View future deployments instantly with
list_scheduled_campaigns, or usecancel_queued_messageif a campaign needs to stop short notice.
Real-World Use Cases
The Marketing Team Needs Confirmation
A marketing lead launches a major promotion. They ask the agent to send 50,000 texts. The agent first runs test_carrier_coverage on key regions, verifies the API balance with get_account_balance, then executes dispatch_bulk_sms. This ensures the campaign doesn't fail due to coverage or budget issues.
The Support Agent Handles a Delivery Complaint
A customer claims they never received an alert. The agent uses the message ID and calls get_delivery_status. This immediately tells the support agent if the message was stopped at the gateway or delivered to the local network, speeding up resolution.
The Developer Sets Up Two-Way Chat
A developer wants customers to reply with a keyword. They use list_inbound_rules to see what's active, and then call upsert_inbound_rule to bootstrap the new parsing block for automated replies.
The Operations Manager Stops a Mistake
An urgent product recall requires stopping an email blast scheduled for next week. The manager simply asks the agent, and it uses list_scheduled_campaigns to confirm the run date, then calls cancel_queued_message to vaporize the drops.
The Tradeoffs
Relying on a single send tool
Calling dispatch_sms_message repeatedly for 10,000 recipients. This is slow and hits rate limits quickly.
→
For high volume, always use dispatch_bulk_sms. This function is designed to handle massive arrays of SMS messages efficiently, optimizing the pipeline bandwidth.
Assuming delivery means receipt
Sending a message and assuming it arrived. You might waste credits on failed deliveries.
→
After dispatching, always check the status using get_delivery_status to confirm if the message successfully passed through the Clickatell nodes.
Ignoring inbound rules
Setting up a two-way chat flow but forgetting to map the keywords. The customer replies, and nothing happens.
→
Always list your current rules with list_inbound_rules before setting new ones using upsert_inbound_rule. This prevents conflicting or orphaned automation logic.
When It Fits, When It Doesn't
Use this MCP if your primary need is managing the entire lifecycle of SMS communication: sending, tracking, and handling replies. If you only need to read contact data (like a user database), this isn't enough; you need a separate user management connector. Conversely, don't use this just because you want MMS or rich media links—this MCP focuses on pure SMS payload rendering. If your needs involve complex conversational AI that requires remembering dialogue history over weeks, you might need to chain this messaging MCP with an external memory storage tool in Vinkius to build a complete customer service agent.
Common Questions About Clickatell MCP
How do I check my Clickatell account balance using the get_account_balance tool? +
Run get_account_balance and the agent returns your current API funding limit, usually providing a clear estimate of how many more messages you can send based on recent activity.
Can I stop an SMS campaign scheduled for next month with cancel_queued_message? +
Yes. Use list_scheduled_campaigns to identify the precise run ID, and then invoke cancel_queued_message. This action immediately removes the drop from the queue.
What is the difference between dispatch_sms_message and dispatch_bulk_sms? +
Use dispatch_sms_message for a single, direct notification. Use dispatch_bulk_sms when sending an array of messages to many recipients; it’s optimized for high-volume throughput.
How do I verify if a number can receive texts before running a campaign? +
Run the test_carrier_coverage tool, providing the MSISDN route. This automatically validates the network path and confirms serviceability without wasting credits on bad numbers.
How do I view all existing automated reply flows using list_inbound_rules? +
It lists every attached structured rule traversing your messaging boundaries. This shows you which keywords or webhooks are currently set up to automatically respond to inbound messages.
What happens if I use wipe_inbound_rule on an existing flow? +
Wiping the rule completely removes it from your account, avoiding any legacy routing. Remember, this action is irreversible; you'll have to rebuild the logic and webhooks manually.
How does dispatch_bulk_sms handle high message volume? +
It optimizes the Clickatell pipeline bandwidth for sending many messages at once. This process helps prevent API lag by identifying bounded routing spaces for concurrent SMS arrays.
What information do I need when running upsert_inbound_rule? +
You must provide the specific structural parsing block and associated webhook details you want to allocate. This function lets you either create a new rule or update an existing one.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.