AIVM Brain gives Cursor governed, persistent memory over MCP. One command from the dashboard patches Cursor's MCP config; from then on Cursor can recall your decisions, docs, and project facts, and capture new ones as you work. Permission-aware for teams, audited end to end, free to start.
Connect Cursor with one command
The dashboard generates a personalized command that adds the brain to Cursor's MCP configuration.
Create your brain and pick Cursor. Sign up free at brain.aivm.io, open Connect, choose Cursor, and generate your key.
Run the command, restart Cursor. The generated npx command patches Cursor's MCP config with your key. Restart Cursor so it picks the server up.
npx @aivm/brain init --host cursor # personalized command comes from your dashboard
Recall something in a new window. Store a fact from one project window, open a different project, and ask for it. Cross-project recall is what a rules file cannot do.
Rules files stop at the repo boundary
Cursor's rules are per-project by design. That is correct for coding conventions and exactly wrong for knowledge. The reason you chose Postgres over Dynamo, the auth quirk that bit you in March, the vendor API's undocumented rate limit: none of that belongs in a rules file, and all of it is what you re-explain to your editor every week.
The brain sits outside the repo, so your Cursor sessions share one memory across every project and every machine. Ask in the editor, get the answer with its provenance, keep moving.
Your whole team's context, scoped per person
On a team, Cursor plus a shared brain means the frontend dev's editor knows what the platform team decided last week, without anyone writing a wiki page about it. Retrieval is permission-aware: each member's key sees what their role allows and nothing more, with field-level redaction for the sharp edges (a doc can be recallable while its salary column is not). Every recall is written to a tamper-evident ledger, which is what makes a shared brain survivable in a security review.