MCP Roo Memory

What mcasdfgf/mcp-roo-memory MCP server does

mcasdfgf/mcp-roo-memory MCP server provides persistent memory for Roo Code through the Model Context Protocol. It represents stored information as a graph rather than as unrelated text fragments. Nodes can represent entities, facts, decisions, tasks, or other knowledge, and relations connect those nodes for retrieval and traversal.

The server also maintains a desktop-style context view with hot, cold, and archive tiers. Agents can restore a workspace, focus a node into active context, and inspect navigation history. This is intended to limit how much stored information is brought into an agent's current context while retaining older material for search.

How it works

Graph data and history are stored in SQLite. Semantic indexing uses Qdrant and fastembed, allowing vector searches based on meaning rather than exact keywords. Hybrid graph search combines semantic retrieval with expansion into related graph subgraphs.

Knowledge can be changed in place, replaced while preserving its history, or removed together with its vector entry. Relations can be traversed from a starting node, followed as reasoning chains, or explored chronologically. The temporal features include chronological graph walks, session timelines, and time-based vector filtering.

Workspace behavior can be global or project-specific. Desktop operations and graph writes use the selected project workspace, while vector searches can either span projects or be limited to one workspace through a workspace identifier.

Setup and configuration

The recommended deployment uses Docker Compose. Cloning the repository and running docker compose up -d starts a Qdrant container on port 6333 and a Cortex container that waits for MCP connections. Roo Code can then be configured to invoke the server inside the running container with Docker and python3 -m src.cortex.

For isolated project memory, the repository's .roo/ directory can be copied into a project and its MCP configuration can include a project-specific --workspace value. The included rules and instructions describe memory lifecycle behavior for several Roo Code modes.

A native installation is also documented for Python 3.11 or later. It uses an editable install from the cloned repository, but Qdrant remains a separate requirement and must still be run, such as through Docker. Native MCP configuration supports CORTEX_DB_PATH, CORTEX_QDRANT_HOST, and CORTEX_QDRANT_PORT.

Tools and capabilities

mcasdfgf/mcp-roo-memory MCP server exposes tools for:

• Opening, focusing, and inspecting workspace sessions.
• Creating, reading, updating, superseding, and deleting graph nodes.
• Adding relations, traversing graphs, and walking reasoning chains.
• Decomposing tasks into structured subtasks.
• Storing text with automatic vectorization and searching by meaning.
• Combining semantic search with graph expansion.
• Walking the graph by time and retrieving a session timeline.

Limitations and notes

The repository labels the software as experimental and a proof of concept. It is provided without warranty, so it should be evaluated before being used as the sole memory system for important workflows.