claude-agent-acp: Bridges Claude Agent SDK with ACP standard
Project Overview
The Agent Client Protocol (ACP) is an emerging standard for agent-to-client communication, and this adapter from the team at agentclientprotocol.com bridges it directly with Anthropic’s Claude Agent SDK. Rather than being a standalone agent or a client itself, this TypeScript package acts as a translation layer: it wraps the official Claude Agent SDK to expose its capabilities through the ACP interface. This means any ACP-compatible client can now drive Claude agents without needing bespoke integration work. The project currently sits at v0.32.0[1] with 1,823 stars[2], indicating strong early interest from the agent ecosystem. The architectural bet here is on protocol standardization rather than building yet another monolithic tool — the adapter pattern lets the community mix and match agents and clients, which is a refreshingly modular approach compared to the tightly coupled agents we’ve seen from other vendors.
What It’s For
This adapter is for developers building or using agentic workflows who want to decouple their clients from their agent backends. If you’re running an ACP-compatible client — whether that’s a custom dashboard, a CLI, or a third-party tool — and you want to use Claude as the underlying agent, this package handles the translation. It supports context @-mentions, image inputs, tool calls with permission requests, following, edit review, TODO lists, interactive and background terminals, custom slash commands, and client MCP servers[1]. The main tradeoff is that you’re locked into Claude’s SDK for the agent logic; if you need multi-model support or want to swap agents frequently, you’d be better served by a more generic ACP agent implementation. But if Claude is your target, this adapter is the most direct path.
How to Use It
The primary workflow is installing the npm package and using it as a bridge between your ACP client and the Claude Agent SDK. You initialize the adapter with your Claude API credentials and any custom configuration (like slash commands or MCP server endpoints), then the adapter handles the protocol translation automatically. The README suggests the setup is straightforward: import the adapter, configure it with your Claude SDK instance, and point your ACP client at the adapter’s endpoints. There’s no complex state management to build yourself — the adapter manages the conversation context, tool call lifecycle, and permission flows internally.
Install the adapter package from npm
npm install @agentclientprotocol/claude-agent-acpImport the adapter factory function to create an ACP-compatible agent from your Claude SDK instance
import { createAcpAgent } from '@agentclientprotocol/claude-agent-acp'Recent Updates
Latest Release: v0.32.0 (2025-07-17)
Latest release in a rapid iteration cycle; the project has seen 32 minor versions since inception.
The commit history shows a project under active development with frequent releases — the jump from v0.31.1 to v0.32.0 suggests the team is iterating quickly based on community feedback. The ACP standard itself is still evolving, so this adapter’s trajectory is tightly coupled to protocol changes and Claude SDK updates.
Sources & Attributions
[1] v0.32.0 (agentclientprotocol/claude-agent-acp) — agentclientprotocol/claude-agent-acp [2] 1,823 stars as of July 2025 (agentclientprotocol/claude-agent-acp) — https://github.com/agentclientprotocol/claude-agent-acp