Introduction
SMSFabric sends and receives SMS through Android phones and SIM cards that you own. The phones run the SMSFabric app and connect to your account. You then send messages from the web portal, from your own code through the REST API or the Node SDK, or from an AI assistant through the MCP server.
Why use your own SIMs
Section titled “Why use your own SIMs”- Local numbers people recognise. Messages come from your real numbers, so replies reach you.
- Your carrier’s prices. You pay your SIM plan, not a per-message markup.
- No sender registration wait. A paired phone can send within minutes.
- More phones, more throughput. Add phones to a pool. If one goes offline, another takes over.
What you can do
Section titled “What you can do”- Send one message or up to 100 recipients in a single request, now or at a scheduled time.
- Follow every message from
queuedtodelivered, in the portal and by webhook. - Receive inbound SMS and forward it to your systems.
- Send one-time codes with built-in abuse protection (Verify).
- Run campaigns to contact lists, with templates, a throttle and quiet hours.
- Give each server its own API key with only the scopes it needs.
The parts of SMSFabric
Section titled “The parts of SMSFabric”| Part | What it is | Where |
|---|---|---|
| Customer portal | The web app where you manage phones, send messages, read logs and create keys | https://app.smsfabric.com |
| Android app | Turns a phone into a gateway that sends and receives SMS through its SIMs | Mobile app |
| iOS app | A companion: dashboard and alerts. It does not send SMS in the background | iOS companion |
| REST API | Everything the portal does, for your code | https://api.smsfabric.com, reference |
| Node SDK | A typed client for the API | @smsfabric/sdk |
| MCP server | Tools that let AI assistants send and read SMS | @smsfabric/mcp-server |
Follow the Quickstart to send your first message, or read How it works first.