Cline forgets your project the moment the task ends
One server fixes that.
Your decisions. Your stack. Where you left off. Add MemoryRouter as a remote MCP server and Cline can pull it all back.
Two minutes. Permanently.
14 days free
Full access. Connect it, ask Cline to remember, cancel anytime.
See the difference
You: Continue the refactor we planned yesterday
Cline: I do not have context on a prior plan in this task. What files and approach did you have in mind?
A new task, and yesterday's plan is gone.
You: Check memory, then continue the refactor we planned yesterday
Cline: Found it: moving session checks into middleware, legacy cookie path stays behind a flag. Starting with routes/auth.ts.
One tool call, and it is caught up.
Sound familiar?
Re-pasting architecture notes into every new task
Starting a new task and losing yesterday's context
Decisions you made last week, gone
With MemoryRouter
search_memories and store_memory show up as MCP tools Cline 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 Cline in two minutes
Cline supports remote MCP servers with OAuth. Add the server, authenticate once, done.
{
"mcpServers": {
"memoryrouter": {
"type": "streamableHttp",
"url": "https://mcp.memoryrouter.ai/mcp"
}
}
}Open it from Cline's MCP Servers icon > Configure MCP Servers, or edit the file directly.
Cline detects the server needs authentication and opens your browser to sign in and choose the vault it should use. Save a unique fact in one task, start a new one, and ask Cline 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 Cline Model Response (gone when the task ends)
With MemoryRouter:
You Cline (calls search_memories or store_memory over MCP) Model Response
This is model-directed recall, not an automatic hook. Cline decides when to call the memory tools, the same way it decides when to use any other MCP tool. Your Cline 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 cline_mcp_settings.json.
Explicit tools, per-tool approval
search_memories, store_memory, and date_search_memories each get their own approve or auto-approve toggle in Cline's MCP panel.
Global or per-project
Set it once in the global settings file, or scope a project-level MCP 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 Cline a memory tonight
14 days free. Two minutes to connect. Tomorrow's first task already knows everything from today.