The MCP server is a thin layer over your VertexSMS account, so your account's own rules apply to everything an assistant sends. This page lists what to expect.
Volume and sending speed
The MCP server does not cap how many messages you send. Sending speed is limited per account, and the limit is set individually for each customer. To change it, contact support.
Requests that arrive without valid credentials are limited per IP address (typically 20 per minute) and answered with RATE_LIMITED; see Errors.
Accepted is not delivered
send_sms returns queued once VertexSMS has accepted the message for processing. Account rules can still stop it afterwards, for example opt-outs, duplicate protection, insufficient balance or Sender ID restrictions. Use get_sms_status to see the outcome.
Sender IDs
Which Sender IDs you may use depends on your account and on the destination country, and the rules differ from customer to customer. Alphanumeric Sender IDs submitted with register_sender_id go through manual review. Mobile numbers registered with register_msisdn_sender are confirmed by a PIN that VertexSMS sends to that number.
Opt-outs
Opt-outs are applied automatically on the VertexSMS side. A message to a number that opted out is accepted and then not delivered, so check its status if delivery matters.
Acceptable use
Messages sent through the MCP server must comply with applicable law and the VertexSMS Terms. An assistant acts on your behalf with your account, so you are responsible for what it sends. Tools that send messages or spend money ask for confirmation in MCP clients that support it.
What the server keeps
The MCP server does not store your messages. Operational logs do not contain message text, and phone numbers in logs are masked. Your token is forwarded to the VertexSMS API and is not shared between sessions. See the privacy policy.