Clicksend MCP Server runs on your own machine — the client starts it, so there is no endpoint to ping. 76 installs a week from npm. Last commit 11 Aug 2026.
MCP for ClickSend.
Today is the operative word: we check Clicksend MCP Server every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add clicksend-mcp-server -- npx -y @clicksend/clicksend-mcp-server
{
"mcpServers": {
"clicksend-mcp-server": {
"args": [
"-y",
"@clicksend/clicksend-mcp-server"
],
"command": "npx"
}
}
}
[mcp_servers.clicksend-mcp-server]
command = "npx"
args = ["-y", "@clicksend/clicksend-mcp-server"]
{
"mcpServers": {
"clicksend-mcp-server": {
"args": [
"-y",
"@clicksend/clicksend-mcp-server"
],
"command": "npx"
}
}
}
{
"mcpServers": {
"clicksend-mcp-server": {
"args": [
"-y",
"@clicksend/clicksend-mcp-server"
],
"command": "npx"
}
}
}
This one needs environment variables set before it will start:
CLICKSEND_USERNAME (Your ClickSend account username), CLICKSEND_API_KEY (Your ClickSend API key).
The author declared them in the registry entry; get the values from the project itself.
MCP Server for okx.com
MCP server and CLI for Brave DevTools
CLI and MCP server for the LinkedIn API
quickstart for mcp deployment
MCP server for matomo
MCP server for Blockscout
MCP server for customer-io
MCP server for SWAPI API
Answers built from our own checks of this server.