Sparetext

dev.sparetextPublished by sparetext.devOfficial publisherv1.4.0Updated Oct 29, 2026

Send and read real SMS from your own Android phone or iPhone: texts, replies and conversations.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP server that lets an assistant send and read real SMS through your own Android phone or iPhone, including texts, replies and conversations.

What you can do
  • Send SMS messages from your own phone number
  • Read incoming texts, replies and conversation threads
  • Work with the phone's existing SMS conversations rather than a separate messaging account
When to use it
Useful when an assistant should text real people from your own phone number, or read and summarize SMS conversations, instead of using a separate messaging service.
Requirements
A remote endpoint at sparetext.dev over streamable HTTP; OAuth sign-in is required. A paired Android phone or iPhone is implied by the service's purpose. No environment variables or headers are declared.
Before you install
The server can send real SMS to real recipients and read your text messages, so it touches private conversations and can incur carrier messaging costs. Access is granted through OAuth to your account; review what the connection is allowed to do before authorizing.

Installation

In SourceWeft

  1. Open Sparetext 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/dev.sparetext%2Fsparetext/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": {
    "sparetext": {
      "type": "http",
      "url": "https://sparetext.dev/mcp"
    }
  }
}

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.4.0LatestOct 29, 2026

Score

83% 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
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.