SMS Bridge

dev.workers.ronenmuzi.sms-bridgePublished by sms-bridge.ronenmuzi.workers.devOfficial publisherv1.0.0Updated Nov 5, 2026

Scoped Android SMS access for AI agents, with Hebrew invoices, OTP, and tracking.

VerifiedStreamable HTTPWeb executableCommunication & Collaboration

Overview

AI-generated overview

Remote MCP endpoint giving AI agents scoped access to Android SMS messages, including Hebrew invoices, OTP codes and shipment tracking.

What you can do
  • Read Android SMS messages through a hosted bridge, scoped to what the agent is allowed to see.
  • Work with Hebrew-language invoices received by text message.
  • Retrieve one-time passcodes delivered by SMS.
  • Follow shipment and delivery tracking messages.
  • No tool list is published, so the exact operations are not documented here.
When to use it
Useful when an assistant needs to act on text messages arriving on an Android phone, such as pulling OTP codes, reading Hebrew invoices, or checking delivery tracking updates, without direct device access.
Requirements
A remote MCP endpoint over streamable HTTP; no local install or package. A bearer token from the SMS Bridge admin UI (Agents tab), sent in the Authorization header. An Android phone connected to the SMS Bridge service is implied by the product description.
Before you install
The bearer token in the Authorization header grants access to SMS content and must be kept secret. Text messages routinely contain OTP codes, invoices and personal data, which are exposed to the agent and to the remote service; scope the agent's access narrowly and consider what the hosted bridge stores.

Installation

In SourceWeft

  1. Open SMS Bridge in the dashboard and add it to a workspace.
  2. Connect Authorization token 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.workers.ronenmuzi.sms-bridge%2Fsms-bridge/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.

{
  "mcpServers": {
    "sms-bridge": {
      "type": "http",
      "url": "https://sms-bridge.ronenmuzi.workers.dev/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

README

This repository has no README.

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

1
  1. v1.0.0LatestNov 5, 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.