The interesting arguments here are the ones that are not the message text. msg_type distinguishes the kind of message being sent, image_path attaches an image, and schedule_date with schedule_time defers delivery, so a reminder or a timed campaign does not need a scheduler of your own wrapped around the call. Sender and receiver are per-call parameters rather than server configuration, which means one server can send on behalf of different numbers — and equally that nothing in the tool set constrains which number it sends as.
A single-tool SMS sender for the Aligo API.
- One call carrying more than the text: send-sms takes the sender and receiver, the message with a title and a msg_type, an image_path, a destination, and a schedule_date with a schedule_time for sending later.
An Aligo account able to send from the sender number you pass. No credentials are configured on the server; the sender and receiver are supplied per call.
One command plus a key — npx -y github:hongsw/aligo-sms-mcp-server mcp-server, then supply credentials