Agent Compatibility Protocol (ACP) launches as the open standard for hosting and consuming agent capabilities across Cursor, Windsurf, Zed, and Cline — MCP-equivalent for the agent layer
ACP gives developer tools a shared spec for agent capability discovery and invocation, ending the per-IDE bespoke-integration tax. It positions itself as the MCP-equivalent for agent-level (not tool-level) interop across the IDE ecosystem — and the first cross-vendor agent-protocol with credible multi-vendor adoption.
The substantive piece is the protocol-layer differentiation. Model Context Protocol (MCP) operates at the tool-invocation tier; Agent Compatibility Protocol (ACP) operates one layer up at the agent-capability-discovery and orchestration tier. The distinction matters because the per-IDE bespoke-integration tax that MCP solved at the tool tier was being recreated at the agent tier through 2025; ACP closes that gap. Cursor, Windsurf, Zed, and Cline launching with day-one ACP support gives the protocol immediate multi-vendor credibility.
The competitive read against Windsurf Wave 13's multi-agent sessions is that the IDE category is restructuring along the agent-orchestrator vs single-agent-editor axis. ACP standardization enables the agent-orchestrator pattern at scale by removing the per-vendor integration cost; the H2 2026 IDE-procurement landscape will increasingly differentiate on orchestration sophistication rather than single-agent quality.
Morph LLM — Windsurf Alternatives Comparison → · Dev.to — Cursor vs Windsurf vs Zed AI IDE Showdown 2026 → · NXCode — Best AI Code Editor 2026: Cursor vs Windsurf vs Copilot vs Zed →