Skip to main content
Glama
clicksend-mcp-server

clicksend-mcp-server

Official
by ClickSend

ClickSend MCP Server

This is the official ClickSend MCP Server developed by the ClickSend team. For security reasons do not use unofficial versions of ClickSend MCP.

Purpose

ClickSend MCP is designed to extend ClickSend’s messaging capabilities into modern AI ecosystems and platforms - allowing developers to easily send SMS via ClickSend without needing to write custom code.

This accelerates adoption, enables new AI-driven use cases, and positions ClickSend as a future-ready messaging platform in the age of intelligent automation.

Related MCP server: Twilio SMS MCP Server

Requirements

  • Node.js >= 18

    • you can usenvm (Node Version Manager) to set the right version to run this app

Installation

Download an AI desktop client. An example would be Claude for Desktop which you can download here.

Configuration

The server requires two environment variables:

  • CLICKSEND_USERNAME: Your ClickSend username

  • CLICKSEND_API_KEY: Your ClickSend API Key

You can find the username and key at https://dashboard.clicksend.com/account/subaccounts once you Sign Up to ClickSend.

Claude Desktop Configuration

  • Open Claude for Desktop

  • Go to Settings from the system's menu bar

  • In the settings window, navigate to the Developer tab and click Edit Config. This opens the configuation file located at:

    • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

    • Windows: %APPDATA%\Claude\claude_desktop_config.json

  • Using NPM Package

{
  "mcpServers": {
    "clicksend": {
      "command": "npx",
      "args": [
        "-y",
        "@clicksend/clicksend-mcp-server@latest"
      ],
      "env": { 
        "CLICKSEND_USERNAME": "<username>",
         "CLICKSEND_API_KEY": "<api-key>"
      }
    }
  }
}
  • Using Local Build

{
  "mcpServers": {
    "clicksend": {
      "command": "node",
      "args": [
        "/path/to/repository/build/clicksend-mcp.js"
      ],
      "env": {
        "CLICKSEND_USERNAME": "your clicksend username",
        "CLICKSEND_API_KEY": "your API Key"
      }
    }
  }
}

After that, restart Claude Desktop to reload the configuration. If connected, you should see clicksend-send-sms when you click on the hammer icon.

Example Interactions with Claude

Here are some natural ways to interact with the server through Claude:

Simple SMS:

Send a text message to the number 61411111111 saying "I'm using ClickSend MCP server to sent SMS!"

Features

  • Send one SMS at a time by setting up the clicksend username and API Key

  • Get Price for sending message to contact list

  • Search Contacts or Contact Lists and send message to them

  • Get SMS Templates, and use that to send message

  • View/Retrieve SMS history

  • Get SMS Statistics for last 30 days

Supported APIs

  1. POST /v3/sms/send

  • Operation ID: send-sms

  • Summary: Send SMS

  • Description: Send messages to recipients, either as phone numbers or contacts from a contact list.

  1. POST /v3/sms/price

  • Operation ID: calculate-sms-price

  • Summary: Calculate SMS Price

  • Description: Calculate the price of sending messages based on message type and length.

  1. GET /v3/sms/templates

  • Operation ID: view-sms-templates

  • Summary: View SMS Templates

  • Description: Retrieve SMS templates with filtering options.

  1. GET /v3/sms/history

  • Operation ID: view-sms-history

  • Summary: View SMS History

  • Description: View previously sent SMS with filtering and pagination options.

  1. GET /v3/statistics/sms

  • Operation ID: view-sms-statistics

  • Summary: View SMS Statistics

  • Description: Get SMS statistics for the last 30 days.

  1. GET /v3/search/contacts-lists

  • Operation ID: view-contact-lists

  • Summary: View Contact Lists

  • Description: Get a list of searched contact lists.

Important Notes

  1. Phone Number Format: All phone numbers must be in E.164 format (e.g., +61411111111)

  2. Rate Limits: Be aware of your ClickSend account's rate limits and pricing

  3. Security: Keep your ClickSend credentials secure and never commit them to version control

Troubleshooting

Common error messages and solutions:

  1. "Phone number must be in E.164 format"

    • Make sure the phone number starts with "+" and the country code

  2. "Invalid credentials"

    • Double-check your CLICKSEND_USERNAME and CLICKSEND_API_KEY. You can copy them from the ClickSend Dashboard

Contributing

Contributions are welcome! Please read our contributing guidelines before submitting pull requests.

License

This project is licensed under the MIT License - see the LICENSE file for details.

Security

Please do not include any sensitive information (like phone numbers or ClickSend credentials) in GitHub issues or pull requests.

Available Tools

6 tools
get--v3-search-contacts-listsC

View Contact Lists

Inputs: q.

get--v3-sms-historyC

View SMS History

Inputs: q, page, limit, date_to, +3 more.

get--v3-sms-templatesC

View SMS Templates

Inputs: q, page, limit, order_by.

get--v3-statistics-smsB

View SMS Statistics

Inputs: no named parameters.

post--v3-sms-priceC

Calculate SMS Price

Inputs: messages.

post--v3-sms-sendC

Send SMS

Inputs: messages.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 6 tools

    Disambiguation4/5

    Each tool targets a distinct endpoint such as sending, pricing, or viewing templates, but 'View SMS Statistics' and 'View SMS History' could be mistaken for one another by an agent looking for past SMS data. The short descriptions provide only a general hint, leaving some ambiguity between those two.

    Naming Consistency4/5

    Tool names follow a consistent pattern of HTTP method plus '--v3--' plus an endpoint path, making them predictable from the API structure. However, the resource portion varies in word order and phrasing (e.g., 'sms-send' vs 'statistics-sms' vs 'search-contacts-lists'), so it is not fully uniform.

    Tool Count5/5

    Six tools is a well-scoped size for an SMS server, covering sending, pricing, templates, contact lists, history, and statistics. Each tool has a clear role and there is no obvious filler.

    Completeness4/5

    The core SMS workflow is covered: calculate price, view templates and contact lists, send the message, then capture history and statistics. The set has minor gaps around managing/updating contacts or templates, but these are not essential for sending or reviewing SMS messages.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI-powered SMS messaging through Twilio with automatic conversation threading, message status tracking, and webhook support for receiving inbound messages.
      1
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to send, receive, schedule, and manage SMS and MMS messages using the Twilio Programmable Messaging API. It provides comprehensive tools for handling bulk messaging, conversation threads, and real-time inbox monitoring through a secure, production-grade architecture.
      16
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to send SMS, manage contacts, verify numbers, and query campaigns via SMS Masivos platform using natural language.
      30
      57 npm
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending SMS messages, managing contacts, campaigns, and inbox from AI assistants like Claude and ClickUp.
      33 npm
      MIT