What is an SMS MCP server?

An SMS MCP server exposes text messaging as tools an AI assistant can call through the Model Context Protocol: send a text, read replies, check delivery, record consent. You connect Claude, ChatGPT, Cursor or your own agent to its URL and approve in the browser. Unlike email, a text needs a registered sender number and the recipient's consent first, and the server checks STOP, quiet hours and the destination country before anything is billed.
Unitpost ·
The Model Context Protocol (MCP) is the standard AI assistants use to call outside tools. An SMS MCP server is one that offers texting: the assistant sees tools such as "send a text" and "list replies", and calls them when you ask in plain words.
What is an SMS MCP server, in plain words?
It's the plug between an AI assistant and a texting service. On its own, Claude or ChatGPT can write a text message but can't deliver it to a phone. Connect an SMS MCP server and the assistant can send it, from a number your business owns, and tell you whether it arrived. The service does the carrier work: routing, delivery receipts, opt-outs and the per-country rules.
What tools does it have?
On Unitpost, each tool maps to one REST API operation:
sms_sendsends one text, now or at ascheduled_attime;sms_getandsms_listread texts, sent and received, filtered by number, contact, tag or text;sms_statsreports delivery over a period;sms_consent_getandsms_consent_recordread and record a contact's consent;sms_templates_create,sms_campaigns_validateandsms_campaigns_sendhandle texts to a whole segment;sms_numbers_listshows the numbers and Sender IDs that can send.
The same server also has email tools, so one connection covers both channels.
What does an SMS MCP server need before the first text?
More than email does. Email needs a verified domain; a text needs:
- A paid plan. SMS isn't on the free plan; texts draw from the same monthly allowance as email.
- A brand. The legal business, its website and a contact. Carriers approve it.
- A sender. A toll-free or 10DLC number in the US, registered for a use case with sample messages, or a Sender ID where a country allows one.
- Consent. A record that each recipient agreed to hear from you. Marketing texts need express consent.
An agent can do most of this setup too, through the brand, quote and registration tools, but buying a number or a registration needs a key permission no preset includes, and the price is quoted before it's confirmed (SMS setup by API).
What rules does it enforce?
The server runs every tool call through the same checks as the REST API, so an assistant can't talk its way around them:
- STOP. A number that replied STOP is skipped, and STOP, START and HELP are answered automatically.
- Consent. A marketing text to someone without recorded express consent is refused.
- Quiet hours. Marketing texts wait for daytime in the recipient's time zone.
- Country reach. A destination the account can't text is refused before it's billed.
- Permissions. The connection only has the scopes you approved: an assistant allowed to read can't send.
Every tool that sends or changes data is marked as having real effects, so clients like Claude ask before calling it.
How is it different from an email MCP server?
The protocol and the connection are the same; the channel's rules differ. Email is cheap per message and checked against suppressions and bounces. Texts cost per segment, reach a phone that buzzes, and are regulated by carriers and consent law, so an SMS server is stricter about who can be messaged and when. What is an email MCP server? covers the email side.
How do you connect one?
Paste https://mcp.unitpost.com/mcp into your client as a custom connector or MCP server, sign in and approve. Let Claude or ChatGPT send texts walks through it without code. For an agent that answers replies as they come in, pair the server with the sms.received webhook (two-way SMS for agents).
