Hatz AI
Building an MSP-native AI platform with model routing, governance, and PSA integrations.
A side-by-side editorial comparison of LiveAgent and Discourse — release velocity, themes, recent moves, and the top alternatives to consider.
Wires MCP into the help desk to let Claude work tickets directly.
LiveAgent has crossed from being a conventional help-desk platform to one that exposes its own ticketing surface to LLM agents via MCP. The May 18 release shipped an AI Agent Work Distributor for tickets, an add_note MCP tool, and OAuth 2.1 on the MCP server for claude.ai custom connectors — alongside an unusually large fix and refactor batch covering voice, WhatsApp, and PHP 8.5 readiness. Cadence is high but uneven, with several small per-day patch versions interleaved with one massive omnibus drop.
Discourse opens its AI bot to any external MCP server, treating the forum as an agent host.
Discourse runs on a monthly main release plus periodic security intermediates, and the editorial focus across recent posts is clearly AI plumbing. March added Bring-Your-Own MCP server support to the Discourse AI Bot, alongside documented AI credentials management and SSO auto-provisioning for forum admins. The team has also been adjusting its release-communication process, with backdated intermediate-release topics filling earlier gaps.
LiveAgent has crossed from being a conventional help-desk platform to one that exposes its own ticketing surface to LLM agents via MCP. The May 18 release shipped an AI Agent Work Distributor for tickets, an add_note MCP tool, and OAuth 2.1 on the MCP server for claude.ai custom connectors — alongside an unusually large fix and refactor batch covering voice, WhatsApp, and PHP 8.5 readiness. Cadence is high but uneven, with several small per-day patch versions interleaved with one massive omnibus drop.
Two clear threads are running in parallel: an AI integration push that treats MCP as the primary contract between LiveAgent and external agents, and a deep platform modernization (Symfony HttpClient replacing legacy Gpf_Net_Http, repository pattern displacing static model calls, IPv6 hardening, CRAM-MD5 prioritization). The product is paying down the foundation it needs to host more agent-driven workflows safely.
Expect the MCP surface to expand beyond add_note — read-side tools (search tickets, fetch conversation context) and probably a triage or routing tool are the natural next steps, given the AI Agent Work Distributor already exists internally.
Discourse runs on a monthly main release plus periodic security intermediates, and the editorial focus across recent posts is clearly AI plumbing. March added Bring-Your-Own MCP server support to the Discourse AI Bot, alongside documented AI credentials management and SSO auto-provisioning for forum admins. The team has also been adjusting its release-communication process, with backdated intermediate-release topics filling earlier gaps.
Discourse is positioning the forum as an environment that hosts agents, not just a place that uses AI features. By accepting any MCP-compatible tool provider as a backend, it makes itself the substrate community managers extend with arbitrary external capabilities — search, ticketing, knowledge bases, whatever the host wires in. SSO auto-provisioning and structured form templates round out the admin surface that this agent-host posture needs.
Expect deeper agent UX inside topics — more entry points and persona configuration — alongside audit and observability tooling for what external MCP tools do on a forum. Community trust depends on that side staying explainable.
Other Support products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either LiveAgent or Discourse.
Building an MSP-native AI platform with model routing, governance, and PSA integrations.
Desk365 is layering security and asset management onto its Teams-native helpdesk play.
Forethought pivots from answering questions to executing outcomes via Orchestrator and Browser Agents.
Mature remote-support tool ships steady platform-compat work while leaning on awards and recap posts for momentum.
Mature helpdesk in deep maintenance mode, publishing infrequently around Zoho-stack integrations.
Re:amaze is rebuilding its helpdesk around an AI agent — multi-channel rollout, smarter intent, sharper positioning.
See all LiveAgent alternatives → · See all Discourse alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. LiveAgent is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. LiveAgent is currently shipping more aggressively (velocity 6.3 vs 5.0), with 1 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Support products to evaluate alongside.
Top LiveAgent alternatives in Support are ranked by recent ship velocity. Browse the "LiveAgent alternatives" section above for the current picks, or visit /alternatives/liveagent for the full list with editorial commentary on each.
Top Discourse alternatives in Support are ranked by recent ship velocity. Browse the "Discourse alternatives" section above for the current picks, or visit /alternatives/discourse for the full list with editorial commentary on each.