Skip to main content
Glama
alesav

smspm-mcp

by alesav
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

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.

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

Related MCP server: Aligo SMS MCP Server

Installation

Option A — Install from npm (once published)

npm install -g smspm-mcp

Option B — Install from source

git clone https://github.com/alesav/smspm-mcp.git
cd smspm-mcp
npm install
npm 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:

Platform

Path

macOS

~/Library/Application Support/Claude/claude_desktop_config.json

Windows

%APPDATA%\Claude\claude_desktop_config.json

Add the smspm entry inside mcpServers:

{
  "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

Parameter

Required

Description

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

Available Tools

1 tool
send_smsB

Send an SMS message via SMSPM. Requires a recipient phone number (international format), message text, and optional sender name.

ParametersJSON Schema
NameRequiredDescriptionDefault
textYesThe SMS message text to send
toNumberYesRecipient phone number in international format, e.g. 37256789045
fromNumberNoSender name or number shown to recipient (default: smspm.com)smspm.com

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must fully disclose behavioral traits. It mentions the tool sends an SMS (a mutation), but lacks details on side effects (e.g., charges, delivery status), error handling, rate limits, or whether the operation is synchronous. This is insufficient for an agent to reason about risks or expectations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single sentence of 14 words, highly concise and front-loaded with the purpose. However, the brevity sacrifices important behavioral details, preventing a higher score.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, output schema, or sibling tools, the description must provide comprehensive context. It covers purpose and parameters but omits critical operational aspects like success/failure indicators, delivery guarantees, message length limits, or authentication requirements. This is incomplete for a mutation tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100%, so the baseline is 3. The description adds the context 'international format' for toNumber and 'optional' for fromNumber, which are already present in the schema descriptions. No new semantic value is added beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description uses the specific verb 'Send' and identifies the resource as 'SMS message via SMSPM', clearly defining the tool's purpose. No sibling tools exist, so differentiation is not needed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines3/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description states required parameters (recipient phone in international format, message text, optional sender name) but does not provide any context on when to use this tool versus alternatives or any prerequisites. Since no sibling tools exist, the lack of alternatives is acceptable, but the absence of usage conditions like message length limits or cost implications reduces guidance.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedsend_sms
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

B3.4/5.0
Disambiguation5/5

Only one tool exists, so there is no possibility of confusion with other tools.

Naming Consistency5/5

With a single tool, naming consistency is not applicable; the name 'send_sms' follows a clear verb_noun pattern.

Tool Count3/5

One tool is borderline thin for an SMS service; additional tools like checking delivery status could be expected.

Completeness2/5

The tool only supports sending SMS without any supporting operations like status checks, scheduling, or contact management, leaving significant gaps.

Maintenance

ActivitySlowing
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • Aligo SMS MCP Server

    hongsw
    A
    license
    B
    quality
    D
    maintenance
    A Model Context Protocol (MCP) server that allows AI agents like Claude to interact with the Aligo SMS API to send text messages and retrieve related information.
    1
    1
    MIT
  • Grizzly SMS MCP Server by GrizzlySMS-Git

    Grizzly SMS MCP Serverofficial

    GrizzlySMS-Git
    A
    license
    A
    quality
    D
    maintenance
    MCP server for integrating with Grizzly SMS platform to rent virtual numbers, receive SMS verification codes, and manage activations directly from AI assistants like Cursor, Claude Desktop, and OpenClaw.
    8
    15
    MIT

  • smsmanager

    larsdittinger
    F
    license
    A
    quality
    D
    maintenance
    MCP server for sending SMS messages via SmsManager.cz HTTP API, supporting high, economy, and low delivery gateways.
    1
    -

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/alesav/smspm-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server