MCP connector for AI assistants

MCP (Model Context Protocol) is a way to give an AI assistant access to an external service. With the Interconnect-Solutions 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?".

URI: https://mcp.interconnect.solutions/mcp

The transport is Streamable HTTP: every call is a JSON-RPC request sent with the POST method. You do not need to run a server of your own — the connector is already live.

Authorization

Every call carries your API key in the Authorization header as Bearer <key>. The key travels straight to the platform API: the connector stores neither keys nor your messages.

Connection parameters

urlstringrequired The connector address: https://mcp.interconnect.solutions/mcp

typestringrequired Transport. Always http — Streamable HTTP

Authorizationheaderrequired Bearer and your API key from the personal cabinet: Settings → API → Add. The key is shown once, so copy it right away

Client configuration

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

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

Check the connection

curl -s https://mcp.interconnect.solutions/health
# {"ok":true,"domain":"interconnect.solutions","send_enabled":true}

send_enabled tells you whether sending is on for your domain. When it is off, the sending tools are not offered at all.

What the connector can do

Eleven tools. Read tools run straight away; sending tools always ask for confirmation first.

Reading

• balance — account balance and currency
• senders_list — registered sender names and their status
• message_status — status of a sent message, decoded
• hlr_lookup — HLR lookup of a phone number

Sending

• send_sms — one SMS
• send_viber — Viber with image, link and button
• send_viber_with_sms_fallback — Viber with an SMS fallback
• send_rcs — RCS
• send_voice — voice call reading out your text
• send_whatsapp — WhatsApp
• send_verification_code — one-time code

First call

Ask for the balance — it costs nothing and proves the key works.

JSON-RPC

{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
        "name": "balance",
        "arguments": {}
    }
}

cURL

curl -X POST 'https://mcp.interconnect.solutions/mcp' \
  -H 'Content-Type: application/json' \
  -H 'Authorization: Bearer ВАШ_API_КЛЮЧ' \
  --data-raw '{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "balance",
    "arguments": {}
  }
}'

Python

import requests

response = requests.post(
    "https://mcp.interconnect.solutions/mcp",
    headers={"Authorization": "Bearer ВАШ_API_КЛЮЧ"},
    json={
        "jsonrpc": "2.0",
        "id": 1,
        "method": "tools/call",
        "params": {
            "name": "balance",
            "arguments": {}
        }
    },
    timeout=30,
)

print(response.json())

Node.js

const response = await fetch("https://mcp.interconnect.solutions/mcp", {
  method: "POST",
  headers: {
    "Content-Type": "application/json",
    Authorization: "Bearer ВАШ_API_КЛЮЧ",
  },
  body: JSON.stringify({
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "balance",
      "arguments": {}
    }
  }),
});

console.log(await response.json());

Response

{
  "jsonrpc": "2.0",
  "id": 1,
  "result": {
      "content": [
          {
              "type": "text",
              "text": "{\"amount\": 152.4, \"currency\": \"EUR\"}"
          }
      ]
  }
}

Why sending requires confirmation

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

The two locks

Explicit confirmationper call Every sending tool requires confirm: true. The assistant cannot set it on its own initiative — the tool description states plainly that it may only be set after a human agrees

No bulk campaignsby design 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

Refusal response

A sending tool called without confirmation refuses and never touches the API.

{
  "refused": true,
  "reason": "Sending spends the client's money and needs an explicit confirmation",
  "how_to": "Ask the person, and pass confirm: true only once they agree"
}

How this differs from the regular API

In substance, not at all: the connector calls the same https://api.interconnect.solutions as any other integration of yours. The difference is who composes the request — your code, or 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.

Limits

What the connector will not do

One call — one message Bulk campaigns are not supported

Sender name registered in advance Registration takes 7–14 business days

No delivery proof in the reply The reply carries an identifier. The operator's report can take up to several hours — ask message_status for the outcome

Cabinet-only operations Tariff changes, address books and sender name registration are not available through the connector

The full parameter list is on the Connector tools page.