Actions Server — Connect with Claude

Learn how to connect to the Mobile Text Alerts Actions MCP server with Claude (web or Desktop)

This connector lets Claude send and schedule text messages and add subscribers and groups directly in your Mobile Text Alerts account. This performs real actions on your account, messages sent actually go out to your recipients and your plan's monthly credits and limits apply. Claude will ask you to confirm before sending/scheduling/creating; review the parameters before approving.

Setup and authentication

Plan availability

Custom (remote MCP) connectors are available on all plans — Free, Pro, Max, Team, and Enterprise. Free users can add one custom connector; paid plans allow multiple. On Team and Enterprise plans, an Owner must add the connector at the organization level first (Organization settings → Connectors), after which individual members connect and enable it themselves.

Add the connector (Claude web or Desktop):

1. Go to Settings → Connectors (shown as Customize → Connectors on some clients).

2. Click the + next to Connectors and choose Add custom connector.

3. Paste the Actions Server URL into the Remote MCP server URL field: https://mcp.mobile-text-alerts.com/mcp

4. Give it a name such as "Mobile Text Alerts." Advanced settings (OAuth Client ID/Secret) are optional and can be left blank.

5. Click Add. The connector now appears in your Connectors list with a "Custom" label.

Authenticate (pick one):

• OAuth 2.1 — recommended. Click Connect. You'll be redirected to the Mobile Text Alerts platform to log in. After logging in (or if you're already logged in), an authorization screen asks you to confirm connecting your account to Claude — click Allow. You're redirected back to Claude, and the Connect button changes to Configure.

• Bearer token (API key). Instead of OAuth, you can paste your Mobile Text Alerts API key into the connector's Authorization header. Generate a key from the platform dashboard under Settings → Developers/API (three-dot menu, top right). Either method authorizes Claude to act on your account, so treat the key like a password.

Configure connector

After connecting click Configure to see the registered tools and enable/disable individual ones or control when Claude may use them. Because every tool here performs a write action, Claude will generally confirm with you before it actually sends, schedules, or creates anything.

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). A vague "done" with no identifier — or no recipient count — is a sign the call may have silently failed; expand the tool-call block in the chat to inspect the exact parameters and response.

Confirmation of Configuration: You can confirm the connection with a quick sanity-check prompt: "Using the Mobile Text Alerts connector, list the available tools."

• Claude reports the four available tools: Send Message, Schedule Message, Add Subscribers, and Create Group. This confirms authentication succeeded.

Send Message: "Using Mobile Text Alerts, send a text to [phone] saying: 'Reminder — practice is at 6 PM tonight.'"

• The text is sent immediately and Claude confirms with a recipient count and message ID (e.g. "Message sent to 1 recipient"). Cost is 1 credit per SMS; a message with an attachment sends as MMS at 3 credits. Note: 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.).

Schedule Message: "Schedule a Mobile Text Alerts message to [phone] for next Monday at 9 AM that says: 'New blog post is live — read it here: example.com/post.'"

• The message is queued for the specified time (stored in UTC) rather than sent now; Claude confirms the scheduled date/time and target recipient(s). It can optionally repeat on a daily/weekly/monthly cadence if you ask.

Add Subscribers: "Add these subscribers to Mobile Text Alerts: Jane Doe, [phone]; and John Smith, [e-mail]."

• Claude confirms the subscriber(s) were added, returning name and number/email (and any group membership). Each subscriber needs at least a phone number or an email. If a number/email already exists on the account, the existing subscriber is updated rather than duplicated.

Subscriber actions are limited to 15 requests per 15 seconds at the account level; large imports should be batched.

Create Group: "Create a new Mobile Text Alerts group called 'VIP Customers.'"

• Claude confirms a new group (regular or adaptive) was created and returns its name and ID, which you can then target when sending or scheduling.

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