ClickSend MCP server
ClickSend in any MCP client, through Memtro: ClickSend does not publish this server. Memtro's ClickSend connector reads ClickSend through its API with the credentials you connect, and one endpoint hands those tools, every other system you connect and Memtro's memory tools to Claude Code, Cursor, Claude Desktop or anything else that speaks Streamable HTTP, as you.
What the model can do
ClickSend SMS: account balance, sent SMS history with delivery status, SMS campaigns, SMS templates, contact lists and their contacts. Can send an SMS to given numbers, send or schedule an SMS campaign to a list, cancel a scheduled SMS or campaign, create, update or delete an SMS template, create or delete a contact list, and add or remove a contact.
Reads
clicksend_get_accountThe ClickSend account: name, username and remaining balance with its currency.clicksend_sms_historySent SMS between two dates (default the last 7 days): recipient, sender, status and when.clicksend_list_sms_campaignsSMS campaigns: name, status, the list it went to, when scheduled or sent.clicksend_list_sms_templatesSaved SMS templates: name and text.clicksend_list_contact_listsContact lists: id, name and how many contacts each holds.clicksend_list_contactsContacts in one list: name, organisation, email and phone number, for when the question is about who is on a list or how to reach someone.
Acts, when you ask
These change something in ClickSend. The model is told to use them only when you ask for exactly that, and each one is granted by name: per team on a shared connection, by the owner on a personal one.
clicksend_create_contact_listCreate a new, empty contact list in ClickSend.clicksend_add_contactAdd one contact to a ClickSend contact list.clicksend_create_sms_templateSave an SMS template in ClickSend.clicksend_send_smsSend one SMS text to up to 10 phone numbers through ClickSend, now or at a scheduled time.clicksend_send_sms_campaignSend one SMS to every contact on a ClickSend contact list, now or at a scheduled time.clicksend_cancel_smsCancel one scheduled SMS that has not been sent yet.clicksend_cancel_sms_campaignCancel a scheduled SMS campaign before it sends.clicksend_update_sms_templateReplace an SMS template's name and text (ClickSend needs both).clicksend_delete_sms_templatePermanently delete an SMS template.clicksend_delete_contactPermanently remove one contact from a ClickSend contact list.clicksend_delete_contact_listPermanently delete a ClickSend contact list together with every contact on it.
Connect it
First connect ClickSend on Dashboard → Connections, then add Memtro to your client once. The ClickSend tools appear alongside the tools of everything else you have connected; nothing is configured per connector.
Claude Code
The Memtro plugin registers the server and a skill for when to use it; the tools are then available in every session.
claude plugin marketplace add memtro-org/claude-memtro
claude plugin install memtro@memtro --config api_key=sk-memtro-...Cursor
Add the server to .cursor/mcp.json in the project, or to the global file under ~/.cursor/.
{
"mcpServers": {
"memtro": {
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Claude Desktop
Create a personal API key on Dashboard → Profile → API keys. In Claude Desktop add an MCP server of type HTTP with URL https://platform.memtro.com/api/mcp and the header Authorization: Bearer sk-memtro-…
OpenCode
A remote server in opencode.json.
{
"mcp": {
"memtro": {
"type": "remote",
"url": "https://platform.memtro.com/api/mcp",
"headers": {
"Authorization": "Bearer sk-memtro-..."
}
}
}
}Pi
One command: pi mcp add memtro --url https://platform.memtro.com/api/mcp --bearer-token-env-var MEMTRO_API_KEY. Tools arrive as mcp__memtro__*. The pi-memtro extension registers it for you, alongside Memtro as the model.
Any other client
Add an MCP server of type HTTP (Streamable HTTP, stateless) at https://platform.memtro.com/api/mcp with the header Authorization: Bearer sk-memtro-.... Codex, Zed, Windsurf, Cline and the SDKs all take a remote server this way.
Who may use it
The key identifies the person, and the server offers that person the tools they may use everywhere else in Memtro. A shared ClickSend connection is used by the teams an administrator granted it to, tool by tool, on the Permissions page; a personal connection is used by its owner alone, and its tools that act stay off until the owner allows them. See Teams and permissions and Connectors.
Ask it like this
- › Did yesterday's reminder texts go out?
- › What is our ClickSend balance?
- › Who is on the Clinic reminders list?
- › Which SMS campaigns went out this month?
- › Send the appointment reminder to the Clinic reminders list at 9am tomorrow
Questions
- Is this an official ClickSend MCP server?
- No. It is Memtro's MCP server with Memtro's ClickSend connector behind it: the connector reads ClickSend through its API with the credentials you connect on Dashboard → Connections, and ClickSend publishes nothing here. The same endpoint carries every other system you connect and Memtro's memory tools.
- What does it cost?
- Nothing on top of Memtro. One price per organisation by its number of users, from $50 a month for up to 10 users after a 7-day free trial, with every connector, the MCP server, jobs and memory included. You bring your own model keys.
- Can it change anything in ClickSend?
- Only when you ask, and only what it has been granted: create a contact list; add a contact to a contact list (never overwriting an existing one); create an SMS template (nothing is sent); send an SMS to up to 10 given numbers, now or scheduled (spends credit); send or schedule an SMS campaign to every contact on a list (spends credit); cancel a scheduled SMS; cancel a scheduled SMS campaign; rename or reword an SMS template; delete an SMS template (permanent); remove a contact from a contact list (permanent); delete a contact list and its contacts (permanent). Every other tool reads, searches or lists. An administrator grants each acting tool by name per team, and a personal connection acts only after its owner allows it.
- Which clients work?
- Any MCP client that speaks Streamable HTTP: Claude Code, Cursor, Claude Desktop, OpenCode, Codex, Zed, Windsurf, Cline and the Anthropic and OpenAI SDKs. There is no local process to run; the server is remote and authenticated with your key.