@cloudtext/mcp

MCP server for cloudtext, the open source SMS gateway that turns an Android phone into an SMS API. Gives Claude Desktop, Claude Code, Cursor, and any MCP client the ability to send and read SMS through your own phone and your own number.

Three tools, no per-message markup, works with self-hosted cloudtext instances.

Setup

You need a cloudtext account with a paired Android device and an API key from the dashboard. The key has full account access; treat it like a password.

Claude Code

claude mcp add cloudtext -s user -e CLOUDTEXT_API_KEY=your-key -- npx -y @cloudtext/mcp

Claude Desktop

Add to claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json):

{
  "mcpServers": {
    "cloudtext": {
      "command": "npx",
      "args": ["-y", "@cloudtext/mcp"],
      "env": { "CLOUDTEXT_API_KEY": "your-key" }
    }
  }
}

Cursor

The same object in ~/.cursor/mcp.json.

Slow first start

npx downloads the package on first run. If your client times out waiting, install globally once and point the config at the binary:

npm install -g @cloudtext/mcp

{ "mcpServers": { "cloudtext": { "command": "cloudtext-mcp", "env": { "CLOUDTEXT_API_KEY": "your-key" } } } }

Tools

send_sms

Send an SMS to one or more recipients (E.164 format, for example +254700000000). The sending phone is chosen automatically: your default device, otherwise the enabled device with the most recent heartbeat. Optional device_id, sim_subscription_id, and scheduled_at. Returns an sms_batch_id for delivery checks when the account uses the SMS queue.

get_messages

Read messages across every device on the account. Defaults to received messages, newest first. Filter by direction (received, sent, all), free-text search, sms_batch_id (per-recipient delivery status of a send), device_ids, and a from/to time window. Supports cursor pagination for polling without duplicates or gaps.

list_devices

The phones on the account: ids, enabled state, which one sends by default, last check-in, and message counts.

Self-hosted cloudtext

Point the server at your own instance:

"env": {
  "CLOUDTEXT_API_KEY": "your-key",
  "CLOUDTEXT_BASE_URL": "https://sms.example.com"
}

The /api/v1 suffix is optional and added automatically. Subpath deployments like https://example.com/cloudtext work too. An invalid URL is an error rather than a silent fallback, so a typo never sends your key to the public API.

Environment variables

| Variable | Required | Default | Purpose | |---|---|---|---| | CLOUDTEXT_API_KEY | yes | none | API key from the cloudtext dashboard | | CLOUDTEXT_BASE_URL | no | https://cloudtextapi.frionode.online | Your instance's URL when self-hosting | | CLOUDTEXT_TIMEOUT_MS | no | 30000 | Per-request timeout in milliseconds |

Notes

• Your key stays on your machine: this server talks only to the cloudtext API at the base URL above.
• Sends count against your cloudtext plan quota, and the plan's rate limits apply server-side.
• All diagnostics go to stderr; stdout is reserved for the MCP protocol.

Using it as a library

The package also exports its tool definitions for embedding in another MCP host (this is how the hosted remote endpoint reuses them):

import { createCloudtextMcpServer, staticCredentials, loadConfig } from '@cloudtext/mcp'

const server = createCloudtextMcpServer({
  credentials: staticCredentials(loadConfig(process.env)),
})

Credentials are resolved per tool call, so a multi-tenant host can inject a different key per request. See credentialsFromAuthInfoExtra.

License

MIT. Part of the cloudtext project.