Integration

Vida integration

Vida runs AI phone, SMS and email agents for businesses. Queue outbound calls, text messages and emails from an agent, send a message to an agent from your own platform, read conversations and their messages, give the agent extra context about a person, manage Contacts and Contact Lists, and create, run, inspect and cancel agent Tasks and task batches. Also manages webhook destinations and reads phone numbers, conversation logs, account details and usage statistics. Agent configuration and publishing, computer agents, SIP, phone number purchase, billing, reseller and organization administration, white-label domains, templates, experiments and API token routes are not included. Authentication is a Vida API token sent as the token query parameter.

Connect Vida How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Vida

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.

Task, 6 operations

cancel_tasksCancel tasksPOSTAtomically cancel pending Tasks without deleting their audit history. Provide exactly one selector: taskIds, batchId, or allPending=true.
create_taskCreate taskPOSTCreates communication, scheduled, or Computer Agent work. Computer Tasks run only on provisioned Computer Agents and preserve their complete work in a linked conversation.
delete_taskDelete taskDELETEDeletes a non-retry Task and its schedule when applicable. Active Computer Agent work is stopped first.
get_taskGet taskGETRetrieve one Task and all of its attempts. When the Task has an associated room, chatRef links directly to its scoped Vida chat.
list_tasksList tasksGETRetrieve Tasks for the current organization. Each retry cadence remains one Task; attemptHistory contains its individual attempts.
update_taskUpdate taskPOSTUpdates a Task by ID. Repeating and cronOneOff Tasks support title, taskContext, state, and cronSchedule. Computer Tasks and retryable communication Tasks can only be canceled.

Contact, 5 operations

delete_contactDelete contactDELETEPermanently deletes the Contact identified by id from the selected organization.
get_contactGet contactGETReturns one Contact of the organization by its Contact id, with its contact details, Contact List memberships and custom fields.
search_contactsSearch contactsGETSearches the organization's Contacts by free text (name, email or phone) or by exact phone, email, status, source, lead source, Contact List or custom field value, one page at a time (page from 1, pageSize up to 100).
update_contactUpdate contactPATCHRecursively merges allowed Contact fields. Explicit null removes a field; arrays and scalars replace.
upsert_contactUpsert contactPOSTCreates a Contact or updates the matching one, and returns the stored Contact. Pass id or target to update a person, or phone or email to create one when none matches. Top-level fields sent replace current values; update_contact merges nested ones.

Contact list, 4 operations

add_contact_to_listAdd contact to listPOSTAdds a Contact to a Contact List, creating the List when its first Contact is added. Adding a Contact already in the List refreshes its membership timestamp.
list_contact_list_membersList contact list membersGETReturns one page of the Contacts in a Contact List (page from 1, pageSize up to 100), sorted by updatedAt, createdAt, id, name, email or phone.
list_contact_listsList contact listsGETReturns the distinct persisted Contact List labels for the organization.
remove_contact_from_listRemove contact from listDELETERemoves a Contact from a Contact List (every membership entry of that Contact with the List's label). Objective state stored under the same name is left in place; remove_contact_from_objective removes both.

Conversation, 3 operations

get_conversationGet conversationGETReturns one authorized conversation using the roomId and uuid values returned by list_conversation_logs.
get_conversations_batchGet conversations batchPOSTReturns up to 200 authorized conversations in one request. Use the roomId and uuid values returned by list_conversation_logs.
list_priority_inboxList priority inboxGETLists the conversation rooms of the agent's priority inbox, each with the other party, the last message and its time. Pass pagination=true with page and pageSize to page through them.

Log, 3 operations

list_contact_logsList contact logsGETReturns a Contact's recent activity (calls, texts, emails), newest first and without full transcripts, filtered by time range, type, event type or direction. Entries with a roomId and uuid can be opened in full with get_conversation.
list_conversation_logsList conversation logsGETReturns authorized conversation logs for a time range.
list_task_logsList task logsGETReturns a Task's communication logs, newest first, without full transcripts. Each entry's conversationRef carries the roomId and uuid to pass to get_conversation for the full conversation and its transcript when available.

Message, 3 operations

list_recent_messagesList recent messagesGETReturns the most recent messages across all inboxes, each with sender, recipient, text, channel, call details (duration, direction, summary, dialog) and the AI lead rating.
list_room_messagesList room messagesGETReturns every message of one conversation room (a roomId from list_priority_inbox or list_recent_messages), with sender, recipient, text, time, delivery status and attachments.
send_message_to_agentSend message to agentPOSTSend a message from your platform to an agent. Must pass outboundMessageWebhookUrl or configure on the organization to receive agent responses. Reseller or partners only.

Task batch, 3 operations

create_task_batchCreate task batchPOSTCreate up to 10,000 Tasks from either an explicit tasks array or a Contact List plus one Task template. Each Task uses the same fields and retry contract as create_task.
get_task_batchGet task batchGETFetch the creation status of an asynchronous Task submission. Status records are available for seven days.
list_task_batchesList task batchesGETList recent server-generated submission batches. Single-task batches are excluded unless includeSingles is true.

Webhook, 3 operations

add_webhookAdd webhookPOSTAdds a webhook destination that Vida posts events of the given type to.
list_webhooksList webhooksGETList all your existing webhook destinations.
remove_webhookRemove webhookDELETERemove an existing webhook destination.

Context, 2 operations

add_contextAdd contextPOSTInjects additional information context your agent can use in conversations with a specific person.
get_contextGet contextGETFetch additional information context stored for conversations with a particular person.

Run, 2 operations

list_task_runsList task runsGETReturns paginated terminal run summaries for one repeating or cronOneOff Task.
run_taskRun taskPOSTStarts one repeating or cronOneOff Task immediately or when due. A 202 response means the run was accepted, not completed.

State, 2 operations

enroll_contact_in_objectiveEnroll contact in objectivePATCHPuts a Contact in the Contact List listName (one per ongoing objective, e.g. renewals) and merges the body into its customFields under that name: objects merge, arrays and values replace, null removes a field. Records phase, next action or outcome.
remove_contact_from_objectiveRemove contact from objectiveDELETERemoves a Contact from the Contact List named listName and deletes its objective state stored in customFields under that name. Use it once the objective is complete or abandoned.

Account, 1 operation

get_accountGet accountGETReturns the account the API token belongs to (id, username and details). Call it first to see which account the token acts on.

Daily count, 1 operation

get_daily_task_countsGet daily task countsGETGet the organization’s current daily call, text, and total Task counts.

Junk conversation, 1 operation

list_junk_inboxList junk inboxGETLists the conversation rooms of the agent's junk inbox, each with the other party, the last message and its time. Pass pagination=true with page and pageSize to page through them.

Limit, 1 operation

get_task_limitsGet task limitsGETRetrieve the org’s current task limits configuration. Business hours use a timezone plus grouped windows; days are 0 (Sunday) through 6 (Saturday).

Outbound call, 1 operation

queue_outbound_callsQueue outbound callsPOSTQueue call Tasks for one target or up to 10,000 targets.

Outbound email, 1 operation

queue_outbound_emailsQueue outbound emailsPOSTQueue email Tasks for an email-enabled agent account. Pass target or to/cc/bcc for one email, or use up to 10,000 targets for separate emails.

Outbound sms, 1 operation

queue_outbound_smsQueue outbound smsPOSTQueue SMS Tasks for one target and message or up to 10,000 targets.

Phone number, 1 operation

list_phone_numbersList phone numbersGETReturns phone numbers assigned to the selected agent account and identifies its primary number.

Task stats, 1 operation

get_task_statsGet task statsGETGet Task counts by state and conversion results for each attempt number.

Usage, 1 operation

get_usage_statsGet usage statsGETReturns usage statistics of the account for the current or previous billing period, or between two dates, optionally as a time series and with costs.

Use Vida from Claude Code, Cursor or Codex

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

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