Skip to main content
Glama

Server Details

The Mobile Text Alerts SMS MCP server enables your AI to send SMS messages & manage contacts

Ownership verified
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
Mobile Text Alerts

TDQS

A4.1/5.0

Scored across 10 tools

Disambiguation5/5

Each tool has a clearly distinct purpose: sending vs scheduling, webhook list/register/delete, onboarding status vs business-data submission, and subscriber/group operations are well separated. No two tools appear to compete for the same action.

Naming Consistency5/5

All tools use a consistent snake_case verb_noun pattern (add_subscribers, create_group, list_webhooks, send_message, etc.). The plural in add_subscribers reasonably reflects a bulk operation and does not break the overall convention.

Tool Count5/5

Ten tools is well within the ideal 3-15 range for an SMS account management server. Each tool covers a meaningful operation without bloat.

Completeness3/5

Core messaging, onboarding, sending numbers, and webhooks are covered, but the surface has notable gaps: subscribers can only be added (no list/remove), groups can only be created (no list/delete), and there is no message history or delivery-status lookup tool. These gaps will likely cause agents to hit dead ends for common administrative tasks.

Publisher details

Operator
Mobile Text Alerts · Publisher source
Vendor relationship
First-party · Publisher source
Restrictions
No setup restrictions

Available Tools

10 tools
add_subscribersAdd or Update SubscribersB
Destructive
Inspect

Add or update subscribers in Mobile Text Alerts (bulk operation)

Inputs: subscribers (required), createOnly. Returns: data, error, status, context, +4 more

create_groupCreate GroupB
Destructive
Inspect

Create a regular or adaptive group in Mobile Text Alerts

Inputs: name (required), hidden, settings, sortOrder, +3 more. Returns: data, error, status, context, +7 more

delete_webhookDelete WebhookA
Destructive
Inspect

Delete a registered webhook so Mobile Text Alerts stops sending its events to that URL. Use list_webhooks to find the id. Use this to clean up a webhook whose receiving URL has changed, or one that should not be receiving account events.

Inputs: webhookId (required). Returns: data, error, status, success, +1 more

get_onboarding_statusGet Onboarding StatusA
Read-only
Inspect

Check the current onboarding status of the user's account.

WHEN TO CALL:

  • At the start of every conversation to determine if onboarding is needed

  • Immediately after receiving an onboarding-related error from any core tool

  • After calling submit_business_data to see updated missing fields and progress

RESPONSE INTERPRETATION:

  • status: 'NEW' → No data collected yet; call submit_business_data with any available fields

  • status: 'BUSINESS_DATA_PENDING' → Partial data saved; guidance.fieldsNeeded lists what's still missing

  • status: 'SUBMITTED' → All data submitted, awaiting carrier approval (~1 business day); do NOT re-submit

  • status: 'ACTIVE' or 'MANUAL_REVIEW' → Account is ready; all core tools are available

The 'guidance.fieldsNeeded' array is computed dynamically from the stored draft — it always reflects exactly what's still missing. The 'progress' object tracks overall completion percentage.

Inputs: no named parameters. Returns: status, guidance, progress

list_sending_numbersList Sending NumbersA
Read-only
Inspect

List the phone numbers this account can send text messages from, whether each can send right now, and which one send_message uses by default (isDefault). Pass a number's number as send_message's from to send from it instead. A new account usually has a main toll-free number awaiting carrier approval plus a temporary trial number that only allows a small number of messages; once the main number is approved it becomes the default.

Inputs: no named parameters. Returns: data, error, status, context, +5 more

list_webhooksList WebhooksA
Read-only
Inspect

List the webhooks registered on the account: each one's id, event and receiving URL. Call this before register_webhook to avoid creating a duplicate, and to find the id needed by delete_webhook. Secrets are never returned.

Inputs: no named parameters. Returns: data, error, status, success, +1 more

register_webhookRegister WebhookA
Destructive
Inspect

Register a webhook so Mobile Text Alerts sends events to a URL you control — for example, to receive replies to messages sent with send_message.

EVENTS

  • message-reply: an inbound reply was received

  • delivery-status: a sent message's delivery status changed

  • message-send: a message was handed off for delivery

  • number-opt-in: a number opted in to a channel

THE SECRET Ask the human user to provide the secret — do not invent one. Tell them to store it outside this conversation (for example in Replit Secrets): the receiving app needs it to verify requests, and it cannot be retrieved from Mobile Text Alerts afterwards.

THE RECEIVING ENDPOINT MUST

  • Be reachable over HTTPS and respond with HTTP 200 (401 if the signature is invalid).

  • Verify the X-Signature header on every request: a lowercase hex HMAC-SHA256 of the RAW request body, keyed with the secret. Compute it over the raw bytes before any JSON parsing (e.g. express.raw() in Express) and compare in constant time. There is no timestamp or nonce, so signatures do not protect against replay.

Payload formats per event: https://developers.mobile-text-alerts.com/tutorials/webhooks

Always call list_webhooks first. Registering the same event and URL again creates a second webhook rather than updating the first, and both will receive every event. If one already exists, reuse it — or, to change the URL or secret, remove it with delete_webhook and register again.

Inputs: url (required), event (required), secret (required), alertEmail, +2 more. Returns: data, error, status, success, +1 more

schedule_messageSchedule Text MessageA
Destructive
Inspect

Schedule a message to be sent at a specific time in the future via Mobile Text Alerts API. Use this tool when you need to send a message at a later date/time rather than immediately. The message goes out from the account's default number (the one it last sent from) unless from names another; the response's sentFrom says which was used.

Inputs: to (required), message (required), scheduledDate (required), from. Returns: data, error, notice, status, +9 more

send_messageSend Text MessageA
Destructive
Inspect

Send a message immediately via Mobile Text Alerts API. Use this tool for messages that need to be sent right away. For scheduling messages to be sent at a future time, use the schedule_message tool instead. The message goes out from the account's default number (the one it last sent from) unless from names another; the response's sentFrom says which was used, and notice carries anything to tell the user, such as a send from a limited trial number. PREREQUISITE: User must complete onboarding first (status must be 'ACTIVE'). If this tool returns 'Onboarding Required' error, immediately call get_onboarding_status to begin the onboarding flow.

Inputs: to (required), message (required), from. Returns: data, error, notice, status, +7 more

submit_business_dataSubmit Business Registration DataA
Destructive
Inspect

Submit brand registration data for the onboarding process. All fields are optional — you can submit partial data and continue filling in the rest in subsequent calls.

USAGE PATTERN:

  1. Read user://current/onboarding_status to see the current status and any missing fields

  2. Collect fields conversationally (one or a few at a time — don't overwhelm the user)

  3. Call this tool with whatever fields you have collected so far

  4. Check the response: if 'missingFields' is present, continue collecting those fields and call again

  5. When all fields are provided, status transitions to 'SUBMITTED' automatically

  6. Re-read user://current/onboarding_status after each call to track updated missing fields

PARTIAL SUBMISSIONS:

  • This tool is fully idempotent and accumulates data across calls

  • Re-submitting a field updates it; other fields already collected are preserved

  • Status stays 'BUSINESS_DATA_PENDING' until all required fields are provided

COMPLETE SUBMISSION:

  • When all required fields are present, status becomes 'SUBMITTED'

  • Inform the user that carrier approval takes ~1 business day

  • Do NOT re-submit once status is 'SUBMITTED' or 'ACTIVE'

BLOCKED STATES:

  • Returns an error if status is already 'SUBMITTED' or 'ACTIVE'

Inputs: destinations, companyCountry, tollFreeVerificationForm. Returns: error, success, newStatus, nextSteps, +2 more

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      An MCP server that enables AI agents to send SMS, MMS, and WhatsApp messages, manage contacts, lists, and webhooks, and explore the Kudosity API through natural language.
      19
      53 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for sending SMS via the SMSPM API. Send transactional SMS from Claude Desktop, Cursor, Windsurf, Cline, or any MCP client.
      1
      32 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive MCP server for TELNYX integration, enabling AI assistants to send SMS messages, make voice calls, and handle incoming communications via webhooks.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources