VertexSMS LLM-readable site index
We use cookies to improve your experience on this site and serve more relevant content to you. By continuing to browse our site you agree to our use of cookies, revised Privacy Policy and Terms of Service.  More information about cookies
docs · two doors

Read the docs.
Build something good.

Two ways to integrate with VertexSMS — pick the one that fits your workload.

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? We'll point you at the right one.

If you write application code, use the REST API. If you want an AI assistant to use VertexSMS for you, use the MCP server. MCP is a thin wrapper on the same REST API.