Sms Mcp

com.mobile-text-alertsPublished by mobile-text-alerts.comOfficial publisherv1.2.0Updated Oct 26, 2026

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

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server from Mobile Text Alerts that lets an AI assistant send SMS messages and manage contacts through your account.

What you can do
  • Send SMS text messages to recipients from the assistant.
  • Manage contacts in the Mobile Text Alerts account.
  • The manifest lists no individual tools, so the exact set of actions is not documented here; the server is described only as enabling sending SMS and managing contacts.
When to use it
Useful when you want an assistant to send text messages or keep a contact list up to date through a Mobile Text Alerts account, for example for customer or team notifications, without building your own SMS integration.
Requirements
A remote MCP endpoint at mcp.mobile-text-alerts.com over streamable HTTP; no local package or runtime is needed. OAuth authentication is required, so you need a Mobile Text Alerts account and must complete the OAuth sign-in flow. Network access to the endpoint is required.
Before you install
The server can send SMS messages and change contact data, so actions may reach real people and alter your account records. Sending texts may incur messaging costs on your Mobile Text Alerts plan. Contact details and message content are handled by Mobile Text Alerts as a third party. Review what the assistant is about to send before approving it.

Installation

In SourceWeft

  1. Open Sms Mcp in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.mobile-text-alerts%2Fsms-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "sms": {
      "type": "http",
      "url": "https://mcp.mobile-text-alerts.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.2.0LatestSep 16, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.