SM SMSMobileAPI MCP

MODEL CONTEXT PROTOCOL · PRODUCTION

Give an AI secure access to your real mobile activity.

Send SMS and WhatsApp messages from connected devices, retrieve incoming SMS, inspect missed, incoming and outgoing calls, and list mobiles through one authenticated MCP endpoint.

Connect a clientREST API documentation
Streamable HTTP endpointhttps://mcp.smsmobileapi.com/mcp
AI / CRMMCP tool call
→
SMSMobileAPIPermission + account isolation
→
Your mobileSIM, SMS, WhatsApp & calls

AVAILABLE TOOLS

Useful operations, scoped to the authenticated account

READ

list_connected_mobiles

Find device IDs, labels, phone metadata, connection state and battery information.

READ

list_received_sms

Retrieve synchronized incoming SMS, optionally by mobile, timestamp or unread state. The default window is the latest 30 days.

ACTION

send_sms

Queue one SMS through a chosen physical mobile and SIM after explicit user confirmation.

READ

list_sent_sms

Inspect API message identifiers, queue state, delivery information and errors.

READ

list_missed_calls

List missed calls with filters, dates and pagination.

READ

list_incoming_calls

Retrieve answered incoming calls, names, numbers and durations.

READ

list_outgoing_calls

Retrieve calls placed from connected mobiles.

ACTION

send_whatsapp

Queue a WhatsApp text through the connected environment after confirmation.

READ

list_received_whatsapp

Read messages recovered through the WhatsApp synchronization workflow. The default filter is the current UTC date.

SYNC

synchronize_received_whatsapp

Open the time-limited synchronization window required for new WhatsApp messages.

READ

check_whatsapp_number

Check whether an international recipient is available on WhatsApp.

RECOMMENDED CONNECTION

OAuth 2.1 with PKCE

  1. Use the MCP URLConfigure your client with https://mcp.smsmobileapi.com/mcp.
  2. Authorize your accountThe client discovers OAuth metadata automatically and opens the secure connection page.
  3. Review the requested permissionsApprove the scopes requested by the client. Tokens are short-lived and revocable without changing your API key.
Generic MCP configurationJSON
{
  "mcpServers": {
    "smsmobileapi": {
      "url": "https://mcp.smsmobileapi.com/mcp"
    }
  }
}

Clients supporting remote Streamable HTTP and OAuth discovery should use this configuration.

JSON-RPC EXAMPLES

Call a tool directly

List mobilescurl
curl -X POST 'https://mcp.smsmobileapi.com/mcp' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  --data '{
    "jsonrpc":"2.0",
    "id":1,
    "method":"tools/call",
    "params":{
      "name":"list_connected_mobiles",
      "arguments":{}
    }
  }'
Send after approvalcurl
curl -X POST 'https://mcp.smsmobileapi.com/mcp' \
  -H 'Authorization: Bearer YOUR_ACCESS_TOKEN' \
  -H 'Content-Type: application/json' \
  --data '{
    "jsonrpc":"2.0",
    "id":2,
    "method":"tools/call",
    "params":{
      "name":"send_sms",
      "arguments":{
        "recipient":"+15551234567",
        "message":"Your appointment is confirmed.",
        "idempotency_key":"appointment-8421-confirmation",
        "confirm":true
      }
    }
  }'

SECURITY MODEL

Built for actions on real communication channels

  • Every request is isolated by the authenticated SMSMobileAPI account.
  • Dashboard endpoint switches remain authoritative and can disable individual capabilities.
  • Send tools require explicit confirmation, E.164 validation and an idempotency key.
  • OAuth API keys are encrypted at rest; access tokens are stored only as hashes.
  • Rate limits separate read operations from SMS and WhatsApp sending.
  • Audit logs store tool, outcome and duration—not message bodies or credentials.

OPERATIONAL NOTES

What developers should expect

  • Asynchronous delivery. A successful send means the job was accepted; the connected mobile completes delivery afterward.
  • Mobile permissions matter. Incoming SMS and call activity must be enabled in the Android app before it can be synchronized.
  • WhatsApp retrieval has two steps. Request synchronization, then list received messages.
  • International numbers. Send tools accept E.164 numbers such as +15551234567.
  • No bulk-send tool. MCP deliberately exposes one confirmed recipient per send call.

SERVICE ENDPOINTS

Discovery and monitoring

MCP
https://mcp.smsmobileapi.com/mcp
OAuth metadata
https://mcp.smsmobileapi.com/.well-known/oauth-authorization-server
Protected resource
https://mcp.smsmobileapi.com/.well-known/oauth-protected-resource
Health
https://mcp.smsmobileapi.com/health