Cursor forgets your project the moment the chat ends
One server fixes that.
Your decisions. Your stack. Where you left off. Add MemoryRouter as a remote MCP server and Cursor can pull it all back.
Two minutes. Permanently.
14 days free
Full access. Connect it, ask Cursor to remember, cancel anytime.
See the difference
You: Finish the auth refactor we started
Cursor: I do not have context on a prior refactor in this chat. Which files, and what approach did you want?
A new chat, and you are re-explaining yesterday's decisions.
You: Check my memory, then finish the auth refactor we started
Cursor: Found it: moving session checks into middleware, keeping the legacy cookie path behind the flag we agreed on. Starting with routes/auth.ts.
One tool call, and it is caught up.
Sound familiar?
Re-pasting architecture notes into every new chat
Starting a new conversation and losing yesterday's context
Decisions you made last week, gone
With MemoryRouter
search_memories and store_memory show up as MCP tools Cursor can call
Ask it to check your memory and it recalls the relevant history
Tell it to remember something and it is there in every future chat
14-day free trial. Cancel anytime.
Connect Cursor in two minutes
Cursor supports remote MCP servers with OAuth built in. Add the server, sign in once, done.
{
"mcpServers": {
"memoryrouter": {
"url": "https://mcp.memoryrouter.ai/mcp"
}
}
}Open Cursor Settings > MCP, find memoryrouter, and enable it. Cursor opens your browser to sign in and choose the vault it should use. Save a unique fact in one chat, start a new chat, and ask Cursor to check its memory for it. That is the moment it clicks.
Sign up free, then add the server above.
How it works
Without MemoryRouter:
You Cursor Model Response (gone when the chat ends)
With MemoryRouter:
You Cursor (calls search_memories or store_memory over MCP) Model Response
This is model-directed recall, not an automatic hook. Cursor decides when to call the memory tools, the same way it decides when to search your codebase. Your Cursor account, model choice, and inference stay exactly where they are. MemoryRouter only stores and retrieves memories.
One config, no key file
Add a URL, not a secret. OAuth handles sign-in, so there is no API key sitting in mcp.json for a teammate or a repo to leak.
Explicit tools
search_memories, store_memory, and date_search_memories show up in Cursor's MCP tool list, so you can see exactly what it can do.
Works everywhere Cursor does
Same config in every project once set globally, or scope it per project with a local .cursor/mcp.json.
Same memory everywhere else
One vault. Connect it to Claude, ChatGPT, or Claude Code and the memory follows you between tools.
Connect in two minutes. 14-day free trial.
Start free. Then just $20/mo.
14-day free trial. Cancel anytime.
- 200M memory tokens / mo included
- Unlimited projects
- Same memory in ChatGPT, Claude, Claude Code, and Codex
- 300 to 500 ms average recall on a typical vault
- Your keys, your data, your control
No inference markup, ever.
FAQ
Give Cursor a memory tonight
14 days free. Two minutes to connect. Tomorrow's first chat already knows everything from today.