Integration

Vonage Applications integration

Vonage Application API v2: list, read, create, update and delete the Vonage applications of an account. An application holds the webhook URLs and the public key Vonage needs for the Voice, Messages, RTC (Client SDK), Verify, Meetings, Video and Network APIs, and the application JWTs of those APIs are signed with its private key. A private key Vonage generates is never returned here: send your own public key, or generate a new key pair in the Vonage API Dashboard. Linking a phone number to an application is done with the update_number tool of the Vonage integration. Authentication is HTTP Basic with the account API key as user name and the API secret as password, both shown in the Vonage API Dashboard.

Connect Vonage Applications How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Vonage Applications

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.

create_applicationCreate applicationPOSTAgents: ask firstCreates a Vonage application with its webhook URLs per product (voice, messages, rtc, verify, meetings, video, network_apis, vbc). Send public_key: a key pair Vonage generates has its private key withheld from this result.
delete_applicationDelete applicationDELETEAgents: ask firstDeletes a Vonage application by id. Vonage states this cannot be undone. Answers with no content on success.
get_applicationGet applicationGETAgents: ask firstReturns one Vonage application by id: name, public key, privacy setting, and each product capability with its webhook URLs, HTTP methods, timeouts and settings.
list_applicationsList applicationsGETAgents: ask firstLists the Vonage applications of the account, page by page: id, name, public key, and each product capability with its webhook URLs and settings.
update_applicationUpdate applicationPUTAgents: ask firstUpdates a Vonage application, replacing it with what is sent. Read it with get_application first and send back name, public_key and every capability to keep, with the change applied.

Use Vonage Applications from Claude Code, Cursor or Codex

Connect Vonage Applications in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Vonage Applications 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 Applications

Create your workspace
Sign up free. Nothing to install.
Connect Vonage Applications once
Add your Vonage Applications 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.