Integration

LiveAgent integration

LiveAgent is a help desk for email, chat, call and social tickets. Create, read, update, postpone and delete tickets and read their messages, history and SLA; manage contacts, companies, contact groups, tags, canned messages and predefined answers; and read agents and their activity, departments, SLA levels, chats, calls, time reports and contact page visits. Account administration (agent creation and deletion, bans, devices, phone and SIP settings, custom buttons, filters, settings), file upload and ticket attributes are not exposed. Authentication is a LiveAgent API v3 key (v1 keys do not work), sent in the apikey header, plus your account subdomain (<subdomain>.ladesk.com).

Connect LiveAgent How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with LiveAgent

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.

Contact, 7 operations

create_contactCreate contactPOSTCreates a customer contact: first and last name, emails, phones, company, contact groups, job position, note, language, location and custom fields.
delete_contactDelete contactDELETEDeletes a contact. deleteTickets true also deletes all of the contact's tickets; false keeps the tickets.
get_contactGet contactGETReturns one contact with names, emails, phones, company, groups, job position, note, language, location, browser details and custom fields.
list_contact_page_visitsList contact page visitsGETLists the web pages a contact visited (title, URL, referrer, browser, date). An empty list can also mean the visit store failed (LiveAgent logs it).
list_contactsList contactsGETLists customer contacts with names, emails, phones, company, groups, city, country and creation dates. Filter with _filters; paginate with _page and _perPage.
replace_contactReplace contactPUTReplaces a contact: every field is set from the request, so send the complete contact. Use update_contact to change only some fields.
update_contactUpdate contactPATCHUpdates only the fields sent of a contact (names, emails, phones, company, groups, job position, note, language, location, custom fields).

Canned message, 5 operations

create_canned_messageCreate canned messagePOSTCreates a canned message (a saved chat reply) with its text and optional keywords, agent and department.
delete_canned_messageDelete canned messageDELETEDeletes a canned message.
get_canned_messageGet canned messageGETReturns one canned message: text, keywords, agent and department.
list_canned_messagesList canned messagesGETLists canned messages (saved chat replies) with their text, keywords, owning agent and department.
update_canned_messageUpdate canned messagePUTUpdates a canned message: text, keywords, agent and department.

Company, 5 operations

create_companyCreate companyPOSTCreates a customer company: name, emails, phones, contact groups, note, language, location and custom fields.
delete_companyDelete companyDELETEDeletes a company. deleteTickets true also deletes all of its tickets; false keeps the tickets.
get_companyGet companyGETReturns one company with its name, emails, phones, groups, note, language, location and custom fields.
list_companiesList companiesGETLists customer companies with name, emails, phones, groups, city, country and dates. Filter with _filters; paginate with _page and _perPage.
update_companyUpdate companyPUTUpdates a company: name, emails, phones, groups, note, language, location and custom fields.

Group, 5 operations

create_groupCreate groupPOSTCreates a contact group with a name and optional colors.
delete_groupDelete groupDELETEDeletes a contact group, identified by its id from list_groups.
get_groupGet groupGETReturns one contact group: id, name and colors.
list_groupsList groupsGETLists the contact groups (segments of contacts and companies) with id, name and colors.
update_groupUpdate groupPUTUpdates a contact group: name and colors.

Predefined answer, 5 operations

create_predefined_answerCreate predefined answerPOSTCreates a predefined answer (a saved email reply) with a name, body, optional subject, format, agent and department.
delete_predefined_answerDelete predefined answerDELETEDeletes a predefined answer.
get_predefined_answerGet predefined answerGETReturns one predefined answer: name, subject, body, format, agent and department.
list_predefined_answersList predefined answersGETLists predefined answers (saved email replies) with name, subject, body, format (T text, H html), agent and department.
update_predefined_answerUpdate predefined answerPUTUpdates a predefined answer: name, subject, body, format, agent and department.

Tag, 5 operations

create_tagCreate tagPOSTCreates a ticket tag with a name, optional text and background colors, and whether it is public (Y) or private (N).
delete_tagDelete tagDELETEDeletes a ticket tag, identified by its id from list_tags.
get_tagGet tagGETReturns one tag: name, colors, public and archived flags.
list_tagsList tagsGETLists the ticket tags with id, name, colors and whether each is public or archived. Tag ids are what tickets carry in tags.
update_tagUpdate tagPUTUpdates a tag: name, colors and public flag.

Ticket, 5 operations

create_ticketCreate ticketPOSTCreates a ticket with a first message: subject, message, department, recipient and user identifier are required; status, CC, BCC, tag ids, custom fields and the do_not_send_mail, use_template and is_html_message flags (Y or N) are optional.
delete_ticketDelete ticketDELETEDeletes a ticket, identified by its id from list_tickets.
get_ticketGet ticketGETReturns one ticket: subject, status, channel, owner contact and email, agent, department, tags, custom fields, due and resolved dates and last activity.
list_ticketsList ticketsGETLists tickets with subject, status, channel, owner contact, agent, department, tags, custom fields and dates. Filter with _filters (status, department, agent and others); paginate with _page and _perPage.
update_ticketUpdate ticketPUTUpdates a ticket: owner contact, department, agent, status, subject, tag ids and custom fields. Only the fields sent are changed; omitted ones are left as they are.

History, 3 operations

get_ticket_historyGet ticket historyGETReturns the history of one ticket: each period with its status, department and agent, start and end dates and elapsed time.
get_ticket_sla_historyGet ticket sla historyGETReturns the SLA history of one ticket: each SLA type with its due, created and closed dates and the total and elapsed time.
list_tickets_historyList tickets historyGETLists ticket history entries across tickets: status, department and agent of each period with its start, end and elapsed time. Paginate with _cursor.

Sla, 3 operations

get_sla_levelGet sla levelGETReturns one SLA level with its target values and business hours.
get_ticket_slaGet ticket slaGETReturns the SLA of one ticket: SLA level and the first answer, first assign, first resolve and next answer deadlines.
list_sla_levelsList sla levelsGETLists the SLA levels with their target values (first answer, first assign, first resolve, next answer, chat and call answer) and business hours.

Agent, 2 operations

get_agentGet agentGETReturns one agent: name, email, role, avatar, online status, account status, gender, two-factor status and voice status.
list_agentsList agentsGETLists the agents of the account with name, email, role, online status (F offline, N online, P paused, C mobile), account status and voice status. Filter with _filters; paginate with _page and _perPage.

Department, 2 operations

get_departmentGet departmentGETReturns one department: name, online status, agent count, agent ids and mail account id.
list_departmentsList departmentsGETLists the departments with their name, online status, agent count, agent ids and mail account id. Department ids are needed to create tickets.

Activity, 1 operation

list_agent_activityList agent activityGETLists the online agents with their activity status (A available, B busy) and the tickets each one is currently viewing, replying to, chatting or calling on.

Call, 1 operation

list_callsList callsGETLists phone calls with type (I incoming, O outgoing, T internal), from and to numbers and names, ticket id, created, answered and finished dates and duration. Paginate with _cursor.

Chat, 1 operation

list_chatsList chatsGETLists chats with subject, preview, status (C chatting, T finished, R ringing, Q in queue), visitor name, emails and location, department, agent and tags.

Message, 1 operation

list_ticket_messagesList ticket messagesGETLists the message groups of a ticket (emails, chats, calls, notes, status changes) with their messages, authors and dates. includeQuotedMessages adds the quoted text.

Ping, 1 operation

pingPingGETChecks that the LiveAgent API answers for this account and API key. Useful to test the connection.

Postpone, 1 operation

postpone_ticketPostpone ticketPUTSets a ticket to the postponed status until the given date and time (YYYY-MM-DD HH:MM:SS).

Status, 1 operation

get_agent_statusGet agent statusGETReturns an agent's status in each department: online and preset channels (R read, M message, T chat, P phone) and whether work can be allocated.

Time, 1 operation

list_time_reportsList time reportsGETLists time report rows (time agents reported or spent on tickets) with agent, ticket, customer, company, reported and spent time and type (auto or manual). Paginate with _cursor.

Time zone, 1 operation

list_time_zonesList time zonesGETLists the time zones LiveAgent knows, with code and name.

User, 1 operation

get_userGet userGETReturns a LiveAgent user (agent, admin, owner or visitor) by id: name, email, role and avatar URL.

Use LiveAgent from Claude Code, Cursor or Codex

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

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