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.
-
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.
In Elaichi
Connect ClickSend once
-
Open Connections, choose Add connection, and pick ClickSend.
-
Optionally set Share with to give a team access, then press Connect.
-
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.
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.
Connect ClickSend to Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Connect ClickSend to ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web today. The plugin directory lives at chatgpt.com/plugins.
Connect ClickSend to Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
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.”
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.
No tools match your search.
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.
Copy the endpoint
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
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
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
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
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 Emma Laurent
-
✓
Schedule
Every weekday at 08:00
0.2s -
✓
Fetch contact lists
ClickSend
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Michael Brennan
Approve Deny -
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
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%
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 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.
Put ClickSend in front of your team
Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.