Cascade forgets your project the moment the conversation ends
One server fixes that.
Your decisions. Your stack. Where you left off. Add MemoryRouter as a remote MCP server and Cascade can pull it all back.
Two minutes. Permanently.
14 days free
Full access. Connect it, ask Cascade to remember, cancel anytime.
See the difference
You: Finish the migration we planned
Cascade: I do not see a prior plan in this conversation. What is the target schema and the constraints?
A new conversation, and yesterday's plan is gone.
You: Check memory, then finish the migration we planned
Cascade: Found it: Postgres 16, the users table split, zero-downtime constraint. Starting with the backfill script.
One tool call, and it is caught up.
Sound familiar?
Re-pasting context into every new conversation
Cascade losing the thread when a conversation resets
Decisions from last week, gone
With MemoryRouter
search_memories and store_memory show up as MCP tools Cascade can call
Ask it to check memory and it recalls the relevant history
Tell it to remember something and it is there next time
14-day free trial. Cancel anytime.
Connect Windsurf in two minutes
Cascade supports remote MCP servers with OAuth. Add the server, sign in once, done.
{
"mcpServers": {
"memoryrouter": {
"serverUrl": "https://mcp.memoryrouter.ai/mcp"
}
}
}Open Cascade's MCP settings panel (hammer icon), find memoryrouter, and refresh. Windsurf opens your browser to sign in and choose the vault it should use. Save a unique fact in one conversation, start a new one, and ask Cascade 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 Cascade Model Response (gone when the conversation ends)
With MemoryRouter:
You Cascade (calls search_memories or store_memory over MCP) Model Response
This is model-directed recall, not an automatic hook. Cascade decides when to call the memory tools, the same way it decides when to search the web. Your Windsurf 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 MemoryRouter key sitting in mcp_config.json.
Explicit tools
search_memories, store_memory, and date_search_memories show up in Cascade's MCP tool list, so you can see exactly what it can do.
Global or per-project
Set it once in your global mcp_config.json, or scope a separate config to a specific workspace.
Same memory everywhere else
One vault. Connect it to Claude, ChatGPT, Cursor, 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 Cascade a memory tonight
14 days free. Two minutes to connect. Tomorrow's first conversation already knows everything from today.