Documentation | VertexSMS

REST API

The VertexSMS REST API for server-to-server integrations: send SMS and Viber messages, run HLR lookups, register Sender IDs, and read rates and operator metadata. Authenticate with an API token; standard JSON over HTTPS.

Best when your application calls VertexSMS from server code on a fixed schedule or in response to your own events.

Read the REST API docs

MCP server

The VertexSMS Model Context Protocol server lets AI assistants — Claude Desktop, Cursor, VS Code Copilot Chat, Claude.ai — use your VertexSMS account directly via tool calls. Bearer token or one-click OAuth 2.1 connect.

Best when an AI assistant needs to discover and use VertexSMS on demand without a hand-coded integration.

Read the MCP server docs

Not sure which to use?

If you are writing application code that calls VertexSMS programmatically, use the REST API. If you want an AI assistant — Claude, Cursor, or similar — to use VertexSMS for you, use the MCP server. The MCP server is a thin wrapper over the same REST API; it adds tool discovery and OAuth, and forwards every call to the API under the hood.