Sendveo for AI agents

Sendveo speaks the Model Context Protocol (MCP). Add it to Claude, Cursor, ChatGPT or any MCP-capable agent, then ask in plain language: list my numbers, connect this one, reply to that chat. The agent calls Sendveo for you.

What it is

The Sendveo MCP server is a small bridge between your AI assistant and your Sendveo account. It exposes the same actions as the API and the dashboard, as tools the assistant can call. Everything runs under your own account: you sign in with your Sendveo email and password, or, for a script or a command-line tool, you use an API key from your dashboard.

There are two ways to connect, and both expose the same tools. Hosted: paste one URL into the assistant and sign in, with nothing to install and no key to copy. Local: the assistant runs a small Sendveo command on your machine with an API key, which never leaves it.

What you can do

One tool per action, grouped as the guide groups them: numbers, messages, conversations, contacts, groups, health and profile, labels, webhook, billing. Operator features are not exposed: the server is limited to the account the connection belongs to.

connect_number, refresh_qr and reconnect_number accept an optional method. qr (the default) returns a QR to scan from WhatsApp under Linked devices, Link a device. code returns an 8-character code to type under Link with phone number: use it when you are on the same phone that holds the number and cannot scan the screen. Both expire and rotate, so ask for a fresh one if it stops working.

Option A: paste the URL and sign in (recommended)

Add Sendveo to your assistant as a remote MCP server. You need one value, the Sendveo MCP URL. There is nothing to install and no key to paste: your assistant opens a Sendveo page where you sign in and approve the connection.

https://mcp.sendveo.com/mcp

In Claude

1. Open Settings, then Connectors, and choose Add custom connector.
2. Paste the Sendveo MCP URL above and save. Your assistant finds the rest on its own.
3. A Sendveo page opens in your browser. Sign in with the email and password you use for the dashboard.
4. Read what the assistant is asking for and the address it will send you back to, then press Allow. Press Refuse and nothing is granted.

The assistant receives a connection tied to your account, carrying the permissions shown on that approval screen. It expires after an hour and renews itself quietly while the connection is in use. You never paste a key into the assistant, and nothing you approve reaches another account, the operator console, or your password.

To disconnect, remove the connector in your assistant. A connection you remove on the Sendveo side stops working immediately, for good.

If no sign-in page opens, check that the URL ends in /mcp. If your assistant reports that it could not reach the sign-in service, Sendveo is unreachable from your network, the same check as loading the dashboard.

ChatGPT, Cursor and other MCP-capable assistants use the same URL in their own remote MCP server settings, and sign you in the same way.

Option B: local (runs on your machine)

If you prefer to keep the key on your own machine, run the Sendveo MCP server locally. It needs Node.js 22 or newer. The assistant starts it with npx @sendveo/mcp and passes your key through the SENDVEO_API_KEY environment variable.

Add the block below to your assistant's MCP configuration. In Claude Desktop that is claude_desktop_config.json; in Claude Code run claude mcp add or edit .mcp.json; Cursor uses .cursor/mcp.json. The block is the same everywhere.

{
  "mcpServers": {
    "sendveo": {
      "command": "npx",
      "args": ["-y", "@sendveo/mcp"],
      "env": {
        "SENDVEO_API_KEY": "YOUR_SENDVEO_API_KEY"
      }
    }
  }
}

Replace the placeholder with your key, restart the assistant, and ask it to list your Sendveo numbers. If the server exits immediately, check that SENDVEO_API_KEY is set.

With an API key instead of signing in

Signing in is the normal way to use the hosted URL. If your tool cannot do that, a script, a curl call, or a client that only lets you set headers, the same URL also accepts a Sendveo API key sent as a bearer token. Each request is authenticated on that key alone and is limited to that key's account.

https://mcp.sendveo.com/mcp

Authorization: Bearer YOUR_SENDVEO_API_KEY

Scopes

Every connection carries scopes, and each tool needs one. When you sign in, the approval screen lists them in plain language before you press Allow. A new API key is granted every scope except the read-only shortcut, so it works with all tools out of the box. If a tool reports a missing scope, adjust the key under API keys in your dashboard, or connect again and approve the missing permission.

messages:manage, chats:read, chats:manage, contacts:read, groups:read and groups:manage were added on 16 September 2026. An API key created before that date has none of them and cannot be given them: create a new key in your dashboard, or reconnect the assistant and approve the permissions. Everything else keeps working on the old key.

Billing is read-only and is covered by numbers:read: there is no separate billing scope.

Safety

• Signing in never gives the assistant your password, and no API key is stored by the hosted server. Each request is authenticated with the credential it carries, and the server keeps none of its own.
• Every request is isolated to the account behind the connection. Operator features are not reachable through MCP.
• Rate limits apply, per key and per source. A 429 response means slow down and retry shortly.
• Treat the key like a password. Prefer a key scoped to what the assistant needs, and revoke it from the dashboard if it leaks.

Troubleshooting