Richpanel vs Discourse
Side-by-side trajectory, velocity, and editorial themes.
Richpanel is widening its integration moat and opening the helpdesk up to AI via MCP.
Richpanel is in heavy integration mode, shipping a new ecommerce or comms connector almost every week — Appstle Subscriptions, JustCall (inbound/outbound calls in the inbox), BigCommerce, WhatsApp templates from the reply box, plus earlier ShipInsure, Okendo, and Fulfil ERP. The strategically interesting moves are a Claude/MCP integration that gives Anthropic's assistant secure access to helpdesk data, and Custom HTTP Widgets that let merchants pull any REST API into the conversation sidebar.
The product is positioning as the most-connected helpdesk for Shopify-era ecommerce: native integrations for every adjacent SaaS, plus the no-code Custom HTTP widget escape hatch for the long tail. The MCP server signals where they want to go next — AI assistants reading and acting on helpdesk data rather than agents copy-pasting between tabs. Competitive frame is Gorgias, Zendesk's commerce push, and Shopify Inbox.
Expect more MCP/agent surface — likely outbound connectors for ChatGPT and Cursor on top of the existing Claude integration, plus internal AI-drafted replies and triage. Integration breadth will keep expanding across loyalty, reviews, subscriptions, and shipping. Pricing may eventually meter AI usage per conversation alongside seat-based plans.
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.
See more alternatives to Richpanel →
See more alternatives to Discourse →