Skip to main content

MCP connector for AI assistants

MCP (Model Context Protocol) is a way to give an AI assistant access to an external service. With the SMS-Docs connector you can send messages and check their delivery right from a chat: "send the customer a verification code", "did yesterday's message arrive?", "how much is left on the account?".

Works with any MCP-capable client: Claude Desktop and Claude Code, ChatGPT, Cursor, VS Code, n8n and others.

Connector address​

https://mcp.alphasms.net/mcp

The transport is Streamable HTTP. You do not need to run a server of your own — the connector is already live.

Connecting​

Get an API key in your personal cabinet: Settings → API → Add. The key is shown once, so copy it right away.

Add the connector to your assistant's configuration:

{
  "mcpServers": {
    "sms": {
      "type": "http",
      "url": "https://mcp.alphasms.net/mcp",
      "headers": {
        "Authorization": "Bearer ВАШ_API_КЛЮЧ"
      }
    }
  }
}

The key travels in the header and is not stored anywhere: the connector passes it straight to the platform API and keeps neither keys nor your messages.

What it can do​

Read — available immediately:

  • account balance;
  • registered sender names and the status of each;
  • the status of a sent message, decoded into plain language;
  • an HLR lookup of a phone number.

Send — always with confirmation:

  • SMS;
  • Viber, including image, link and button;
  • Viber cascade with an SMS fallback when Viber is not delivered;
  • RCS;
  • a voice call that reads out your text;
  • WhatsApp;
  • one-time verification codes.

The full parameter list is on the Connector tools page.

Why sending requires confirmation​

Sending spends money from your account, so it has two locks.

First, every sending tool requires an explicit confirmation parameter. The assistant cannot set it on its own initiative — the tool description states plainly that it may only be set after a human agrees.

Second, the connector cannot do bulk campaigns, and it never will. One call is one message to one number. A tool that could blast your whole contact list is too dangerous in the hands of a model that has just read someone else's text and taken it for an instruction. Bulk campaigns belong in the cabinet.

How this differs from the regular API​

In substance, not at all: the connector calls the same https://alphasms.net as any other integration of yours. The difference is who composes the request. The regular API is called by your code; the connector is called by an assistant you briefed in words.

Sending goes through the asynchronous endpoint: the message is queued and the response carries an identifier, not a delivery status. The status is requested separately, once the operator reports it.

Limits​

  • One call is one message. Bulk campaigns are not supported.
  • The sender name must be registered in advance; registration takes 7–14 business days.
  • The reply to a send is an identifier, not proof of delivery. The operator's report can take up to several hours.
  • Tariff changes, address books and sender name registration are not available through the connector — those live in the cabinet.