Cursor in JetBrains IDEs

Source: Cursor Date: 2026-03-04 URL: https://cursor.com/changelog/03-04-26

Summary

Cursor expands to JetBrains IDEs (IntelliJ IDEA, PyCharm, WebStorm, and others) via the Agent Client Protocol (ACP), installable from the ACP Registry using existing Cursor credentials. The integration brings Cursor’s full model routing (OpenAI, Anthropic, Google, and Cursor models) and agent-driven workflows to developers who prefer JetBrains for Java and multi-language development.

Implications

Agent-IDE feature race. ACP-based JetBrains integration is a significant market expansion — JetBrains has ~12M developers, skewed toward enterprise Java/Kotlin/Python. This directly challenges GitHub Copilot (which has a JetBrains plugin) and Windsurf’s VS Code focus. Cursor moving beyond its VS Code fork via a protocol-based integration signals a platform strategy rather than a single-editor product.

MCP/protocol adoption. The Agent Client Protocol (ACP) is distinct from MCP — it’s a host-agnostic protocol for embedding Cursor’s agent layer in foreign IDEs. This is an underreported architectural move: if ACP gains traction, Cursor becomes an agent runtime that lives inside other editors, not just its own.

Watch: Whether ACP becomes an open standard (like MCP) or stays Cursor-proprietary, and whether JetBrains itself ships a competing native agent layer in response.