Discourse vs Twilio
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.
Twilio reframes itself as the conversation layer for AI agents, not just a messaging API.
Twilio just shipped a coordinated batch of GA launches anchored on a new Conversations layer: Agent Connect SDK, Conversation Memory, Conversation Intelligence, Enterprise Knowledge, and Conversation Relay Insights all moved to GA on the same day. Alongside that, Apple Messages for Business is in private beta and a Bulk Messaging API is in public beta. The platform's center of gravity has clearly shifted from raw channel APIs to an AI-agent orchestration stack sitting on top of them.
Twilio is repositioning the company as the runtime where customer-facing AI agents live — owning memory, intelligence, channel reach, and observability, not just message delivery. The packaging is deliberate: each piece is shippable alone, but together they form an opinionated stack that competes head-on with Salesforce/Genesys agent platforms and with developer-first stacks like LiveKit. Expect Twilio to push hard on lock-in through Conversation Orchestrator as the binding layer.
Next likely moves: GA for Apple Messages for Business, and an expansion of the Agent Connect SDK toward third-party LLM and tool integrations to position it as the de-facto agent runtime on top of Twilio's channels. A Bulk Messaging GA and pricing for the AI features should follow within one to two quarters.
See more alternatives to Discourse →
See more alternatives to Twilio →