Score breakdown
Popularity is tracked separately. Support, ads, sponsorships, and tips never affect these signals.
Why it matters
Most coding-agent developers today who want their agent to plug into a code editor (Zed / VS Code / JetBrains) have been either (a) writing custom JSON-RPC bridges per editor (no canonical protocol), (b) reaching for non-standard integrations like stdin / stdout file-watch that require custom agent-side code, or (c) maintaining separate transport layers per editor. agentclientprotocol/agent-client
Who should use it
Who should skip it
Consider ACP: Apache-2.0 Open Standard (Current Stable v1) for Connecting Any Code Editor to Any Coding Agent (JSON-RPC, 5 SDKs) lower priority if you already have a working solution in this category.
About this signal
ACP: Apache-2.0 Open Standard (Current Stable v1) for Connecting Any Code Editor to Any Coding Agent (JSON-RPC, 5 SDKs) is tracked by RepoRadar as a tool in the Radar section. It was first seen on 2026-07-08 and last updated on 2026-07-08. The current verdict is 'try now' with a Gold tier and moderate setup difficulty. Across RepoRadar's eight signals, ACP: Apache-2.0 Open Standard (Current Stable v1) for Connecting Any Code Editor to Any Coding Agent (JSON-RPC, 5 SDKs) is strongest on workflow potential (10.0) and practical usefulness (9.0) and weakest on setup ease (6.4) — a profile worth weighing against your own priorities. This page summarizes the evidence RepoRadar has captured from captured source metadata. The score, tier, risk label, and verdict on this page are never influenced by sponsorship, ads, or tips — they reflect only the usefulness, popularity, novelty, momentum, maturity, and evidence signals described in the RepoRadar methodology.
How this item is evaluated
RepoRadar assigned ACP: Apache-2.0 Open Standard (Current Stable v1) for Connecting Any Code Editor to Any Coding Agent (JSON-RPC, 5 SDKs) a composite score of 9.0 out of 10, placing it in the Gold tier. This score combines weighted sub-signals: usefulness (35%), novelty (18%), momentum (14%), maturity (10%), open-source/build quality (7%), evidence quality (6%), workflow potential (6%), and setup ease (4%). Popularity is tracked separately at 0.0 and never affects the composite score or tier. The risk label of 'low' reflects inherent user-impacting hazards, not generic novelty. Items with no risk flag may still require normal code review before production use.
Putting this into practice? Read How to vet an AI agent or MCP server before you wire it in for the checklist behind this score.
Risk explanation
The 3; 600* / 296-fork / 16-subscriber repo is at active maintenance with the protocol v1 stable but the consumer SHOULD note the project is a protocol + SDK bundle (not a single binary); so adoption requires integrating one of the 5 SDKs (Rust / Kotlin / Java / Python / TypeScript) into an existing editor or agent -- not a drop-in install; the consumer SHOULD note the protocol is JSON-RPC over stdio / WebSocket.