Discourse vs LiveAgent
Side-by-side trajectory, velocity, and editorial themes.
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.
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.
LiveAgent wires its ticketing engine into the Claude ecosystem via MCP.
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.
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.
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.
See more alternatives to Discourse →
See more alternatives to LiveAgent →