How to Use the Clickatell MCP in Cursor

Q: How do I add the Clickatell server to Cursor?

Create a .cursor/mcp.json file in your project root. Add the Clickatell MCP Server configuration, and Cursor's Agent mode will immediately gain access to the SMS tools.

Q: Can Cursor test MSISDN carrier coverage using Clickatell?

Yes. Cursor invokes testcarriercoverage to run automated validation checks on specific MSISDN routes, returning the carrier paths directly to your chat panel.

Q: How does Cursor track Clickatell campaign schedules?

The editor uses listscheduledcampaigns to identify active marketing arrays. You can view, verify, or modify your Clickatell schedules directly from the Cursor sidebar.

Q: Can I delete stale routing rules using Cursor?

Yes, Cursor runs wipeinboundrule to obliterate legacy HTTP logic bounds on your Clickatell account, ensuring your inbound rule list stays clean.

Code and test Clickatell SMS workflows directly in Cursor.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

MCP Servers - Free for Subscribers

Connect Clickatell MCP to Cursor

Create your Vinkius account to connect Clickatell to Cursor and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Setup Clickatell with Cursor

Ask AI about this MCP

ChatGPT

Claude

Perplexity

Debug Clickatell MCP Server tools in Agent mode

This Clickatell MCP Server relies on `get_delivery_status` to let Cursor inspect mobile messaging infrastructure while you write code. The editor triggers the tool to fetch real carrier properties and injects that structural data directly into your active editor tab. Instead of writing mock payloads, Cursor triggers `dispatch_sms_message` to generate real E.164 outbound SMS messages. You see the actual JSON schema your code needs to output.

Inspect and modify inbound webhook routing

Inspecting active routing rules is driven by `list_inbound_rules` directly inside your Cursor MCP setup. The editor pulls your current mobile-originated bounds directly into your workspace. If you need to point incoming SMS to a new local server, Cursor executes `upsert_inbound_rule` to allocate a fresh webhook parsing block. You test and refine your webhooks without leaving your editor.

Run bulk SMS pipeline checks inside the editor

Optimizing your messaging code is straightforward when Cursor calls `dispatch_bulk_sms` to evaluate high-volume pipelines using this MCP toolset. The editor identifies bounded routing spaces and traces concurrent SMS arrays. When debugging queue failures, Cursor runs `cancel_queued_message` to instantly vaporize scheduled drops. You manage your active Clickatell pipelines without switching to a web browser.

Setup guide

Set up Clickatell MCP in Cursor

Prerequisites

Cursor installed (macOS, Windows, or Linux)
Active Vinkius subscription with a valid endpoint token

1

Open MCP Settings

Go to Cursor Settings → MCP or open the Command Palette (Cmd+Shift+P / Ctrl+Shift+P) and search for "MCP: Add Server".
2

Add the Clickatell MCP

Cursor will create or open .cursor/mcp.json in your project root. Paste the JSON snippet on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com.
3

Enable Agent mode

Open Composer (Cmd+I / Ctrl+I) and switch to Agent mode using the dropdown at the top. MCP tools are only available in Agent mode.
4

Verify the connection

Ask Cursor something like "List my recent Clickatell transactions." If the MCP tools are loaded correctly, Cursor will call the Clickatell tools automatically. You can also check Settings → MCP for a green status indicator.

.cursor/mcp.json

{
  "mcpServers": {
    "clickatell-mcp": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

Get your connection token →

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.

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Connect Clickatell now

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Clickatell MCP in Cursor

Create a `.cursor/mcp.json` file in your project root. Add the Clickatell MCP Server configuration, and Cursor's Agent mode will immediately gain access to the SMS tools.

Yes. Cursor invokes `test_carrier_coverage` to run automated validation checks on specific MSISDN routes, returning the carrier paths directly to your chat panel.

The editor uses `list_scheduled_campaigns` to identify active marketing arrays. You can view, verify, or modify your Clickatell schedules directly from the Cursor sidebar.

Yes, Cursor runs `wipe_inbound_rule` to obliterate legacy HTTP logic bounds on your Clickatell account, ensuring your inbound rule list stays clean.

Cursor stores your Clickatell API tokens in local configuration files. Recipient MSISDN numbers and SMS payload texts are processed locally in your editor sandbox, never sent to external servers.

Use it with your favorite AI tools

Connect this server to Cursor, Claude, VS Code, and more.

OpenAI Agents SDK sdk-python

Google ADK sdk-python

Pydantic AI sdk-python

Vercel AI SDK sdk-typescript