FireText MCP by usefulapi

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

• Connection: Runs in the cloud
• Transport: Streamable HTTP
• Category: Chat & email

Install

Pick the AI app you use, then copy the settings.

You need

• Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

https://firetext.usefulapi.io/mcp

claude mcp add --transport http firetext https://firetext.usefulapi.io/mcp

{
  "mcpServers": {
    "firetext": {
      "url": "https://firetext.usefulapi.io/mcp"
    }
  }
}

{
  "servers": {
    "firetext": {
      "type": "http",
      "url": "https://firetext.usefulapi.io/mcp"
    }
  }
}

https://firetext.usefulapi.io/mcp

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 6, 2026. The maker wrote them, not us; we show them as plain text.

• firetext_get_credit

  Number of SMS credits (messages) remaining on the FireText account or a sub-account. FireText: /credit.

• firetext_list_received_messages

  Inbound SMS received on the account's FireText numbers/keywords (messageID, sentTo, keyword, receivedFrom, receivedOn, message). Dates YYYY-MM-DD; from="last" returns only what is new since the last call. FireText: /receivedmessages.

• firetext_list_sent_messages

  Messages (campaigns) sent from the account: messageID, sentOn, sentTo (group), recipientCount, message. The messageID is what the delivery and click reports need. Dates YYYY-MM-DD. FireText: /sentmessages.

• firetext_get_sent_summary

  Totals for a date range: number of campaigns, recipients and credits used. FireText: /sentreport.

• firetext_list_scheduled_messages

  Messages queued for later sending (messageID, queuedOn, scheduledFor, recipientCount, sourceAddress, sendTo, message). FireText: /scheduledmessages.

• firetext_get_delivery_report

  Per-recipient delivery status of one sent message (mobile, names, messageSent, messageUpdate, status: Delivered / Declined / Buffered / Pending with Network / Rejected / Unconfirmed). Give the FireText message id OR the custom reference used when sending. FireText: /deliveryrepor

• firetext_get_click_report

  Link clicks for one sent message (mobile, names, clicked, userAgent). Only for messages that used FireText's Trackable SMS feature (otherwise the vendor answers URL error). FireText: /clickreport.

• firetext_get_contact

  Stored details of one contact by mobile number (firstname, lastname, mobile, customField1-3). FireText: /contactinfo.

• firetext_list_unsubscribed

  Contacts that opted out (names, mobile, custom fields, addedOn, unsubscribedOn, reason). Optional date range and group API id. FireText: /unsubscribed.

• firetext_list_keywords

  SMS keywords on the account (keywordID, number, keyword, reference). FireText: /keywords.

• firetext_send_sms

  WRITE, SPENDS MONEY: sends a REAL SMS to real phones and uses the account's SMS credits (one credit per 160 GSM characters per recipient; long and unicode messages cost more). Cannot be undone. At most 10 recipients per call; no groups, templates, scheduling or repeats. Only call

• firetext_subscribe_contact

  WRITE: adds a contact (by mobile number) to the FireText account, optionally into a group, or with update=true refreshes the names/custom fields of an existing contact. Does not send any SMS. A contact that opted out cannot be re-added this way (they must rejoin by SMS). FireText

• firetext_unsubscribe_contact

  WRITE: opts a contact out of the FireText account (all groups by default), so it no longer receives group messages. The contact can only rejoin by SMS. Does not send any SMS. FireText: /unsubscribe.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

• ✓ Pass

  Maker matches the repo

  The registry name was verified against the domain usefulapi.io (the registry checks domain ownership)

• … Not checked yet

  Still maintained

  We have not read this repo from GitHub yet

• … Not checked yet

  Has a licence

  We have not read this repo from GitHub yet

• ✓ Pass

  Endpoint responds

  Responded in 30 ms (HTTP 200)

• – Not applicable

  Sign-in with OAuth

  No sign-in needed

• ✓ Pass

  No hidden instructions in tool descriptions

  Read 13 tool descriptions and found no hidden instructions to the AI

Compared with others in Chat & emaili

• More stars than 0% of the other 1760 servers in this category
• Published to the registry more recently than 96% of the other 1760 servers in this category
• Basic checks equal to or better than 100% of the other 1760 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

README from the maker

{