Integration

VoxApp integration

VoxApp runs AI voice assistants for businesses. Start an outbound phone call, a web call link or a meeting link with one of your assistants, send an SMS or an email through an assistant, queue batches of up to 1,000 calls, SMS or emails and read each batch's progress, read a call's transcript, summary, sentiment and structured output, create and update contacts, and subscribe webhooks to events such as call.completed. Assistants themselves are configured in the VoxApp dashboard. Authentication is OAuth 2.0 client credentials: create an OAuth2 client in my.voxapp.com under Settings, Developers, and its client id and secret are exchanged for a Bearer token.

Connect VoxApp How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in VoxApp.Built from the 24 VoxApp tools below, on the connection you add once.

What you can do with VoxApp

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.

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

Call, 5 operations

find_callFind callGETLooks up one call by call_id, or by email_id (the source_record_id the call was started with), and returns it with output_*, form_* and meta_* keys flattened. Pass one of the two.
get_callGet callGETReturns the full record for a single call, including transcript, summary, structured output, sentiment, and recording URL when available.
list_recent_call_outputsList recent call outputsGETReturns recent calls that carry a summary, structured output, analysis or form data, flattened into output_*, form_* and meta_* keys. VoxApp does not document how many calls it returns.
list_recent_callsList recent callsGETReturns only the 3 most recent calls in completed or failed status, with transcript and summary. Filter by assistant_id. Use get_call for a known id.
start_callStart callPOSTStarts a real outbound phone call from an assistant at once. Give assistant_id plus one of contact_id, phone_number or contact (with a phone). Read the result later with get_call using call_id.

Assistant, 3 operations

get_assistantGet assistantGETGets one assistant's configuration by id: name, description, status, voice and LLM settings, first message, maximum call duration.
list_assistant_namesList assistant namesGETLists assistants with id and name only. Use an id as assistant_id; list_assistants returns full configuration.
list_assistantsList assistantsGETLists every assistant in active status with its configuration: name, voice and LLM provider, first message, maximum call duration and whether it extracts structured output. Use an id as assistant_id.

Contact, 3 operations

create_contactCreate contactPOSTCreates a contact; if one already matches on phone, email or external_id, that contact is returned instead. Creating one fires the contact.created webhook.
list_recent_contactsList recent contactsGETReturns only the 3 most recently created contacts (VoxApp offers no full contact listing or search).
update_contactUpdate contactPUTUpdates a contact. VoxApp requires first_name on every update: send the current first name if it does not change. metadata keys are merged; the docs do not say whether other omitted fields are kept.

Call batch, 2 operations

get_call_batchGet call batchGETGets the progress of a call batch: status (pending, processing, completed, failed or cancelled) and total, pending, completed and failed counts.
start_call_batchStart call batchPOSTQueues up to 1,000 real outbound calls from one assistant at once. Returns batch_id: read progress with get_call_batch.

Email batch, 2 operations

get_email_batchGet email batchGETGets the progress of an email batch: status (pending, processing, completed, failed or cancelled) and total, pending, completed and failed counts.
send_email_batchSend email batchPOSTQueues up to 1,000 real emails from one assistant at once. Returns batch_id: read progress with get_email_batch.

Sms batch, 2 operations

get_sms_batchGet sms batchGETGets the progress of an SMS batch: status (pending, processing, completed, failed or cancelled) and total, pending, completed and failed counts.
send_sms_batchSend sms batchPOSTQueues up to 1,000 real SMS from one assistant at once; the assistant must have an SMS template. Returns batch_id: read progress with get_sms_batch.

Webhook, 2 operations

create_webhookCreate webhookPOSTSubscribes an HTTPS URL to one VoxApp event (for example call.completed); VoxApp then POSTs each event to it. The signing secret is not passed on, so deliveries cannot be verified: use a secret, unguessable URL.
delete_webhookDelete webhookDELETEDeletes a webhook subscription; VoxApp stops posting its event to the URL.

Email, 1 operation

send_emailSend emailPOSTSends one real email at once from the assistant to a contact, given by contact_id or contact. The contact must have an email address.

Identity, 1 operation

get_current_identityGet current identityGETReturns the user and tenant (workspace) the current credential authenticates as. Use it to check the connection.

Meeting link, 1 operation

create_meeting_linkCreate meeting linkPOSTReturns the assistant's stable meeting URL (an in-browser meeting with the assistant). The URL persists: calling again returns the same link.

Sms, 1 operation

send_smsSend smsPOSTSends one real SMS at once using the assistant's SMS template (the assistant must have one configured). Give assistant_id plus contact_id, phone_number or contact. Returns sms_id.

Web call, 1 operation

create_web_call_linkCreate web call linkPOSTCreates a single-use URL that opens an in-browser voice call with the assistant; nothing is sent to the contact. Optionally attach a contact (contact_id or contact) for personalised context.

Use VoxApp from Claude Code, Cursor or Codex

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

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