Skip to content
// Integrations

Works with the tools your team already runs.

Virex Memory reaches every MCP-compatible coding client, so support follows the protocol rather than a hand-written integration list. Virex Remote is built specifically around Claude Code.

// Two products, different integration stories. This page states both plainly.

// Why the two lists differ

One follows a protocol. One follows a product.

It would be easier to claim both products work everywhere. It would also be untrue, so here is the actual reason the lists are different lengths.

Memory follows the protocol

Virex Memory is reached over MCP. Any client that speaks the protocol discovers the same tools against the same organization memory, so the list grows without us shipping anything.

Remote follows Claude Code

Virex Remote is built around how Claude Code sessions run, pause for permissions, and gate on plan decisions. That specificity is what makes the oversight useful, and it is why we do not claim broader coverage.

// Where to go next

Pick the angle that fits.

By problem

The use-case pages start from a situation rather than a product, which is usually how people actually arrive.

By team shape

Solutions pages cover teams, enterprise, agencies, and individual developers separately.

By vocabulary

The glossary defines MCP, agent memory, permission requests, and the rest of the category language.

Use cases, solutions, and the glossary.

Connect what you already use.

Subscribe, assign a seat, and point your tools at your organization memory. Remote adds oversight for Claude Code sessions on top.