Integrations / Cursor
Stop re-explaining your codebase to Cursor every session
Cursor's context window is scoped to the project you have open. OmegaVault connects over MCP so architectural decisions, gotchas, and conventions from past sessions — even in other projects — are available the moment you open a new one.
Without OmegaVault
A decision made in one Cursor session — why a library was swapped, why a pattern was avoided — has no path to the next session unless it was written into a file Cursor happens to read.
FAQ
Does OmegaVault see my source code?
OmegaVault captures the decisions and context you and Cursor discuss, not your repository. See the docs link below for exactly what the MCP connection has access to.