Feature matrix · Last reviewed September 2026

Multi-agent framework feature matrix

Last reviewed: September 2026

Quick answer

LangGraph and Google ADK have the most Yes marks, 9 of 13 each, followed by BAND and Microsoft Agent Framework with 8. BAND is the only tool marked Yes on all three collaboration rows: cross-framework agents, humans as live participants and coding agents as teammates. The frameworks lead on open-source licensing, durable execution, built-in tracing and self-hosting; BAND is a hosted (SaaS) service with no documented self-hosting. Every tool supports MCP, and Google ADK leads on languages.

Collaboration and framework features matrix

Feature matrix of eight multi-agent tools across thirteen capabilities, September 2026
FeatureBANDLangGraphCrewAIMicrosoft Agent FrameworkGoogle ADK (Agent Development Kit)OpenAI Agents SDKn8nAgno
Python SDKYesYesYesYesYesYesNo / not documented: No SDK (code nodes only)No SDK (code nodes only)Yes
TypeScript / JavaScript SDKYesYesNo / not documentedNo / not documented: .NET and Go instead.NET and Go insteadYesYes: @openai/agents@openai/agentsNo / not documented: No SDK (code nodes only)No SDK (code nodes only)No / not documented
.NET, Go, Java or KotlinNo / not documentedNo / not documentedNo / not documentedYes: .NET GA, Go preview.NET GA, Go previewYes: Go, Java, KotlinGo, Java, KotlinNo / not documentedNo / not documentedNo / not documented
A2A protocolYesYes: LangSmith Agent Server, A2A v1.0LangSmith Agent Server, A2A v1.0Yes: native delegation, client and servernative delegation, client and serverPartial: open-source framework shows A2A in hosting samples; Microsoft Foundry Agent Service lists A2A v1.0 as generally availableopen-source framework shows A2A in hosting samples; Microsoft Foundry Agent Service lists A2A v1.0 as generally availableYes: Google created A2AGoogle created A2ANo / not documentedNo / not documentedYes: AgentOS interfaceAgentOS interface
MCPYesYes: agents exposed at /mcpagents exposed at /mcpYes: mcps fieldmcps fieldYes: stdio, HTTP, WebSocket toolsstdio, HTTP, WebSocket toolsYes: toolstoolsYes: MCP server toolsMCP server toolsYes: client and server nodesclient and server nodesYes: tools and AgentOS as servertools and AgentOS as server
Connects agents built in other frameworksYes: native adapters and published integrations incl. LangGraph, CrewAI, Google ADK, Agno, Pydantic AI, Letta, Claude Agent SDK, Copilot Studio, Agentforcenative adapters and published integrations incl. LangGraph, CrewAI, Google ADK, Agno, Pydantic AI, Letta, Claude Agent SDK, Copilot Studio, AgentforcePartial: via A2A endpointsvia A2A endpointsPartial: A2A delegationA2A delegationPartial: MCP tools; A2A samplesMCP tools; A2A samplesPartial: consume remote A2A agentsconsume remote A2A agentsNo / not documentedPartial: MCP client/serverMCP client/serverPartial: A2AA2A
Humans as live participants in agent threadsYes: rooms where people inspect, approve, override and reply in placerooms where people inspect, approve, override and reply in placePartial: human-in-the-loop interruptshuman-in-the-loop interruptsPartial: HITL checkpointsHITL checkpointsPartial: orchestrations support HITLorchestrations support HITLPartial: action confirmations and human inputaction confirmations and human inputPartial: needs_approval interruptionsneeds_approval interruptionsPartial: human approval for toolshuman approval for toolsPartial: confirmation and user inputconfirmation and user input
Coding agents (Claude Code, Codex, Copilot) as participantsYes: BAND for desktop; integrations list Claude Code, Codex, GitHub Copilot, OpenCodeBAND for desktop; integrations list Claude Code, Codex, GitHub Copilot, OpenCodeNo / not documentedNo / not documentedNo / not documentedNo / not documentedNo / not documentedNo / not documentedNo / not documented
Vendor-managed hostingYes: Hosted (SaaS); connects agents running on AWS, GCP or on-premHosted (SaaS); connects agents running on AWS, GCP or on-premYes: LangSmith DeploymentLangSmith DeploymentYes: CrewAI AMPCrewAI AMPYes: Microsoft Foundry hosted agentsMicrosoft Foundry hosted agentsYes: Agent Runtime on Google CloudAgent Runtime on Google CloudNo / not documented: library, you hostlibrary, you hostYes: n8n Cloudn8n CloudPartial: hosted control plane on Pro; runtime runs in your cloudhosted control plane on Pro; runtime runs in your cloud
Self-hostingNo / not documented: No (not documented)No (not documented)Yes: library; platform self-host on Enterpriselibrary; platform self-host on EnterpriseYesYesYesYesYes: Community EditionCommunity EditionYes
Open-source licenseNo / not documented: commercial, not open sourcecommercial, not open sourceYes: MITMITYes: MITMITYes: MITMITYes: Apache 2.0Apache 2.0Yes: MITMITNo / not documented: fair-code Sustainable Use License, not OSI open sourcefair-code Sustainable Use License, not OSI open sourceYes: Apache-2.0Apache-2.0
Durable execution / checkpointingNo / not documented: not documented; per-message delivery tracking insteadnot documented; per-message delivery tracking insteadYes: checkpointers and durable executioncheckpointers and durable executionPartial: Flow state persistenceFlow state persistenceYes: workflow checkpointingworkflow checkpointingPartial: session state servicessession state servicesPartial: sessions; resumable run state for approvalssessions; resumable run state for approvalsPartial: saved executions; retry from failed nodesaved executions; retry from failed nodePartial: session storage in a databasesession storage in a database
Built-in tracing / observabilityPartial: per-message lifecycle with attempt history; not a tracing toolper-message lifecycle with attempt history; not a tracing toolYes: LangSmith tracingLangSmith tracingYes: built-in tracingbuilt-in tracingYes: OpenTelemetryOpenTelemetryYes: dev UI traces; OpenTelemetrydev UI traces; OpenTelemetryYes: built-in tracingbuilt-in tracingPartial: execution logs per runexecution logs per runPartial: via observability integrationsvia observability integrations
Tally8 Yes, 1 Partial, 4 No9 Yes, 2 Partial, 2 No7 Yes, 3 Partial, 3 No8 Yes, 3 Partial, 2 No9 Yes, 3 Partial, 1 No6 Yes, 2 Partial, 5 No3 Yes, 4 Partial, 6 No5 Yes, 5 Partial, 3 No

Yes = documented and generally available. Partial = available with limits, in preview, or only through samples or a separate package. No = not offered, or not documented in the vendor pages we reviewed in September 2026. Tell us if something changed: editors@multiagentcompare.com.

What does each feature mean?

Python SDK / TypeScript SDK / .NET, Go, Java or Kotlin
An official SDK maintained by the vendor. Code nodes inside a visual tool count as partial.
A2A
The Agent2Agent protocol, now a Linux Foundation project, for agent-to-agent calls across frameworks. v1.0.0 was released on March 12, 2026.
MCP
The Model Context Protocol, for connecting agents to tools and data. Latest spec revision 2026-07-28.
Connects agents built in other frameworks
Can agents that were not built with this tool take part in its multi-agent coordination? Partial means through a protocol call rather than as a full participant.
Humans as live participants
Can a person reply and redirect inside the same thread as the agents? Partial means approval or interrupt steps.
Coding agents as participants
Can Claude Code, Codex, GitHub Copilot or OpenCode sessions join and hand off work?
Vendor-managed hosting / Self-hosting
Whether the vendor runs it for you, and whether you can run it yourself.
Open-source license
Released under an OSI-approved open-source license such as MIT or Apache 2.0. Fair-code and source-available licenses count as No.
Durable execution / checkpointing
Can a run save its state and resume after a failure or a pause? Partial means session or execution storage without full workflow checkpointing.
Built-in tracing / observability
Does the tool record traces of agent runs, directly or through a first-party service? Partial means logs or third-party integrations.

How do coordination models and pricing compare?

ToolCoordination modelEntry priceLicenseSource
BAND@mention-based routing in shared rooms (direct, group, task-scoped); per-agent, per-message lifecycle with attempt history; loop prevention via mandatory mentions and per-room limits; cross-agent context via Memories.Free $0 (single user, non-commercial, up to 20 remote agents, 250 active rooms, 2-week retention); Pro $17.99/mo (single user, 40 remote + 40 native agents, 500 rooms, 40 participants per chat, data export); Enterprise custom (by quote; required for team or commercial use).CommercialBAND platform
LangGraphExplicit state graph; documented multi-agent patterns are subagents, handoffs, skills, router and custom workflow.OSS free; LangSmith Developer $0 (1 seat, 5k base traces/mo); Plus $39/seat/mo (10k base traces, 1 free Serverless Small deployment); Enterprise custom.MITLangGraph repo
CrewAICrews of role-based agents run as a Sequential or Hierarchical process (hierarchical automatically assigns a manager); Flows add event-driven control with state.OSS free; AMP Basic free (50 workflow executions/mo); Enterprise custom.MITCrewAI repo
Microsoft Agent FrameworkTyped, graph-based Workflows plus built-in orchestrations: Sequential, Concurrent, Handoff, Group Chat, Magentic; all support human-in-the-loop; checkpointing.Framework free; Foundry and model usage billed by Azure.MITAgent Framework repo
Google ADK (Agent Development Kit)Sequential, Parallel and Loop workflow agents; graph-based workflows (new in 2.0); delegation via a Task API.Framework free; runtime and models billed by Google Cloud.Apache 2.0ADK docs
OpenAI Agents SDKHandoffs between agents and agents-as-tools (manager style); guardrails, sessions, tracing built in; human approval of tool calls via needs_approval interruptions.SDK free; pay model API usage.MITOpenAI Agents SDK (Python)
n8nTrigger- and event-driven workflows with an agent loop; agents can delegate to other agents (sub-agents) and run on a schedule; human approval before an AI Agent runs specific tools.EUR, billed annually: Starter €20/mo (2,500 executions), Pro €50/mo (10,000), Business €667/mo (40,000, self-host option), Enterprise custom; Community Edition self-hosted free; one agent turn counts as one execution.Sustainable Use License (fair-code, not OSI) + n8n Enterprise Licensen8n pricing
AgnoLeader-and-members Teams with four modes (Coordinate, Route, Broadcast, Tasks) plus Workflows; HITL confirmations and user input.Free $0; Pro $150/mo (1 live control-plane connection, 3 seats); Enterprise custom.Apache-2.0Agno teams

Official SDK languages

Counts languages with an official SDK. Go for Microsoft Agent Framework is in public preview. Source: vendor docs, September 2026.
Official SDK languages
ToolOfficial SDK languagesLanguages
BAND2Python, TypeScript
LangGraph2Python, JS/TS
CrewAI1Python
Microsoft Agent Framework3Python, .NET, Go preview
Google ADK5Python, TS/JS, Go, Java, Kotlin
OpenAI Agents SDK2Python, TS/JS
n8n1visual builder, JS/Python code nodes
Agno1Python

Protocol support

MCP is close to universal. BAND also lists ACP. A2A support is where stacks differ, and supporting A2A is not the same as agents sharing a room.
Protocol support
ToolA2A scoreMCP score
BAND11
LangGraph11
CrewAI11
Microsoft Agent Framework0.51
Google ADK11
OpenAI Agents SDK01
n8n01
Agno11

What do people ask about the feature matrix?

Why is every tool marked Yes for MCP?

Because every one of them documents MCP support. That is why we do not treat MCP as a differentiator.

Why does BAND show No for self-hosting?

BAND is a hosted (SaaS) platform. band.ai says agents connected to BAND can run on different clouds (AWS, GCP, on-prem), but it does not document self-hosting BAND itself.

Why is AutoGen not in the matrix?

AutoGen is in maintenance mode. We compare it on two vs pages and recommend Microsoft Agent Framework for new work.