io.github.argosautomationPublished by GitHub account argosautomationv1.1.0Updated Nov 6, 2026
Send and read SMS and MMS from your own Android phone and number via Android Texter.
Connects an assistant to an Android Texter account so it can read, search, send and schedule real SMS/MMS from the user's own paired Android phone.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Follow the launch instructions in the repository.
Let Claude, Cursor, Windsurf, and any other MCP client send and read text messages through Android Texter.
Android Texter turns your own Android phone into an SMS and MMS gateway. Texts go out from the phone's real number over its carrier plan, and replies come back into your account. This server connects your AI assistant to that account, so you can say "text Sam that the meeting moved to 3pm" or "who replied to yesterday's broadcast?" and it happens on your phone.
atx_.node --version).The server runs with npx, so there is nothing to install by hand. Pick your client below and replace atx_YOUR_API_KEY with your key.
Open Settings > Developer > Edit Config (or edit claude_desktop_config.json directly: ~/Library/Application Support/Claude/ on macOS, %APPDATA%\Claude\ on Windows) and add:
Restart Claude Desktop. The Android Texter tools appear under the tools menu in a new chat.
Run claude mcp list to check that it connected.
Add to ~/.cursor/mcp.json (all projects) or .cursor/mcp.json (one project):
Add to ~/.codeium/windsurf/mcp_config.json (or Settings > Cascade > MCP Servers > View raw config):
Add to .vscode/mcp.json. VS Code asks for the key once and stores it securely:
Run npx -y android-texter-mcp as a stdio server with ATX_API_KEY in its environment.
On Windows, if your client cannot find npx, use "command": "cmd" with "args": ["/c", "npx", "-y", "android-texter-mcp"].
The same server is available as a single file from the dashboard (Settings > Integrations > Download Script). Save it anywhere and use "command": "node" with "args": ["/absolute/path/to/android-texter-mcp.js"] in place of the npx lines above.
Sending tools send real texts to real people from your number. Good clients ask before calling them; you can also set them to always ask in your client's tool settings.
Help: [email protected]. API reference: androidtexter.com/docs.
MIT
Source: mcp/README.md at commit e9196e6
List paired phones
List the Android phones paired to your Android Texter account. Each entry has its id, name, phone_number, status (online or offline), battery_level, last_seen, and its SIMs (slot, label, number) on dual-SIM phones. Texts are sent from these phones with their own numbers and carrier plans, so check that one is online before sending.
Takes no parameters.
List conversations
List your text conversations, most recent activity first. Each entry has phone (the other party, or a group's members joined by commas), last_message, last_direction, last_at, message_count, thread_type (direct or group), thread_ref, and the device it is on. Use get_conversation to read one in full.
viewlimitRead a conversation
Read the messages in the conversation with one phone number, newest first. Each message has direction (inbound or outbound), body, status, created_at, and media_url for picture messages. For a group conversation, pass the thread_ref from list_conversations.
pagelimitphonerequiredthread_refSearch messages
Search all of your texts, sent and received, for a word or phrase. Matches the message text, the phone number, and the contact's name. Newest first.
qrequiredpagelimitSend a text
Send a text message from one of your paired Android phones, using that phone's own number and carrier plan, to a real person. Confirm the recipient and wording with the user before sending. The call returns once the message is queued and pushed to the phone, not when it is delivered: use get_message_status with the returned message_id to follow it. Pass scheduled_at to send it later instead of now. Free plans have a daily sending limit.
phonerequiredmessagerequiredsim_slotdevice_idmedia_urlscheduled_atSend one text to many people
Send the same text to a list of phone numbers (up to 500), each as its own one-to-one message from your paired phone's own number. Only use this when the user has asked to text a list of people, and confirm the list and wording first: every recipient gets a real text. The message can be personalized from each recipient's contact record with {{name}}, {{first_name}}, {{last_name}}, {{full_name}}, {{company}}, {{city}} or {{state}}, and {{first_name|there}} gives a fallback when the field is empty. {{name}} is the name set by save_contact; first_name and last_name are only filled for contacts imported with those fields. Broadcasts send now and cannot be scheduled. Returns sent and failed counts and a message_id per recipient.
phonesrequiredmessagerequireddevice_idmedia_urlround_robinCheck a message's status
Check where an outbound message is: queued (waiting for the phone), sent (the phone handed it to the carrier), delivered, or failed. Pass the message_id returned by send_message or send_broadcast.
message_idrequiredList scheduled messages
List the messages that are scheduled to go out later and have not been sent or cancelled yet, soonest first. Use this before scheduling more, and to get the id needed by cancel_scheduled_message.
Takes no parameters.
Cancel a scheduled message
Cancel a message that is scheduled for a future send, so it never goes out. Only works while it is still pending; a message that has already been released to the phone cannot be recalled.
message_idrequiredList contacts
List or search your Android Texter contacts. Each contact has id, phone, name, email, company, notes, tags, and line type and carrier when a lookup has been run. Filter by tag to build a list for send_broadcast.
tagpagelimitsearchList contact tags
List every tag used on your contacts, for filtering list_contacts.
Takes no parameters.
Create or update a contact
Create a contact, or update the one that already has this phone number. Only the fields you pass are changed; fields you leave out keep their current values. Tags are added to the contact's existing tags, never removed.
nametagsemailnotesphonerequiredcompany90% 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.
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
{ "mcpServers": { "android-texter": { "command": "npx", "args": ["-y", "android-texter-mcp"], "env": { "ATX_API_KEY": "atx_YOUR_API_KEY" } } }}claude mcp add android-texter --scope user --env ATX_API_KEY=atx_YOUR_API_KEY -- npx -y android-texter-mcp{ "mcpServers": { "android-texter": { "command": "npx", "args": ["-y", "android-texter-mcp"], "env": { "ATX_API_KEY": "atx_YOUR_API_KEY" } } }}{ "mcpServers": { "android-texter": { "command": "npx", "args": ["-y", "android-texter-mcp"], "env": { "ATX_API_KEY": "atx_YOUR_API_KEY" } } }}{ "inputs": [ { "type": "promptString", "id": "atx-api-key", "description": "Android Texter API key", "password": true } ], "servers": { "android-texter": { "command": "npx", "args": ["-y", "android-texter-mcp"], "env": { "ATX_API_KEY": "${input:atx-api-key}" } } }}npm installnpm run typechecknpm run build # build/index.js, the npm binnpm run build:download # also copies it to the dashboard download in the Android Texter monorepo