Integration

Vonage Subaccounts integration

Vonage Subaccounts API (beta, restricted availability: Vonage enables it on request through the account manager, and Vonage Partners have it automatically): list, create, rename, suspend and reactivate the subaccounts of a primary Vonage account, move balance or credit between the primary account and a subaccount, list those transfers, and move a phone number from one account to another. Transfers move real money or credit and number transfers move live numbers. The secret of a new subaccount is never returned here. Authentication is HTTP Basic with the PRIMARY account API key as user name and its API secret as password, both shown in the Vonage API Dashboard.

Connect Vonage Subaccounts How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Vonage Subaccounts.Built from the 9 Vonage Subaccounts tools below, on the connection you add once.

What you can do with Vonage Subaccounts

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Each badge shows the default agent permission of an endpoint (allowed: an agent calls it without asking; ask first: you are asked before an agent calls it, when the agent or chat asks permission for sensitive actions; never: no agent may call it), which every user can change endpoint by endpoint in their credential settings.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Subaccount, 4 operations

create_subaccountCreate subaccountPOSTAgents: ask firstCreates a subaccount under the primary account and returns its API key (id). Vonage generates its API secret, which is withheld here. It shares the primary balance unless use_primary_account_balance is false.
get_subaccountGet subaccountGETAgents: ask firstReturns one subaccount by its API key: name, creation time, suspended flag, whether it shares the primary balance, and its balance and credit limit (null when the balance is shared).
list_subaccountsList subaccountsGETAgents: ask firstLists the subaccounts of the primary account with their API key (id), name, suspended flag, balance and credit limit, plus the primary account's own balance and the totals across all accounts.
update_subaccountUpdate subaccountPATCHAgents: ask firstRenames, suspends or reactivates a subaccount, or gives it its own balance (Vonage: cannot be undone). Send at least one of name, suspended, use_primary_account_balance; fields left out keep their value.

Balance transfer, 2 operations

list_balance_transfersList balance transfersGETAgents: ask firstLists the balance transfers between the primary account and its subaccounts from start_date on: id, amount, from and to account keys, reference and time.
transfer_balanceTransfer balancePOSTAgents: ask firstMoves money (account balance) between the primary account and one of its subaccounts, either way; subaccount to subaccount is not supported. Answers the transfer record.

Credit transfer, 2 operations

list_credit_transfersList credit transfersGETAgents: ask firstLists the credit transfers between the primary account and its subaccounts from start_date on: id, amount, from and to account keys, reference and time.
transfer_creditTransfer creditPOSTAgents: ask firstMoves part of the credit limit Vonage granted between the primary account and one of its subaccounts (either way). This changes what each account can spend. Answers the transfer record.

Phone number, 1 operation

transfer_numberTransfer numberPOSTAgents: ask firstMoves a Vonage phone number from one account to another (the primary account or one of its subaccounts): the number changes owner. Answers the number, its country, and the from and to account keys.

Use Vonage Subaccounts from Claude Code, Cursor or Codex

Connect Vonage Subaccounts in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Vonage Subaccounts operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Vonage Subaccounts

Create your workspace
Sign up free. Nothing to install.
Connect Vonage Subaccounts once
Add your Vonage Subaccounts connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.