Overview

The ClickSend MCP Server is the official Model Context Protocol (MCP) server provided by ClickSend. It acts as a secure bridge between modern AI clients (for example, AI desktop assistants) and ClickSend’s messaging APIs, allowing AI applications to send SMS without embedding ClickSend credentials or writing bespoke integration code. Using the official server ensures you run a verified release and avoid untrusted forks or unofficial versions.

This guide helps developers get the official MCP server up and running, configure it for an AI desktop client (example: Claude Desktop), and safely supply credentials. It includes installation and configuration examples, supported endpoints, common use cases, and security notes so you can deploy quickly and securely.

Features

Send SMS messages via ClickSend from AI clients
Calculate SMS pricing for messages or contact lists
Search contacts and contact lists; send messages to lists
Retrieve SMS templates and use them to dispatch messages
View SMS history with filters and pagination
Get SMS statistics (last 30 days)
Runs on Node.js (>= 18) and can be installed via npx or built locally

Installation / Configuration

Prerequisites:

Node.js >= 18 (use nvm to switch versions if needed)
ClickSend account with API key and username

Required environment variables:

export CLICKSEND_USERNAME="your_clicksend_username"
export CLICKSEND_API_KEY="your_clicksend_api_key"

Install and run via npx (recommended for quick setup):

# Runs the latest published package without installing globally
npx -y @clicksend/clicksend-mcp-server@latest

Run a local build (if you cloned the repository and built the project):

# Example: run the compiled server script
node /path/to/repository/build/clicksend-mcp.js

Example Claude Desktop config (macOS / Windows paths shown). Add to the “Developer -> Edit Config” JSON.

Using npx (auto-download):

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

Using a 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"
      }
    }
  }
}

Claude Desktop config file locations:

macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
Windows: %APPDATA%\Claude\claude_desktop_config.json

After saving the configuration, restart the AI client to pick up the MCP server. The client should expose actions such as clicksend-send-sms in its developer actions list.

Available Resources (Supported APIs)

Path	Method	Operation ID	Purpose
/v3/sms/send	POST	send-sms	Send SMS to phone numbers or contact list entries
/v3/sms/price	POST	calculate-sms-price	Estimate price for a message or list
/v3/sms/templates	GET	view-sms-templates	Retrieve SMS templates
/v3/sms/history	GET	view-sms-history	Fetch previously sent messages
/v3/statistics/sms	GET	view-sms-statistics	30-day SMS statistics
/v3/search/contacts-lists	GET	view-contact-lists	Search contact lists

Example curl (local server running on default port):

curl -X POST http://localhost:PORT/v3/sms/send \
  -H "Content-Type: application/json" \
  -d '{
    "to": ["+61411111111"],
    "message": "Test message from ClickSend MCP server via AI client"
  }'

Use Cases

AI assistant sends OTPs, alerts, or confirmations using ClickSend templates without exposing API keys to end users.
An AI workflow queries contact lists, composes personalized messages, and multicasts to a selected list.
Price estimation for bulk sends before executing a campaign (calculate-sms-price endpoint).
Retrieve SMS history and statistics to produce analytics or inform AI-generated summaries.

Concrete example prompt a user might send to their AI client:

“Send a text to +61411111111 saying ‘Your appointment is confirmed for 10am tomorrow.’” The AI client translates that into a POST /v3/sms/send request to the MCP server.

Troubleshooting & Notes

Phone numbers must use E.164 format (e.g., +61411111111). Invalid format errors will be returned by the server.
If you see “Invalid credentials”, verify CLICKSEND_USERNAME and CLICKSEND_API_KEY match your ClickSend Dashboard values.
Be mindful of ClickSend account rate limits and pricing—bulk sends can incur costs.
Node.js version mismatches can cause startup failures; ensure Node >= 18.

Security

Use the official ClickSend MCP Server release to avoid supply-chain or impersonation risks.
Never commit CLICKSEND_USERNAME or CLICKSEND_API_KEY to version control. Load credentials from environment variables, secure vaults, or a secrets manager.
Limit network access to the MCP server where possible, and monitor traffic for unusual activity.
Report security issues through the repository’s official channels and avoid posting secrets in issues or PRs.

Contributing & License

Contributions are welcome. Follow the repository’s contributing guidelines and do not include sensitive data in PRs or issues. The project is distributed under the MIT License (see the repository for license details).

ClickSend Official MCP Server Download Guide