This guide walks you through connecting the ClickSend MCP (Model Context Protocol) server directly to Claude Code, enabling Claude to send SMS and manage your ClickSend account directly from your terminal. Whether you prefer a quick terminal setup or a manual configuration file, you'll be up and running in minutes.
Option A — CLI (recommended)
Run the following command from your terminal:
claude mcp add clicksend \
-e CLICKSEND_USERNAME=<your-clicksend-username> \
-e CLICKSEND_API_KEY=<your-clicksend-api-key> \
-- npx -y @clicksend/clicksend-mcp-server@latestNotes on flags:
-
-e KEY=VALUE– passes an environment variable. Repeat the flag for each variable you need to set. -
Everything after
--is the exact command Claude Code uses to start the server. -
The default scope is user, which makes the server available across all your projects. Add
--scope projectto write the entry to.mcp.jsonat the repo root instead – useful for sharing the config with your team via source control. -
Keep your API key out of source control – if you're using project scope, don't commit your API key as plain text. Use shell variable substitution instead:
-e CLICKSEND_API_KEY=$CLICKSEND_API_KEY.This reads the value from your local environment at runtime, so no secrets end up in your repo.
Option B — Manual config file
Edit the global configuration file for your operating system:
-
macOS / Linux :
~/.claude.json -
Windows:
%USERPROFILE%\.claude.json
(Alternatively, if you are using project-level scope, edit the .mcp.json file located in your project's root directory).
{
"mcpServers": {
"clicksend": {
"type": "stdio",
"command": "npx",
"args": ["-y", "@clicksend/clicksend-mcp-server@latest"],
"env": {
"CLICKSEND_USERNAME": "<your-clicksend-username>",
"CLICKSEND_API_KEY": "<your-clicksend-api-key>"
}
}
}
}Verify the connection
Once configured, run the following to confirm the server is listed and started successfully:
claude mcp list
This lists all configured servers and flags any that failed to start. Inside an active Claude Code session, use the /mcp slash command to check live status – a green indicator means the server is connected and shows the available tool count.
FAQs
What is the difference between "user" scope and "project" scope when installing? +
By default, installing via the Claude CLI uses user scope, making the ClickSend MCP server available across all your local projects. If you add the --scope project flag, the configuration is written to a local .mcp.json file in your repository's root directory, making it project-specific and easy to share with your team.
How do I securely share my project-scoped MCP configuration without exposing my API keys? +
To share a .mcp.json file safely through version control, do not hardcode your raw credentials. Instead, use shell variable substitution when running the CLI command:
This ensures the configuration references local environment variables rather than storing plain-text keys in your repository.
How do I verify that Claude Code has successfully connected to the ClickSend MCP server? +
You can verify the connection in two ways depending on your environment:
From your terminal: Run
claude mcp listto view all configured servers and check for any startup errors.During an active Claude Code session: Run the
/mcpcommand to open a live status panel. A green indicator means you are successfully connected.
What should I do if the ClickSend MCP server fails to start? +
First, run claude mcp list in your terminal to see if any specific error flags are displayed. Next, check your credentials in ~/.claude.json (or your project's .mcp.json) to ensure both CLICKSEND_USERNAME and CLICKSEND_API_KEY are correct and that you are using your API key, not your account login password.
