930aaeb
CopilotKitDocs
  • Docs
  • Integrations
  • Reference
Get Started
QuickstartCoding Agents
Concepts
ArchitectureGenerative UI OverviewOSS vs Enterprise
Agentic Protocols
OverviewAG-UIAG-UI MiddlewareMCPA2A
Build Chat UIs
Prebuilt Components
CopilotChatCopilotSidebarCopilotPopup
Custom Look and Feel
CSS CustomizationSlots (Subcomponents)Fully Headless UIReasoning Messages
Multimodal AttachmentsVoice
Build Generative UI
Controlled
Tool-based Generative UITool RenderingState RenderingReasoning
Your Components
Display ComponentsInteractive Components
Declarative
A2UIDynamic Schema A2UIFixed Schema A2UI
Open-Ended
MCP Apps
Adding Agent Powers
Frontend ToolsShared State
Human-in-the-Loop
HITL OverviewPausing the Agent for InputHeadless Interrupts
Sub-AgentsAgent ConfigProgrammatic Control
Agents & Backends
Built-in Agent
Backend
Copilot RuntimeFactory ModeAG-UI
Runtime Server AdapterAuthentication
AG2
Shared state
Reading agent stateWriting agent state
Readables
Observe & Operate
InspectorVS Code Extension
Troubleshooting
Common Copilot IssuesError Debugging & ObservabilityDebug ModeAG-UI Event InspectorHook ExplorerError Observability Connectors
Enterprise
CopilotKit PremiumHow the Enterprise Intelligence Platform WorksHow Threads & Persistence WorkObservabilitySelf-Hosting IntelligenceThreads
Deploy
AWS AgentCore
What's New
Full MCP Apps SupportLangGraph Deep Agents in CopilotKitA2UI Launches with full AG-UI SupportCopilotKit v1.50Generative UI Spec SupportA2A and MCP Handshake
Migrate
Migrate to V2Migrate to 1.8.2
Other
Contributing
Code ContributionsDocumentation Contributions
Anonymous Telemetry
AG2What's NewA2A and MCP Handshake

A2A and MCP Handshake

AG-UI handshakes enable seamless protocol interoperability

A2A and MCP Handshake

AG-UI now includes handshakes with both MCP and A2A protocols, ensuring smooth interoperability across the full agentic stack.

What Are Protocol Handshakes?#

Protocol handshakes allow AG-UI to seamlessly communicate with agents using different interaction protocols. This means you can connect your frontend to agents that internally use MCP or A2A without any additional configuration.

Benefits#

Full Interoperability#

If your host agent connects to subagents using MCP or A2A, their UI properties can be propagated all the way through to the user-facing application.

Security and Control#

Handshakes preserve full security, policy, and observability controls throughout the communication chain.

Simplified Architecture#

No need to choose between protocols—use them all together in a single application.

How It Works#

  1. Frontend connects via AG-UI - Your application uses AG-UI to connect to the host agent
  2. Host agent uses MCP/A2A - The host agent can communicate with subagents using MCP or A2A
  3. UI properties propagate - Generative UI and other properties flow back to your frontend automatically

Learn More#

  • AG-UI Protocol
  • MCP Integration
  • A2A Protocol
  • Agentic Protocols