memory-bank-mcp

⚠️ CALL THIS FIRST. Get comprehensive instructions for using the Memory Bank MCP server. Call this tool FIRST at the start of every session to understand the available tools and recommended workflow.

Initialize a Memory Bank in the specified directory

Set a custom path for the Memory Bank

Debug the current MCP configuration

Read a file from the Memory Bank. Returns content with ETag for optimistic concurrency control.

Write to a Memory Bank file. Supports optimistic concurrency control via ifMatchEtag.

List Memory Bank files

Check Memory Bank status

Migrate Memory Bank files from camelCase to kebab-case naming convention

Get all Memory Bank files in a single response for quick context loading. Returns all core files (product-context, active-context, progress, decision-log, system-patterns) as a combined JSON object.

Get a compact summary of the Memory Bank for context-limited situations. Returns recent progress entries, current tasks, known issues, and recent decisions.

Search across all Memory Bank files with full-text search

Create a backup of the current Memory Bank state, or list existing backups. Backups are stored in the parent directory with timestamped names.

Restore the Memory Bank from a specified backup. By default, creates a backup of the current state before restoring.

Add a structured progress entry to the Memory Bank. Provides a type-safe API for logging progress with categories and metadata.

Add a timestamped session note to the active context. Useful for recording observations, blockers, or context that should persist.

Update the current tasks list in active context. Can add, remove, or replace tasks.

Read multiple Memory Bank files in a single request. More efficient than individual reads for loading context.

Write multiple Memory Bank files in a single request. Supports optimistic concurrency via ETags.

Track progress and update Memory Bank files

Update the active context file

Log a decision in the decision log

Switch to a specific mode, get current mode info, or manage UMB (Update Memory Bank) state. Call with no parameters to get current mode. Set umb:true to activate UMB, umb:false to deactivate.

Create or update an entity in the knowledge graph. If an entity with the same name exists, it will be updated.

Add an observation about an entity. Observations are facts, notes, or information associated with entities.

Create or remove a directed relationship between two entities. Use action:"unlink" to remove a relationship.

Search the knowledge graph for entities and observations matching a query. Supports fuzzy matching on names and observation text.

Open specific nodes and their neighborhood. Returns a subgraph with the requested entities and their connections.

Delete an entity from the knowledge graph, or delete a specific observation if observationId is provided.

Perform maintenance operations on the knowledge graph: rebuild snapshot from event log, or compact event history.

List all registered Memory Bank stores. Returns the currently active store and any additional configured stores from the persistent registry.

Manage Memory Bank stores. Actions: select (switch active store), register (add to registry), unregister (remove from registry). Default action is "select" for backward compatibility.

Record a numbered thinking step for structured reasoning, or reset session history. Use this to break complex problems into sequential steps with optional branching and revision. The raw thought text is NOT returned — only metadata. Call finalize_thinking_session when done to persist outcomes to Memory Bank. Set reset:true to clear thinking history instead of recording a thought.

Persist the outcome of a thinking session into Memory Bank files. Accepts only human-facing summary fields — raw thoughts are NEVER persisted. Writes to existing Memory Bank files (active-context.md, decision-log.md, progress.md) via existing mechanisms.

Returns a budgeted, minimal "context pack" for a query by using the knowledge graph as an index. Reads only the smallest relevant slices of Memory Bank files instead of dumping full documents. Prefer this over get_context_bundle or batch_read_files for most questions.

Link a knowledge graph entity to a specific Memory Bank file (and optional heading). This helps get_targeted_context find the right file excerpts for a query. The file path is validated before saving.