Continue starts every session with no memory of the last one
One server fixes that.
Your decisions. Your stack. Where you left off. Add MemoryRouter as a remote MCP server and Continue can pull it all back.
Two minutes. Permanently.
14 days free
Full access. Connect it, ask Continue to remember, cancel anytime.
See the difference
You: Pick up the API redesign from yesterday
Continue: I do not have context on a prior redesign in this session. What were the goals and constraints?
A new session, and yesterday's work is gone.
You: Check memory, then pick up the API redesign from yesterday
Continue: Found it: moving to versioned routes, keeping the old ones deprecated for 90 days. Starting with the router config.
One tool call, and it is caught up.
Sound familiar?
Re-pasting architecture notes into every new session
Switching from chat mode to agent mode and losing the thread
Decisions from last week, gone
With MemoryRouter
search_memories and store_memory show up as MCP tools in agent mode
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 Continue in two minutes
Continue supports remote MCP servers with OAuth. Add the server, sign in once, done.
mcpServers:
- name: MemoryRouter
type: streamable-http
url: https://mcp.memoryrouter.ai/mcpComing from Claude, Cursor, or Cline? Continue also auto-loads JSON MCP config files dropped in .continue/mcpServers/.
MCP servers only run in agent mode. Switch modes, open the MCP servers list, and complete the OAuth sign-in for memoryrouter. Save a unique fact in one session, start a new one, and ask Continue 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 Continue Model Response (gone when the session ends)
With MemoryRouter:
You Continue (calls search_memories or store_memory over MCP, agent mode) Model Response
This is model-directed recall, not an automatic hook, and it only runs in agent mode. Your Continue 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 config.yaml.
Explicit tools
search_memories, store_memory, and date_search_memories show up in Continue's agent mode tool list.
Local or hub config
Add it to your local config.yaml, or publish the block to a shared Continue Hub assistant for your team.
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 Continue a memory tonight
14 days free. Two minutes to connect. Tomorrow's first session already knows everything from today.