Overview

PixelSMS is a simple SMS API for developers. Send SMS worldwide with a single POST request. Get your API key from the dashboard.

Base URL: https://pixelsms.tech
All requests use JSON where applicable.
Authenticate with your API key in the header.

Authentication

Include your API key in every request. Use either the X-Api-Key header or Authorization: Bearer YOUR_KEY. Never expose your key in client-side code or version control.

Header

X-Api-Key: ps_live_xxxxxxxx...
# or
Authorization: Bearer ps_live_xxxxxxxx...

Send SMS

POST /api/v1/sms — Send a single SMS. Body: to (required),text (required), from (optional sender name, max 11 chars). Use E.164 for to (e.g. +1234567890).

curl -X POST https://pixelsms.tech/api/v1/sms \
  -H "X-Api-Key: YOUR_PIXELSMS_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"to": "+1234567890", "text": "Hello from PixelSMS", "from": "PixelSMS"}'

Responses & Errors

Success returns 200 with { success: true, message_id, status }. Errors: 401 invalid/missing API key, 400 invalid body, 402 insufficient balance, 422 send failed (carrier/validation).

Success (200)

{
  "success": true,
  "message_id": "77232007287",
  "status": "sent"
}

Rate & Limits

Sending is limited by your wallet balance. Add funds in the dashboard. Message length and sender ID limits follow carrier rules; keep messages concise and use E.164 for recipient numbers.

MCP (AI coding agents)

The Model Context Protocol (MCP) lets AI assistants talk to tools in a standard way. PixelSMS ships an MCP server so agents can read our API reference and help you write code. The server does not send SMS and does not use your API key.

Getting started

Requirements: Node.js 18+. Build the server once, then add it to your editor.

Add the PixelSMS MCP server in your .mcp.json (project root or Cursor config). Same style as other MCPs (e.g. context7, Supabase). No API key needed.

.mcp.json

{
  "mcpServers": {
    "pixelsms": {
      "command": "npx",
      "args": ["-y", "pixelsms-mcp-server@latest"]
    }
  }
}

Or from a local clone: "command": "node", "args": ["path/to/mcp-server/dist/index.js"]

Capabilities

API reference — Agents get endpoint, auth, body, and error codes so they can answer questions or generate code that uses the PixelSMS API.

Sending SMS is done with your API key via POST /api/v1/sms from your app; MCP is docs-only.

Available tool

pixelsms_get_api_docs — Returns a short API summary (base URL, auth, request/response, errors).

Using with agents

Once the server is configured, your agent can use the API docs to give accurate answers and code.

Example: Ask "What is the PixelSMS API for sending SMS?" or "How do I authenticate with PixelSMS?" The agent will call pixelsms_get_api_docs and respond with the right endpoint, headers, and body.

Troubleshooting

Using npx: ensure pixelsms-mcp-server is published on npm (or use a local path)
Local path: build with cd mcp-server && npm install && npm run build, then use full path to dist/index.js
In Cursor: Settings → Features → MCP, then add or refresh the server