ClickSend MCP Server

Created By
ClickSenda year ago
MCP Server for Messaging using ClickSend
Overview

what is ClickSend MCP Server?

ClickSend MCP Server is a Model Context Protocol (MCP) server that allows AI assistants like Claude to send SMS and MMS messages using the ClickSend service.

how to use ClickSend MCP Server?

To use the ClickSend MCP Server, set up your ClickSend username and API key, configure the server with the required environment variables, and integrate it with Claude Desktop by modifying the configuration file.

key features of ClickSend MCP Server?

  • Send SMS messages one at a time using ClickSend.
  • Easy integration with AI assistants like Claude.
  • Requires minimal setup with Node.js.

use cases of ClickSend MCP Server?

  1. Sending automated SMS notifications through AI assistants.
  2. Integrating SMS capabilities into applications using ClickSend.
  3. Facilitating communication via SMS for various services.

FAQ from ClickSend MCP Server?

  • What is the required phone number format?

All phone numbers must be in E.164 format (e.g., +61411111111).

  • How do I find my ClickSend username and API key?

You can find them at https://dashboard.clicksend.com/account/subaccounts after signing up for ClickSend.

  • What should I do if I encounter an "Invalid credentials" error?

Double-check your CLICKSEND_USERNAME and CLICKSEND_API_KEY.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ClickSend
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago