Rasa

Verification notes: Two corrections this pass. First, the 'Rasa Open Source' framing itself is being retired, not just left in maintenance: Rasa's own materials now describe a 'Rasa Developer Edition,' free to run locally and in production within set limits, built on CALM (Conversational AI with Language Models) rather than the older intent-classification pipeline; the commercial line splits into Rasa Pro (framework and infrastructure) and Rasa Studio (no-code UI). Apache 2.0 licensing is unchanged. Second, the mcp flag moves from false to true: Rasa now has a dedicated product page (rasa.com/mcp) documenting MCP support as part of its orchestration layer, letting agents call MCP-defined tools via declarative policies rather than only model-guessed tool calls — this appears to be a platform-wide capability rather than something scoped only to the paid tiers, but that scoping wasn't fully disambiguated on the page itself, worth checking on a future pass. No A2A support confirmed. Correction this pass: the a2a flag moves from false to true. Rasa's own documentation (rasa.com/docs/reference/integrations/a2a-server/, last updated September 14, 2026) confirms Rasa Pro 3.17 added a native A2A Server: when an a2a_server block is set in endpoints.yml, Rasa registers A2A JSON-RPC routes (message/send, message/stream, tasks/cancel, tasks/get) on the same port as REST/channel webhooks, with an auto-generated AgentCard served at /.well-known/agent-card.json. This is the sub-agent (server) side -- Rasa exposing itself to external A2A orchestrators -- documented separately from Rasa's existing role as an A2A orchestrator calling external sub-agents.