Cursor, sharing memory with everything else you run.
Cursor connects to Virex Memory over MCP, reading and writing the same organization-scoped corpus as the rest of your toolchain. Virex Remote is a different story, and this page says so directly.
- Not supported: Virex Remote
- Supported: Virex Memory
Remote control for Cursor
The honest answer, stated plainly rather than buried.
Virex Remote does not support Cursor. Remote is built specifically around how Claude Code sessions run, pause for permission requests, and gate on plan decisions, and that specificity is what makes the oversight worth having. Claiming generic coverage would make the product worse and the claim untrue.
Memory for Cursor
Support follows the Model Context Protocol, so Cursor works with the same memory as every other compatible client, with no bespoke integration in between.
Memory tools over MCP
Cursor discovers the memory tools through the protocol and uses them while working, rather than waiting for a person to paste context in.
Retrieval by meaning
Semantic search returns what is relevant without needing the exact wording an earlier session used.
The same corpus as your other tools
A memory written from Claude Code is retrievable from Cursor and the reverse, because the scope is your organization rather than the client.
Maintained automatically
Relevance scoring is refreshed on a schedule and stale memories expire, so nobody owns a curation chore.
This is the practical argument for a protocol rather than per-tool integrations: a mixed toolchain stops fragmenting what your team knows.
What setup involves.
The account steps are the same for every tool. The connection step is where they differ, and that detail lives in the docs.
Create your account and organization
One login covers every Virex surface. Each user belongs to exactly one organization.
Subscribe to Virex Memory
Checkout starts your organization subscription, or adds Memory as another line item if you already run Virex Remote.
Assign seats
A seat grants a member access. One seat covers every MCP client that member uses, rather than one per tool.
Connect Cursor
Point it at the Virex Memory MCP server so it can read and write your organization memory.
Configuration steps for Cursor live in the docs.
Cursor questions
Does Virex Memory work with Cursor?
Yes. Cursor speaks the Model Context Protocol, so it reads and writes the same organization-scoped memory as every other MCP-compatible client.
Does Virex Remote work with Cursor?
No. Virex Remote is built around Claude Code sessions specifically. We would rather say that plainly than imply coverage we do not have.
Can I use Cursor and Claude Code against the same memory?
Yes, and that is the point of putting memory behind a protocol. Both read and write the same organization memory, so context does not fragment across tools.
Do I need a separate seat for each tool?
No. Seats are per member per product, not per tool. One Virex Memory seat covers every MCP client you use.
What if my team switches away from Cursor later?
Your memory is unaffected. It belongs to your organization rather than to a tool, so changing clients does not reset what your agents know.
One memory, whichever agent you run.
Subscribe to Virex Memory, assign a seat, and connect Cursor alongside everything else.