Continue.dev Memory MCP
https://hub.continue.dev/continuedev/memory-mcp
Official Memory MCP (Mar 2025) backed by a knowledge graph. Memory is injected via MCP rather than native to the Continue core. Scope depends on MCP server deployment (local or shared).
At a glance
- Type
- KG-backed memory via MCP
- Tier
- T2
- Section
- Coding-agent memory
- Created
- 2023-06 (Continue.dev founded); Memory MCP March 2025
- Latest release
- not applicable — not OSS
- License
- not applicable — not OSS
- GitHub
- not applicable — no GitHub repo
- Pricing
- Free (OSS core); paid Continue Hub plans for teams (pricing on website)
- Funding
- $5.6M total raised: $2.1M (YCS23) + $3M SAFE led by Heavybit
Taxonomy
- storage
- graph
- retrieval
- graph-traversal
- persistence
- long-term
- update
- extraction
- unit
- fact
- governance
- inspectable
- conflict
- none
When to use
Optimised for: KG-backed memory across IDE sessions
Anti-fit: not for non-coding tasks
Pros & cons
Pros
Open-source IDE extension with MCP-based memory — choose your own memory backend.
Cons
Memory quality bounded by chosen MCP server; setup more involved than first-party offerings.
Claims & capabilities
Hub package continuedev/rules-memory ; community integrations add worktree-aware queries.
Technical surface
- API surface
- searched not found
- Backend storage
- searched not found
- Deployment
- Both (VS Code/JetBrains extension local + optional shared MCP server)
- Embedding model
- searched not found
- Multi-tenancy
- searched not found
- MCP
- native (first-party)
- A2A
- not supported
- OpenTelemetry
- OpenTelemetry via Continue Enterprise; OSS edition has local logs only
Similar systems
Other coding-agent memory in the catalog, ranked by inbound references.
- Aider T2
Appends conversation turns to .aider.chat.history.md in project root. restore_chat_history defaults to false — no automatic replay into new sessions. Community /session save command for JSON state snapshots. .aider.conf.yml carries static preferences.
- Augment Code T1
Real-time knowledge graph indexed from connected repos + commit history + CI/CD + tickets + docs. Separate Agent Memory layer (Sept 2025) captures session decisions/corrections/goals as discrete items with developer review/approval UI. MCP endpoint exposes the graph.
- Bolt.new (StackBlitz) T2
In-browser WebContainer (Rust-backed shared memory) is the implicit state store. No dedicated memory abstraction — project files are the state. Team plan adds shared workspaces + GitHub integration.
- Devin (Cognition) T1
Structured Knowledge items stored server-side. Three-tier scope: repo-pinned (always injected), global (recall by relevance), org/enterprise (visible to org members). Auto-generates Repo Knowledge from repo structure each session; reads past session trajectories for self-improvement; writes notes for recurring scheduled tasks.
- Lovable T2
Long-term context stored as files in /docs that the agent reads on each session. Agent Mode (default since July 2025) holds working context within session but doesn't persist cross-session beyond filesystem state.
- Mistral Vibe (Remote Agents) + Mistral Medium 3.5 T1
Vibe is Mistral's cloud-hosted coding-agent platform: each session runs in an isolated sandbox with task state, history, and approvals. Spawnable from CLI or Le Chat, with parallel execution. Local CLI sessions can be "teleported" to the cloud and resumed. Powered by Mistral Medium 3.5 (77.6% SWE-Bench Verified). Plugs into GitHub, Linear/Jira, Sentry, Slack/Teams.
Related systems
References (2)
- Model Context Protocol (MCP spec) depends on at runtime — Memory is injected via MCP rather than native to the Continue core. Scope depends on MCP server deploymen
- Official MCP Memory server builds on — Official Memory MCP (Mar 2025) backed by a knowledge graph. Memory is injected via MCP