SMSPM MCP Server

io.github.alesavPublished by GitHub account alesavv1.0.1Updated Oct 24, 2026

Send SMS via the SMSPM API from any MCP client.

VerifiedSTDIODesktop onlyCommunication & Collaboration

Overview

AI-generated overview

Lets an assistant send SMS messages through the SMSPM API using a single send_sms tool.

What you can do
This local MCP server exposes one tool, send_sms, which sends a text message through the SMSPM SMS API. It takes a recipient number in international format, the message text, and an optional sender name or number that defaults to smspm.com. It is meant to be configured in an MCP client such as Claude Desktop, Cursor, Windsurf, or Cline.
When to use it
Worth adding when you want an assistant to send transactional or notification SMS from a chat session, for example shipping notices or short alerts, using an existing SMSPM account. It is not a general messaging or receiving tool.
Requirements
Node.js 18 or later, either the npm package smspm-mcp or a local build from source, and an SMSPM account. Two credentials are required as environment variables: SMSPM_HASH and SMSPM_TOKEN. The server runs locally over stdio and needs network access to api.smspm.com.
Before you install
Sending SMS usually costs money on your SMSPM account, and each call sends a real message to a real phone number. The server requires the secrets SMSPM_HASH and SMSPM_TOKEN, which are stored in the local client config file; keep that file out of version control. Messages are sent to the third-party SMSPM API.

Installation

In SourceWeft

  1. Open SMSPM MCP Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

MCP server for the SMSPM SMS API. Send transactional SMS from Claude Desktop, Cursor, Windsurf, Cline, or any MCP client. Get your API credentials at https://app.smspm.com/app/api.

[MCP server on Glama.ai] [MCP server]

SMSPM MCP Server

Send SMS messages from Claude Desktop (or any MCP client) using your SMSPM account.

Prerequisites

  • Node.js 18+
  • An SMSPM account with a Hash and API Token

Installation

Option A — Install from npm (once published)

bash
npm install -g smspm-mcp

Option B — Install from source

bash
git clone https://github.com/alesav/smspm-mcp.gitcd smspm-mcpnpm installnpm run build

Note the full path to the built file — you'll need it in the next step:

/path/to/smspm-mcp/dist/index.js

Configure Claude Desktop

Open your Claude Desktop config file:

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

Add the smspm entry inside mcpServers:

json
{  "mcpServers": {    "smspm": {      "command": "node",      "args": ["/path/to/smspm-mcp/dist/index.js"],      "env": {        "SMSPM_HASH": "your-hash-here",        "SMSPM_TOKEN": "your-api-token-here"      }    }  }}

If installed via npm globally, replace the path with: "npx" as command and ["smspm-mcp"] as args.

Restart Claude Desktop after saving the config.

Getting your Hash and Token

  1. Log in to smspm.com
  2. Go to Settings → API
  3. Copy your Hash (looks like e3dbe013-6f66-4fae-8ae2-96c364cb6b61)
  4. Copy or generate your API Token

Usage

Once configured, just ask Claude:

"Send an SMS to +37256789045 saying Hello from Claude"

"Text +447911123456 — your order has shipped"

Claude will use the send_sms tool automatically.

Tool parameters

ParameterRequiredDescription
toNumber✅Recipient phone in international format (e.g. 37256789045)
text✅Message content
fromNumber❌Sender name/number shown to recipient (default: smspm.com)

Security

  • Your SMSPM_HASH and SMSPM_TOKEN live only in your local config file
  • They are never sent to Anthropic or Claude — only to api.smspm.com
  • Never commit your config file to version control

License

MIT

Source: README.md at commit 4b1439a

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts