Memory Bank MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get-memory-bank-infoA | Read and return all Memory Bank file contents. This tool is similar to codelf's get-project-info:
|
| update-memory-bankB | Generate detailed Memory Bank file update instructions with immediate execution guidance. This tool provides comprehensive, actionable instructions for updating Memory Bank files:
|
| init-memory-bankA | Initialize memory-bank directory and core files. This tool will:
|
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 3 tools
Each tool has a clearly distinct purpose with no overlap: get-memory-bank-info reads existing files, init-memory-bank creates the initial structure, and update-memory-bank provides instructions for modifications. The descriptions reinforce these distinct roles, making misselection unlikely.
All tool names follow a consistent verb-noun pattern with hyphens (get-memory-bank-info, init-memory-bank, update-memory-bank), using clear action verbs aligned with their functions. There are no deviations in naming style or convention.
Three tools are appropriate for the server's purpose of managing a memory bank, covering initialization, reading, and updating. However, the scope feels slightly thin as there is no tool for deleting or archiving files, which could be useful for lifecycle management.
The tools cover core operations for a memory bank system: initialization, reading, and updating. A minor gap exists in lacking a delete or archive tool for full lifecycle coverage, but agents can likely work around this by using update-memory-bank to modify content as needed.