Skip to content

Marketing Automation

ClickSend MCP connector

The ClickSend connector links your ClickSend contact lists, contacts, subaccounts and account usage to Claude, ChatGPT, Cursor and any MCP client, so your team can ask for list work in plain language and every change is logged.

Connect on Elaichi How to connect

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect ClickSend to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect ClickSend once

  1. Open Connections, choose Add connection, and pick ClickSend.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a ClickSend API key. One person generates a token in ClickSend and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

clicksend
ClickSend
Attentive
Beamer
beehiiv
Bird
Buffer
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

ClickSend MCP connector for Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

ClickSend MCP connector for ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

ClickSend MCP connector for Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect ClickSend to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Connect ClickSend on Elaichi See pricing

Use cases

What teams do with ClickSend through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Marketing

    Clean a list before a campaign

    Ask for duplicates and opted-out numbers to be removed from a ClickSend contact list before the next send goes out, so nobody gets texted twice or against their wishes.

  • Marketing

    Import a spreadsheet into a new list

    Create a ClickSend contact list for an event or promotion and import the contacts you were sent, without opening ClickSend and pasting rows by hand.

  • Sales

    Move a lead after a call

    Once a prospect converts, copy or transfer their contact from the prospects list to the customers list in ClickSend so they hear the right messages from now on.

  • Support

    Fix a customer's number on the spot

    When a customer calls in with a new mobile number, find their ClickSend contact and update it during the conversation.

  • Operations

    Set up a subaccount for a new team

    Create a ClickSend subaccount for a new region or department, and regenerate its API key later if it needs rotating.

  • Finance

    Check how much has been used

    Ask for ClickSend account usage and a rundown of subaccounts to see where spend is going before the invoice arrives.

Try asking

  • “Which ClickSend contact lists grew this month?”
  • “Show account usage for each ClickSend subaccount.”
  • “Search ClickSend contact lists for EMEA prospects.”

See all 201 ClickSend tools below

Compare

Elaichi vs Zapier MCP vs Composio for ClickSend

All three can connect ClickSend to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.

Elaichi compared with Zapier MCP and Composio for ClickSend, by what to check
What to check Elaichi Zapier MCP Composio
Where the AI connects One address for the whole organization. https://api.elaichi.ai/mcp A server per member, created at sign-in. An MCP endpoint per team, or an SDK.
Control over ClickSend tools Allow or restrict single ClickSend tools, per role or user. App and action restrictions on the account. Role permissions, down to the action.
Record of calls One audit entry per ClickSend call. A History tab of tool calls. A log of every tool call.
Single sign-on SAML or OIDC, plus SCIM, on Gold. SAML on Enterprise. SAML and OIDC on Enterprise.
Price $15 per user per month. 2 tasks per successful call. Billed per tool call.

Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.

Longer take: Zapier MCP alternative and when you don't need an MCP gateway.

AI tools

ClickSend tools for your AI agents

201 tools are ready to call through Elaichi's MCP endpoint the moment you connect ClickSend, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting ClickSend gets you

6 screens from the product, each doing one job for your ClickSend account.

The agent

Ask about ClickSend contact lists in plain language.

Answers come from live ClickSend subaccounts, contact lists and usage records.

  • contact lists
  • contacts
  • subaccounts
  • accounts

Ask Elaichi to work across your apps.

Which ClickSend contact lists grew this month?

Show account usage for each ClickSend subaccount.

Search ClickSend contact lists for EMEA prospects.

Also runs in Claude, ChatGPT or Cursor

MCP clients

Claude, ChatGPT and Cursor share one ClickSend endpoint.

Connect any MCP client over OAuth, with no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emily Carter

 • Connected 4 minutes ago
Cursor
M

Megan Brooks

 • Connected 2 hours ago
ChatGPT
R

Ryan Hayes

 • Connected Yesterday

Tool catalog

201 ClickSend tools are ready to call.

Accounts, subaccounts, usage and contact lists are covered with no custom code.

  • List all ClickSend account
  • ClickSend account get usage
  • List all ClickSend subaccounts
  • Create a ClickSend subaccount
ElaichiTools
Tool Action Description
List all ClickSend account List Get information about the authenticated ClickSend account, including user details, balance, billing info, SMS settings, and preferences. Returns: total, per_page, current_page, last_page, from, to.
ClickSend account get usage Get Get ClickSend account usage for a specific year and month, broken down by subaccount across SMS, MMS, voice, fax, post, email, and postcard channels. Returns: sms, mms, voice, fax, post, email, email_transactional, postcards, sms_total, voice_total, fax_total, post_total, email_total, mms_total, email_transactional_total, postcards_total, _currency. Required: year, month.
List all ClickSend subaccounts List List all ClickSend subaccounts. Returns: subaccount_id, api_username, email, phone_number, first_name, last_name, api_key, access_smpp, access_users, access_billing, access_reporting, access_contacts, access_settings, access_sms, access_email, access_voice, access_fax, access_post, access_reseller, access_global_sending, access_mms, hide_pricing, share_campaigns, notes, is_main, sign_up_type. Max…
Create a ClickSend subaccount Create Create a new ClickSend subaccount. Returns the created subaccount object including subaccount_id, api_username, email, api_key, and access permission flags.
Get single ClickSend subaccount by ID Get Get a specific ClickSend subaccount by id. Returns: subaccount_id, api_username, email, phone_number, first_name, last_name, api_key, access_smpp, access_users, access_billing, access_reporting, access_contacts, access_settings, access_sms, access_email, access_voice, access_fax, access_post, access_reseller, access_global_sending, access_mms, hide_pricing, share_campaigns, notes, is_main,…

Toolboxes

Every team gets its own ClickSend toolbox.

Curate one toolbox per team so each sees only the ClickSend tools it needs.

  • Marketing
  • Sales
  • Support
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Marketing toolbox

ClickSend · contact lists and campaigns

 ClickSend starter 18 Mar 4, 2026

Sales toolbox

ClickSend · outbound contacts and lists

 — 9 Mar 2, 2026

Support toolbox

ClickSend · customer notifications

 — 24 Feb 27, 2026

Operations toolbox

ClickSend · subaccounts and account usage

 ClickSend starter 6 Feb 19, 2026

Finance toolbox

ClickSend · usage and spend records

 — 31 Jan 30, 2026

Platform toolbox

ClickSend · api keys and subaccount setup

 — 12 Jan 22, 2026

Shared connections

Teammates send through ClickSend without holding keys.

See who connected each ClickSend account and which teams and members use it.

  • Marketing
  • Sales EMEA
  • Support
  • Operations
ElaichiConnections
Connection Scope Status Access
CL

ClickSend (Marketing)

Connected by Emily Carter

 Personal • Active 1 team · 6 members
CL

ClickSend (Sales EMEA)

Connected by Jake Morgan

 Organization • Active 3 teams · 24 members
CL

ClickSend (Support)

Connected by Megan Brooks

 Organization • Active 2 teams · 11 members
CL

ClickSend (Operations)

Connected by Tyler Reed

 Personal • Needs re-auth 1 team · 3 members
CL

ClickSend (Finance)

Connected by Ryan Hayes

 Personal • Active Not shared
CL

ClickSend (Product Launch)

Connected by Ashley Parker

 Personal • Active 2 teams · 9 members

Audit log

Every ClickSend call is on the record.

When, who, what happened, type and resource for each contact list and subaccount change.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM
E

Emily Carter

emily.carter@northwind.io

 Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM
J

Jake Morgan

jake.morgan@northwind.io

 Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM
M

Megan Brooks

megan.brooks@northwind.io

 Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM
T

Tyler Reed

tyler.reed@northwind.io

 ClickSend Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM
R

Ryan Hayes

ryan.hayes@northwind.io

 ClickSend Contact lists Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM
A

Ashley Parker

ashley.parker@northwind.io

 ClickSend Contact lists List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and ClickSend work finishes.

Fetch contact lists, group them, draft a digest, get approval, post back to ClickSend.

ClickSend digest

Run 418 · started 2 minutes ago · on behalf of Emily Carter

  1. ✓

    Schedule

    Every weekday at 8:00 AM

    0.2s
  2. ✓

    Fetch contact lists

    ClickSend

    1.4s
  3. ✓

    Group by owner

    Transform

    0.1s
  4. ✓

    Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s

  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve

  6. Post the digest

    ClickSend

    Queued

Collections and dashboards

ClickSend numbers land before anyone asks.

Four metrics, 14 days of contact lists created and a team breakdown, refreshed on schedule.

ClickSend health

Refreshed 4 minutes ago · every 15 minutes · from the contact lists collection

Live

Contact lists

1,284 ↓ 12%

Contacts

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Contact lists created

Last 14 days

By team

Share of activity

Marketing 34%

Sales EMEA 27%

Support 21%

Operations 18%

Related connectors

More from the catalog

Browse all 600+ connectors →

FAQ

Frequently asked questions

How do I connect ClickSend to Claude?

Connect ClickSend in Elaichi first, which asks for your ClickSend API key rather than a sign-in screen, so there is no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Sign in with your Elaichi account and ClickSend is ready to use.

Does ClickSend work with ChatGPT and Cursor as well as Claude?

Yes. Once ClickSend is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client and the Elaichi Agent. You connect ClickSend once and every client picks it up.

What can an AI agent actually do with my ClickSend data?

It can create, search and update ClickSend contact lists, add or update individual contacts, import a batch of contacts into a list, remove duplicates and opted-out numbers, and copy or move contacts between lists. It can also create and manage ClickSend subaccounts and report on account usage. Short, concrete asks work best, such as remove duplicates from the spring promo list.

Does connecting ClickSend give the AI everything in my account?

No. Every request runs inside the access of the person who signed in, so the AI can only reach the ClickSend lists, contacts and subaccounts that person could already reach. Elaichi can narrow that further with restrictions, and it can never widen it beyond what ClickSend itself allows.

Can my team share one ClickSend connection?

Yes. One person connects ClickSend with the API key and shares the connection with a team in Elaichi, and nobody else ever sees or handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who edited a contact list or moved a contact, not a shared login.

Can I stop an agent from deleting or changing things in ClickSend?

Yes. Restrictions in Elaichi work per action, so you can allow reading and updating ClickSend contacts while blocking deleting lists, contacts or subaccounts. A blocked action is never shown to Claude, ChatGPT or any other client at all, so no prompt can reach it.

What happens to a ClickSend connection when someone leaves?

Offboarding that person in Elaichi ends their access to ClickSend through every client at once. A shared ClickSend connection keeps working for everyone else on the team, and if you ever want it gone, disconnecting once in Elaichi removes ClickSend from Claude, ChatGPT, Cursor and every other client together.

Does the ClickSend MCP connector work with Gemini, Codex, Claude Code or other MCP clients?

Yes. ClickSend is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.

Is Elaichi an alternative to Zapier MCP for ClickSend?

Yes. Both let Claude, ChatGPT or Cursor use ClickSend. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every ClickSend call.

How is Elaichi different from Composio for ClickSend?

Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to ClickSend: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.

Put ClickSend in front of your team

14 days on Gold, no credit card. Connect it once and pick what each team can call.

Connect ClickSend Talk to us
Works with
Claude ChatGPT Cursor and any other MCP client, or the Elaichi Agent.
When the trial ends
Nothing is deleted. Connections, roles and the audit log stay where they are, so subscribing picks up exactly where you left off.