agentclientprotocol/agent-client-protocol

Health v2 · maintenance only

Adoption not part of the score

4079 stars · 356 forks observed · 2026-08-28

What it is AI-extracted, prompt v1, taxonomy v1, 2026-08-29, confidence not recorded

The Agent Client Protocol (ACP) is an open protocol, with a Rust schema crate and JSON Schema artifacts, that standardizes communication between code editors/IDEs and AI coding agents via JSON-RPC over stdio or remote transports. It decouples editors from agents so any ACP-compatible agent works with any ACP-compatible editor, analogous to how LSP standardized language servers.

Use cases

• connect a coding agent to any editor without custom integrations
• implement an ACP-compatible AI coding agent in Rust
• build editor support for third-party AI agents
• generate SDKs for the ACP protocol from JSON Schema artifacts
• run AI agents as local subprocesses or remote services from an IDE
• standardize agent-editor communication like LSP did for language servers

When to choose

• you are building an editor or IDE that needs to talk to multiple AI coding agents
• you are implementing a coding agent and want broad editor compatibility
• you need Rust types or JSON Schemas for the ACP wire protocol
• you want to avoid per-editor, per-agent custom integration work

When to avoid

• you need a ready-to-use coding agent or editor rather than a protocol library
• your agent only targets a single editor with its own native API
• you need a higher-level runtime API rather than the low-level schema crate (use the agent-client-protocol runtime crate instead)

Facets

library · maturity active

rpc sdk serialization developer-tools developer-tools artificial-intelligence apis text-editors cross-platform rust cli agent-client-protocol -rpc coding-agents editor-integration protocol schema lsp-analog ai-agents

Member repositories

For agents

markdown · JSON · MCP: product_card(name="agentclientprotocol/agent-client-protocol")