Overview

CopilotKit connects to your agents through the Agentic Protocol of your choice

CopilotKit is fully compatible with three major agentic protocols: AG-UI, MCP, and A2A.

Agentic Protocols - Venn Diagram

Connection

Protocol

Purpose

Agent ↔ User InteractionAG-UI

(Agent-User Interaction Protocol)

The open, event-based standard that connects agents to user-facing applications. It enables real-time, multimodal, interactive experiences.

Agent ↔ Tools & DataMCP

(Model Context Protocol)

Open standard that lets agents securely connect to external systems: tools, workflows, and data sources.

Agent ↔ AgentA2A

(Agent to Agent)

Defines how agents coordinate and share work across distributed agentic systems.

Agent ↔ Generative UI

A2UI (Google)


MCP Apps (MCP Ecosystem)

Declarative, LLM-friendly generative UI specs that define what to render and how to structure agent responses visually. CopilotKit renders A2UI and MCP Apps.

Mixing and Matching Protocols

CopilotKit lets developers connect to any of these protocols directly or in combination. CopilotKit can connect to your agent backend through any of these protocols.

Any Agentic Backend

AG-UI middleware connects CopilotKit to A2A agents and MCP servers through one AG-UI agent. See A2A and AG-UI middleware.

This means that 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.

MCP and A2A through AG-UI

How is this guide?