Mobile Text Alerts SMS
officialMobile Text Alerts SMS is the official remote MCP server from Mobile Text Alerts, an SMS messaging platform for businesses and organizations. It connects any MCP-compatible AI assistant — Claude, ChatGPT, Cursor, and others — to your Mobile Text Alerts account, so you can send and schedule text messages, manage subscribers and groups, and complete carrier registration through conversation.
What can you do with Mobile Text Alerts SMS MCP?
- Send an SMS now — Ask your assistant to send a text message immediately to your subscribers through your Mobile Text Alerts account.
- Schedule a future message — Have your assistant schedule a message to be sent at a specific future date and time.
- Add subscribers in bulk — Ask your assistant to add or update multiple subscribers at once.
- Create a group — Have your assistant create a regular or adaptive group in Mobile Text Alerts.
Hosted MCP Server
npx add-mcp 'https://mcp.mobile-text-alerts.com/mcp'Installs into Claude Code, Codex, Cursor and more
Documentation
For the complete documentation index, see llms.txt. Markdown versions of documentation pages are available by appending
.mdto page URLs; this page is available as Markdown.
Actions MCP Server
Learn how to utilize Mobile Text Alert's Actions MCP Server
Mobile Text Alerts offers a robust and powerful Model Context Protocol (MCP) server, unlocking the capabilities to send and manage SMS messaging directly by an AI assistant. This server allows AI assistants and other applications to access your Mobile Text Alerts account from beyond our web and mobile app platforms.
Access the Server
Server URL
The Actions MCP server is a remote server hosted at the following URL:
https://mcp.mobile-text-alerts.com/mcp
Learn more about connecting to remote MCP servers.
Authorization
You can authenticate with the following methods:
OAuth (recommended)
The server adheres to the latest MCP specification and implements a fully compatible OAuth 2.1 flow with Dynamic Client Registration (DCR). Link your Mobile Text Alerts account simply by logging in and authorizing your AI assistant to access your account.
Bearer Token Authentication
The Actions MCP server also accepts a Mobile Text Alerts API key via the Authorization header using Bearer Token Authentication. By providing this key, you are implicitly authorizing your AI assistant or agent to access your Mobile Text Alerts account
See Get an API Key to learn how to get an API Key.
Tools & Usage
The Actions MCP server supports multiple tools, enabling your AI assistant access to the following actions with the Mobile Text Alerts API:
- Send Message - This sends a message immediately, for scheduling messages to be sent at a future time, use the Schedule Message tool (below).
- Schedule Message - Schedule a message to be sent at a specific future date/time.
- Add Subscribers - Add or update your subscribers in bulk.
- Create Group - Create a regular or adaptive group in Mobile Text Alerts.
See Actions Server — Connect with Claude if you will connecting Mobile Text Alerts Actions MCP server with Claude (web or Desktop).
Troubleshooting
Need additional help or have questions? Send an email to contact@mobile-text-alerts.com or use our support chat on mobile-text-alerts.com and indicate your question is about the Mobile Text Alerts MCP server.
Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.
Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.
Perform an HTTP GET request on the following URL with the ask and goal query parameters:
GET https://developers.mobile-text-alerts.com/ai/mcp-servers/actions-mcp-server.md?ask=<question>&goal=<user_goal>
ask is the immediate question: it should be specific, self-contained, and written in natural language.
goal is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with ask=how do I create an API token, a goal like automate deployments from our CI pipeline lets GitBook tailor the answer to that use case.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.
Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.