Memory Bank MCP Server
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 |
|---|---|
| van_modeC | Initialize project and determine complexity level. Entry point for the Memory Bank system. |
| plan_modeC | Create detailed implementation plan based on complexity level |
| creative_modeC | Design and architecture work for complex components |
| implement_modeC | Execute the implementation based on plan and creative decisions |
| reflect_archive_modeC | Reflect on implementation and archive documentation |
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 has a clearly distinct purpose in the Memory Bank workflow: creative_mode for design, implement_mode for execution, plan_mode for planning, reflect_archive_mode for reflection/documentation, and van_mode for initialization. There is no overlap or ambiguity between these tools as they represent sequential stages in a project lifecycle.
All tool names follow a consistent pattern of descriptive_verb_mode (e.g., creative_mode, implement_mode, plan_mode). This uniform naming convention makes the tool set predictable and easy to understand, with no deviations in style or structure.
With 5 tools, this server is well-scoped for its purpose of managing a Memory Bank system workflow. Each tool earns its place by covering a distinct phase from initialization to reflection, avoiding bloat while ensuring comprehensive coverage of the project lifecycle.
The tool set provides complete lifecycle coverage for the Memory Bank domain: van_mode initializes projects, plan_mode creates plans, creative_mode handles design, implement_mode executes, and reflect_archive_mode concludes with reflection and archiving. There are no obvious gaps, and the tools support a seamless workflow from start to finish.