MCP server for SMS
An MCP server lets an AI assistant such as Claude or ChatGPT work with your SMS platform directly: sending messages, validating numbers or checking delivery statuses, without you writing any code. SMSBOX is building such a server; below you will find what the Model Context Protocol is, what it will make possible and what you can already automate today.
Want to send SMS from your own software or AI agent right now? That works today through the SMS API and the API documentation.
What is the Model Context Protocol?
MCP (Model Context Protocol) is an open standard that lets AI assistants use external tools. An MCP server exposes a set of clearly described actions — for example "send an SMS" or "check this number" — and the assistant picks the action that fits what you asked. The protocol has since been adopted by all major AI providers, which means the same server works with different assistants.
Think of it as a power strip: without MCP, every AI application has to be wired up to every service separately. With MCP, SMSBOX writes one server and any assistant that speaks the protocol can plug into it — with no integration work on your side.
What will it make possible?
These are the actions we want to open up first. They already exist as API functions; the MCP server simply makes them reachable in plain language.
Send SMS in plain language
Ask your assistant to send a message to a single number, a group or a full contact list — it drafts the message and shows it to you for confirmation.
Schedule reminders
Have appointment reminders queued automatically for tomorrow or next week, each at the right time for the contact concerned.
Check numbers
Have a list of numbers checked for validity and activity before you spend credits on sending.
Summarise delivery reports
Ask how many messages in a campaign arrived and which ones failed, and get a readable summary instead of a raw export.
Follow up on replies
Have incoming SMS replies read, summarised and sorted, so you only see the messages that need follow-up.
Check balance and usage
Ask for your credit balance or last month's usage, per subaccount if you use more than one.
What already works today: the REST API
There is no need to wait to automate SMS. The SMSBOX REST API sends and receives messages with a single HTTP request, and AI agents that can call functions themselves already work with it today. Delivery statuses and incoming messages reach your own software directly through webhooks.
Safety and control
An assistant that can send SMS on its own spends money and reaches real people. That is why we start from these principles:
- You keep final control: a send is shown first and only carried out after you confirm it. If you want a strict separation, give the assistant its own subaccount with its own credit balance.
- The connection uses an API key that you create yourself and can revoke at any time.
- Your contacts and messages stay on Belgian servers, in line with the GDPR — the MCP server changes nothing about that.
- Every send remains visible in your usual overviews and delivery reports, whether it came from your software or from an assistant.
Status and availability
The SMSBOX MCP server is in development and not available yet. We are building it on top of the existing REST API, so that everything you can do through the API today will also be possible from an AI assistant. Do you have a concrete use case in mind? Let us know — your use case helps decide which actions come first.
