Actions Server — Connect with Replit

Learn how to connect the Mobile Text Alerts Actions MCP server to your Replit apps

Any agent or app you build in Replit can be connected to the Mobile Text Alerts Actions MCP server to quickly send texts, schedule messages, and manage subscribers directly, with no SMS infrastructure configuration. Add SMS to anything you build on Replit, with just a few lines of prompting.

This connector performs real actions on your account, messages sent actually go out to your recipients and your plan's monthly credits and limits apply.

Review parameters carefully before approving any send, schedule, or create action inside your Replit app.

Setup and authentication

Install the connector (self-serve flow)

1

Click the install button below

(Or paste this install link directly into your browser)

This brings you to the following Replit pages:

• If logged in to Replit: the integrations page with a pop-up prompting you to complete the installation.

• If not logged in to Replit: you will be directed to Replit's sign-in/sign-up page. Sign in if you have an account, or sign up — it's free.

2

Click "Test & save."

Once signed in, a pop-up appears to confirm the connection. No configuration is needed, click Test & save.

3

Click "Authorize Mobile Text Alerts."

Replit verifies the MCP server connection, and the same pop-up updates with a new button: Authorize Mobile Text Alerts.

4

Sign in to your Mobile Text Alerts account

Replit opens the Mobile Text Alerts platform for log in. After logging in, you need to authorize Replit to access your account by clicking Allow. Replit confirms the connection, and Mobile Text Alerts now appears under Integrations, ready to use in any of your projects.

Example prompts and expected results

The Actions Server exposes four tools: Send Message, Schedule Message, Add Subscribers, and Create Group. These are write actions, so a working call should return a confirmation plus an identifier (a message ID, subscriber ID, or group ID). If your responses do not contain an identifier, this is a sign the call may have silently failed; check your agent's tool-call logs to inspect the exact parameters and response.

Note for message sends:

• Cost is 1 credit per SMS; adding an image sends as MMS at 3 credits.

• Trial accounts and unverified sender numbers can only send approved/templated content until the number is verified. Recipients must have opted in, and messaging must follow carrier and SMS regulations (opt-out handling, TCPA, etc.).

Add SMS notifications to an app: "My project has a newSignup(user) function. When it fires, use Mobile Text Alerts to text me at [phone] with the new user's name and email."

• Once configured, each signup triggers a real text with a message ID confirming delivery. This is a common first step for builders who want a heads-up the moment something happens in their app, without building their own notification pipeline.

Send a test message: "Using Mobile Text Alerts, send a text to [phone] saying: 'Test alert from my Project — order #4821 just shipped.'"

• The text sends immediately, and you get a recipient count and message ID back (e.g., "Message sent to 1 recipient"). Useful for confirming your integration logic works before wiring it into real app events.

Schedule a reminder from a workflow app: "Schedule a Mobile Text Alerts message to [phone] for tomorrow at 9 AM that says: 'Reminder: your appointment is at 10 AM today.'"

• The message is queued for the specified time (stored in UTC) rather than sent immediately. This is a natural fit for booking or reminder apps built on Replit — schedule the text the moment the appointment is created, and let Mobile Text Alerts handle delivery.

Grow a subscriber list from an app's signup form: "A user just signed up in my app: Jane Doe, [phone]. Add her as a subscriber in Mobile Text Alerts."

• Your agent confirms the subscriber was added, returning their name and number/email (and any group membership). Each subscriber needs at least a phone number or an email. If the number/email already exists, the existing subscriber is updated rather than duplicated.

Subscriber actions are limited to 15 requests per 15 seconds at the account level; if your app imports subscribers in bulk, batch the requests.

Segment users: "Create a new Mobile Text Alerts group called 'Beta Testers' for the users signing up through my Project's waitlist form."

• Confirms a new group (regular or adaptive) was created and returns its name and ID — which your app can then target whenever it sends or schedules messages to that segment.

Known limitations

• Four actions only. The connector only supports Send Message, Schedule Message, Add Subscribers, and Create Group. It does not expose listing/searching subscribers, deleting subscribers, reading inbound replies, or pulling analytics/billing — those exist in the API but aren't part of this Actions toolset.

• Sends consume credits. 1 credit per SMS (160 characters, no attachment) and 3 credits per MMS (up to 1,550 characters plus a ~500 KB image). Your plan's monthly credits and limits apply.

• Trial / unverified-number restriction. Until your sending number is verified, you can only send approved/templated message content.

Support

Need additional help or have questions? Send an email to [e-mail] or use our support chat on mobile-text-alerts.com and indicate your question is about the Mobile Text Alerts MCP server.

Privacy policy