Memory Bank MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_BANK_ROOT | Yes | Directory where project memory banks will be stored |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_projectsB | List all projects in the memory bank |
| list_project_filesA | List all files within a specific project |
| memory_bank_readB | Read a memory bank file for a specific project |
| memory_bank_writeC | Create a new memory bank file for a specific project |
| memory_bank_updateC | Update an existing memory bank file for a specific project |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 5 tools
Each tool targets a distinct resource and action: listing projects, listing files within a project, reading a file, creating a file, and updating a file. There is no overlap or ambiguity between tools.
Names mix two conventions: 'list_projects' and 'list_project_files' use verb-first snake_case, while 'memory_bank_read', 'memory_bank_write', and 'memory_bank_update' use object-first with a modifier. The pattern is inconsistent but still readable.
Five tools is well-scoped for a memory bank server, covering the essential operations without unnecessary bloat. The count feels right for the domain.
The server covers list, read, create, and update of memory bank files, but it is missing a delete operation. This is a notable gap in CRUD coverage, though agents can work around it by archiving or overwriting files.