← Back to all sparks
LiveAgent logo

LiveAgent

SUPPORT
Velocity6.3

Helpdesk software with live chat and ticketing

LiveAgent wires its ticketing engine into the Claude ecosystem via MCP.

mcpclaude-connectorai-ticket-triagecustomer-supportsecurity-hardeningbackport-cadence
Current state
LiveAgent is in dense maintenance mode — multiple version trains and a backport branch all shipping fixes and security patches almost daily — but the AI integration thread has sharpened. The 5.64 release adds an AI Agent Work Distributor for tickets, a new add_note MCP tool, and OAuth 2.1 on the MCP server with the explicit goal of letting claude.ai connect as a custom connector. Earlier May releases switched the MCP protocol to Streamable HTTP and renamed MCP tokens for clarity.
Where it's heading
The product is positioning MCP as its core integration substrate. Each release adds another MCP refinement — protocol upgrade, naming cleanup, ticket-level AI work distribution — pointing toward a model where Claude or any MCP-aware agent triages and acts on tickets natively. The parallel backport lines (5.62.x, 5.63.x) suggest the AI work is being layered on without forcing customers off the legacy install base.
Prediction
Expect the AI Agent Work Distributor to grow into more autonomous resolution flows, with new MCP tools added incrementally (search, reply, escalate), and a more explicit Claude-Connector-ready posture in product marketing.

Recent moves

  1. 3d ago

    AI Agent Work Distributor and OAuth 2.1 MCP server for claude.ai land in 5.64.6

    ⚡ SPARK

    Three AI-shaped changes hit at once: an AI Agent Work Distributor for tickets, an add_note MCP tool, and OAuth 2.1 on the MCP server specifically to support claude.ai's custom connector flow. Together they are the strongest directional move of the quarter — LiveAgent is now wiring its core ticketing actions to be addressable from an external agent.

    View source ↗
  2. 4d ago

    5.63.7 patch: Facebook Graph v20+, AI work fixes, mail parser hardening

    A fix-heavy point release that upgrades Facebook Graph API to v20+ in SSO and patches multiple bugs around AI Work executions, ticket field handling, and forwarded mail parsing. Tells you the AI Work surface is now in real-world use and being shaped by production feedback.

    View source ↗
  3. 9d ago

    5.63.7 hotfix: badge save error and Zendesk import null-field crash

    A two-fix hotfix release. No directional content — typical maintenance for a mature support platform.

    View source ↗
  4. 10d ago

    5.63.7 patch: MCP switches to Streamable HTTP, API and rules fixes

    Switches the MCP protocol to Streamable HTTP and clears a backlog of API and rules engine fixes. The protocol change matters more than it looks — Streamable HTTP is the same transport Claude.ai's connector expects, slotting into the broader MCP positioning shown in the 5.64 release.

    View source ↗
  5. 14d ago

    5.63.7 patch: MCP token rename, security and Facebook fixes

    Renames MCP Tokens to MCP Access Tokens — small but meaningful for a surface that is increasingly user-facing — alongside the usual mix of security improvements and Facebook integration fixes. Consistent with the MCP polish pass happening across May.

    View source ↗
  6. 14d ago

    5.62.18 backport: single security improvement

    A one-line backport-branch release containing only a security improvement. Confirms the older 5.62.x line is still being maintained alongside the active 5.63 and 5.64 trains.

    View source ↗