Skip to navigation

Connect Conversive MCP

Connect Conversive to your AI assistant to send SMS, WhatsApp and RCS messages and check your credit balance through chat. Your Conversive API key stays on the Conversive server and is never shared with the AI.

There are two ways to connect:

  • Sign in with Conversive (OAuth) for Claude.ai, Claude Desktop and Claude Code.
  • Personal access token for headless clients such as Retell, ElevenLabs and your own scripts.

Before you start

You need:

  • Your Conversive Platform username and password.
  • A Conversive role that allows the actions you want to perform, such as sending messages.
  • Permission to add custom connectors in your AI assistant. On Claude Team and Enterprise plans, an organization owner may need to add the connector first.

Conversive MCP server URL

Data centreServer URL
United Stateshttps://mcp.beconversive.com/mcp
European Unionhttps://eu-mcp.beconversive.com/mcp
Australiahttps://aus-mcp.beconversive.com/mcp

Use the URL for the data centre your Conversive account is hosted in.

1. Enable Conversive MCP

A Conversive account administrator must complete this step before anyone can connect an assistant.

  1. Open the Conversive admin app and go to [path].
  2. Turn on Conversive MCP.
  3. Choose which tool groups are available.
  4. Set the daily limit for messages sent through MCP (Phase 2).

2. Add Conversive to your AI assistant

Claude.ai and Claude Desktop

  1. In Claude, open Settings > Connectors > Add custom connector.
  2. Name it Conversive and enter the server URL for your data centre.
  3. Click Connect. A Conversive sign-in page opens.
  4. Sign in with your Conversive Platform username and password.
  5. Back in Claude, enable the Conversive connector for your chat.

If your organization manages Claude connectors, an organization owner must add Conversive in the organization’s connector settings first. Members can then find Conversive in their connectors and sign in individually.

For more on custom connectors, see Claude’s custom connector guide.


Claude Code

Run this command in your terminal. If your account is in the EU or Australia, replace the URL with https://eu-mcp.beconversive.com/mcp or https://aus-mcp.beconversive.com/mcp.

claude mcp add --transport http conversive https://mcp.beconversive.com/mcp

Then:

  1. Start Claude Code and run /mcp.
  2. Select conversive and choose Authenticate.
  3. Sign in with your Conversive Platform username and password in your browser.

Voice agents and scripts (Retell, ElevenLabs, custom code)

These clients can’t sign in through a browser, so they connect with a personal access token (PAT) created in the token dashboard.

Create a token

  1. Open the token dashboard at https://mcp.beconversive.com/tokens and sign in with your Conversive Platform credentials.
  2. Go to the Tokens tab and click + Create new secret key.
  3. Enter a label, such as Retell.
  4. Optionally set an expiry date, up to one year away.
  5. Choose an access level (see below).
  6. Click Create and copy the token straight away. It’s shown only once.

Access levels

Access levelTools the token can use
Full accessEvery tool, including tools added later
Read-onlyget_credit_balance and current_date_time_utc
CustomOnly the tools you select

Choose the narrowest level your client needs. For example, a voice agent that only sends booking confirmations needs send_message and current_date_time_utc.

Manage tokens

On the Tokens tab, use the icons on each token’s row:

  • Shield: change the token’s access level at any time.
  • Pencil: rename the token.
  • Red bin: revoke the token.

Configure your client

In your agent platform’s MCP settings, enter the server URL for your data centre and add the token.

Each token acts with the permissions of the user who created it. Treat it like a password.


ChatGPT and other assistants

ChatGPT support is coming soon. Other assistants that support remote MCP servers with OAuth may work, but they aren’t officially supported yet.

3. Sign in

When you connect from Claude, a Conversive sign-in page opens in your browser. Sign in with the same username and password you use for the Conversive Platform.

Your assistant then acts as you, and your Conversive role applies to every action. Your Conversive password and API key are never shared with the assistant.

Note: Claude sign-in sessions can use every tool your role allows. Choosing tools for Claude sign-in, as you can for tokens, is coming soon.

4. Test your connection

Step 1: Start a chat with Conversive turned on and ask:

“What is my Conversive credit balance?”

A successful response shows your account’s SMS/MMS credit balance.

Step 2: Try a send to your own number:

“Send an SMS to [your mobile number] saying: Testing Conversive MCP.”

Your assistant asks for permission before it sends. Check the recipient, channel, sender and message, then approve. Today, the message is sent as soon as you approve, so always review sends carefully.

To check your activity, open the Usage tab in the token dashboard. See MCP Usage & Pricing.

For everything you can do, see Explore MCP Tools.

Troubleshooting

1. Sign-in fails

Use the same username and password as the Conversive Platform. Check that you used the server URL for your account’s data centre.

2. The sign-in page shows “403 Forbidden”

The request was blocked before it reached the Conversive server.

3. A tool call returns “Denied”

The token’s access level doesn’t include that tool. On the Tokens tab, use the shield icon to change the access level, or create a new token. Tokens created before access levels were introduced have no scope and are denied every tool, so update or replace them.

4. You lost a token

A token can’t be shown again. Revoke it and create a new one, then update your client.

5. A send fails or is blocked

Your assistant shows the reason returned by Conversive. Check the Usage tab, where you can search errors by text.

6. Conversive doesn’t appear in the assistant

Restart the assistant, start a new chat, and check that the Conversive connector is turned on for the chat.

7. Your organization blocks custom connectors

Ask the administrator of your AI assistant’s workspace to allow the connection. Conversive settings can’t override restrictions in your AI assistant’s workspace.

8. An access token stopped working

Check whether the token has expired or been revoked, then create a new one and update your client.


Contact support

If these steps don’t fix the problem, contact: care@conversive.ai.