Formbricks
Formbricks 6.0 RC cycle reveals commercial hardening: lower self-hosted cap, MCP OAuth, and Act as Beta
A side-by-side editorial comparison of Live Helper Chat and Re:amaze — release velocity, themes, recent moves, and the top alternatives to consider.
Live Helper Chat ships MCP support, making self-hosted customer chat an AI-queryable endpoint
Live Helper Chat added native Model Context Protocol support in its latest release, adding an MCP endpoint at `aimcp/mcp` that exposes the chat installation to external AI clients—ChatGPT custom connectors, Claude, and other MCP hosts. The endpoint uses Streamable HTTP via the official PHP MCP SDK, with token-based authentication, CORS controls, and a new admin screen showing the tool catalog. Recent releases have also added reCAPTCHA v3 and Cloudflare Turnstile support, and configurable operator offline reasons.
Re:amaze keeps adding stages to the pipeline before a human sees a ticket
Re:amaze publishes a blog that doubles as its release channel, and the run since January is a single continuous build: the AI Agent launched as a knowledge-base-backed chatbot, gained smarter intent detection, extended to email and SMS, then a mid-year roundup added visibility into how the agent works and ways to test it before it goes live. The newest entry introduces an AI Pre-Filter that sorts the inbox before any of that runs — separating marketing mail, shipping notices, social mentions and spam from the customers who actually need an answer.
Live Helper Chat added native Model Context Protocol support in its latest release, adding an MCP endpoint at `aimcp/mcp` that exposes the chat installation to external AI clients—ChatGPT custom connectors, Claude, and other MCP hosts. The endpoint uses Streamable HTTP via the official PHP MCP SDK, with token-based authentication, CORS controls, and a new admin screen showing the tool catalog. Recent releases have also added reCAPTCHA v3 and Cloudflare Turnstile support, and configurable operator offline reasons.
The MCP addition converts LHC from a standalone support tool into infrastructure that participates in agentic workflows. This is the most significant architectural change the project has shipped in several releases—and it opens the door to AI agents querying chat history, routing conversations, or creating tickets without custom API wrappers. The next moves will likely expand the MCP tool catalog and deepen the AI client integration.
Expect the MCP tool surface to grow in the next 2-3 releases: richer read/write access to conversation history, customer profiles, and ticket creation are the natural asks from AI client integrators who've discovered the endpoint.
Re:amaze publishes a blog that doubles as its release channel, and the run since January is a single continuous build: the AI Agent launched as a knowledge-base-backed chatbot, gained smarter intent detection, extended to email and SMS, then a mid-year roundup added visibility into how the agent works and ways to test it before it goes live. The newest entry introduces an AI Pre-Filter that sorts the inbox before any of that runs — separating marketing mail, shipping notices, social mentions and spam from the customers who actually need an answer.
The company is working backwards from the reply toward the inbox. First the agent answered questions, then it understood them better, then it reached more channels, then it became inspectable and testable. Pre-filtering is the logical next step upstream: deciding what is even a support conversation. The supporting content — how to write help centre articles for better AI answers, how much support AI should handle — is aimed at customers who have to decide how much of the queue to hand over.
Expect the pre-filter and the agent to be connected into a single routing decision, with escalation rules for the VIP case the announcement explicitly calls out as needing a person.
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 Live Helper Chat or Re:amaze.
Formbricks 6.0 RC cycle reveals commercial hardening: lower self-hosted cap, MCP OAuth, and Act as Beta
SolarWinds Service Desk is loading its Labs pipeline with native Entra ID automation, IT asset tracking, and compliance-ready task management.
Freshchat keeps product moves off the public record — changelog offers nothing to track.
Freshdesk's changelog feed contains only marketing copy — no substantive release data available.
TeamViewer's scraped feed contains only community marketing fragments—no actual release data.
LiveAgent launches Svelte 5 frontend migration and multi-model AI simultaneously.
See all Live Helper Chat alternatives → · See all Re:amaze alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — customer-support — within Support. Live Helper Chat is currently shipping more aggressively (velocity 6.3 vs 2.5), 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. Live Helper Chat is currently shipping more aggressively (velocity 6.3 vs 2.5), 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 Live Helper Chat alternatives in Support are ranked by recent ship velocity. Browse the "Live Helper Chat alternatives" section above for the current picks, or visit /alternatives/livehelperchat for the full list with editorial commentary on each.
Top Re:amaze alternatives in Support are ranked by recent ship velocity. Browse the "Re:amaze alternatives" section above for the current picks, or visit /alternatives/reamaze for the full list with editorial commentary on each.