Integration

Vonage Media integration

Vonage Media API (labelled beta by Vonage): list the media items stored on a Vonage account (audio files and other media used with Vonage APIs), read an item's metadata, download its file, or delete it. Files can hold recorded voices, so handle them as personal data. Listing covers the last 7 days unless a start time is given. Updating an item's metadata is left out because Vonage's own references disagree on how that call is made. 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; JWT application authentication is not supported here.

Connect Vonage Media How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Vonage Media

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.

Media item, 3 operations

delete_media_itemDelete media itemDELETEAgents: ask firstPermanently deletes a media item and its file from the Vonage account, by id as returned by list_media_items; the API offers no way to restore it. Answers with no content on success.
get_media_itemGet media itemGETAgents: ask firstReturns the metadata of one media item by id: original file name, MIME type, size, download count and limit, whether it is public, and its metadata strings and timestamps.
list_media_itemsList media itemsGETAgents: ask firstLists the media items of the Vonage account (audio files and other media used with Vonage APIs), newest first by default. Only items created in the last week are listed unless start_time is set.

Media file, 1 operation

download_media_itemDownload media itemGETAgents: ask firstDownloads the file of a media item by id and returns it as a stored file, with the MIME type Vonage sends. Each download is counted in times_downloaded, which max_downloads_allowed caps.

Use Vonage Media from Claude Code, Cursor or Codex

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

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