LoginSign Up
← Back to Support
Weekly · Support · Week of May 25, 2026

Customer support's MCP week: LiveAgent wires Claude.ai into ticketing while the long tail goes quiet

mcpai-agentshelpdeskgovernancemsp-platformplatform-modernization
O
By Onur Öztürk
LinkedIn ↗
Generated 1h agoDrawn from 11 products

The week in customer support

The sector's most consequential release this week was small in word count and large in implication. LiveAgent shipped an MCP server hardened with OAuth 2.1 specifically for claude.ai custom connectors, an addnote MCP tool, and an AI Agent Work Distributor that hands tickets to agents as a routing primitive — bundled into the same drop as Symfony HttpClient replacing legacy GpfNet_Http, a repository-pattern refactor of contact and ticket access, and PHP 8.5 readiness. A help desk that has historically read like a Zendesk alternative is now an MCP-addressable system, and it picked the most opinionated possible client to integrate against first.

The rest of the week reads as supporting evidence for the same direction. Hatz AI wired Autotask in as its second PSA alongside ConnectWise Manage and added tenant-level direct-download restrictions, deepening the MSP-control-plane positioning. Discourse, whose March Bring-Your-Own MCP launch already reframed the forum as an agent host, shipped a backdated intermediate security batch on May 19 — quiet, but consistent with the tightened release-comms cadence the team needs to keep enterprise self-hosters confident. Desk365 stayed on its asset-management absorption track with a second Asset Panda comparison piece. Forethought, Supportbench, Tiledesk, the Zoho trio, and osTicket published no in-window shipping signal: editorial only or maintenance posture.

Leaders

  • LiveAgent — The May 18 omnibus is the week's defining release for the sector. OAuth 2.1 on the MCP server is the load-bearing detail: it signals LiveAgent expects external agents to authenticate against ticketing the way a SaaS app authenticates a user, not the way a webhook authenticates a callback. The simultaneous platform refactor (Symfony HttpClient, repository pattern, PHP 8.5) is the un-glamorous half — paying down the foundation needed to safely host more agent-driven workflows. A May 22 cleanup batch covering chat-group offline fallback, IVR field substitution, and a missing WhatsApp ticket panel showed the team still has bandwidth for operator-visible fit-and-finish in the same week.
  • Hatz AI — Autotask landed as the second major PSA wired into Hatz workflows on May 22, completing the pair started with ConnectWise Manage's rebuild a week earlier. The same release adds OneDrive/SharePoint save targets, tenant-level direct-download restrictions, and a Client Admin Usage Dashboard. Read together, this is governance keeping pace with capability expansion — the MSP control-plane thesis getting more credible by the week.
  • Discourse — May 19's intermediate-release batch is routine on its surface but worth flagging because Discourse's broader AI plumbing — particularly Bring-Your-Own MCP for the AI bot — depends on the security cadence staying tight. Patches were shipped across the 2026.5, 2026.4, 2026.3, and 2026.1 trains, fitting the team's documented patch-fast, document-later posture.
  • Desk365 — No new product release dropped this week, but the second Asset Panda review piece (May 19) plus the prior week's MFA and asset-bulk-edit shipment together form a coherent move: absorb asset management into the Microsoft Teams-native helpdesk wedge rather than leave it to integrations. The buyer-funnel content is doing the same work as a product page.

Wildcards

  • Forethought — Shipped no functionality this week; the only in-window post is "How Trust is Becoming the Currency of AI," a CEO-adjacent essay that reinforces the deterministic-control framing the team established with April's Orchestrator and Browser Agents GA. Worth tracking because Forethought is the sector's clearest articulation of the "outcomes, not answers" pivot, and the trust framing reads as setup for outcomes-priced packaging.

Themes that compounded

  • MCP became the contract. Two of the four substantive shippers this week — LiveAgent and Hatz — touched MCP infrastructure directly, and Discourse's prior BYO-MCP move continues to anchor its agent-host posture. The pattern across the sector is no longer "does this product have AI features" but "what does its MCP surface let an external agent do."
  • Help desks added governance before they added features. LiveAgent's OAuth 2.1, Hatz's tenant-level download restrictions and admin usage dashboards, and Desk365's prior-week MFA all point the same way: the AI-readiness work that ships this quarter is the access-control plumbing, not the model integration. The model layer is treated as commoditized; the boundary controls are not.
  • Platform refactors hid inside AI releases. LiveAgent's MCP launch bundled a Symfony HttpClient swap, a repository-pattern refactor, and PHP 8.5 readiness — exactly the legacy debt a 2003-era PHP help desk has to retire before it can safely host agent workflows. The pattern is broader than LiveAgent; modernization is travelling under AI-shaped marketing.
  • Editorial substitutes for shipping in the long tail. Supportbench published ten 'How to' SEO posts in 48 hours, all pitching AI triage as the routing fix; Tiledesk continued its MCP-themed editorial run; Zoho Desk and osTicket published nothing. Three different versions of quiet — content marketing as proxy, agentic-pivot positioning, and pure maintenance mode — sit side by side.

Watch this week

Two follow-throughs are most likely. LiveAgent's MCP surface is unusually narrow today — add_note plus the AI Agent Work Distributor — and the obvious next moves are read-side tools (search tickets, fetch conversation context) and a triage or routing MCP tool that mirrors the internal work distributor. If those land in the next omnibus, the platform crosses from MCP-addressable to MCP-operable. Separately, Hatz AI has now closed the PSA pair (ConnectWise plus Autotask); the natural next surface is RMM (NinjaOne, Kaseya) or audit-log exports for the governance side, either of which would extend the MSP control-plane positioning into a defensible enterprise-procurement story.