CrewAI

Verification notes: Re-checked this pass: MIT core license, native MCP support (via crewai-tools-mcp, shipped with the 1.0 GA), and A2A protocol compatibility (added in the v1.10.1 release) all remain accurate — no change to flags. A2A support lets one Crew delegate to another as a standardized endpoint rather than only through custom glue code. For a comparable but not identical developer framework, see the newly added OpenAI Agents SDK listing — same job, building multi-agent workflows, different vendor and protocol posture. Re-checked again this pass: license, MCP, and A2A support remain accurate — no flag changes. Development has continued at a steady pace (CrewAI 1.1.0 shipped with declarative-refs support for flows and crews, JSON-schema kickoff fixes, and Crew Studio updates; crewai-tools had its own separate release in mid-August 2026), but nothing in the recent release notes changes the protocol-support or licensing picture documented previously. Re-checked 2026-09-28: CrewAI has shipped well past the 1.1.0 release cited above — current is v1.15.22 (September 16, 2026, per CrewAI's own changelog), with 1.14.0 adding runtime state checkpointing and 1.15.x adding connection aliasing and tracing improvements. MIT license and MCP/A2A support are reconfirmed directly in the crewAIInc/crewAI repository's own README. No flag changes.