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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_memory_sessionD | – |
| store_memoryD | – |
| revise_memoryD | – |
| create_collectionD | – |
| merge_collectionD | – |
| analyze_memoriesD | – |
| export_session_to_fileD | – |
| export_memories_to_fileD | – |
| create_project_structureD | – |
| load_project_contextD | – |
| update_project_indexC | Update specific section in project_knowledge_index.md |
| discover_packagesB | Discover available packages and their APIs |
| validate_package_usageB | Validate if code uses existing packages appropriately |
| explore_existing_apisC | Explore existing APIs that might provide the needed functionality |
| store_codebase_patternC | Store a codebase pattern for future reference |
| load_codebase_contextC | Load existing codebase structure and patterns into memory |
| prevent_reinvention_checkB | Check if functionality might already exist in known packages |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| memory_guide |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_memory_tree | |
| get_analysis | |
| get_patterns | |
| get_discovered_packages | Get discovered packages in the current session |
| get_codebase_patterns | Get stored codebase patterns |
| get_validation_checks | Get validation checks for the current session |
TDQS
Scored across 17 tools
The tools have overlapping purposes that could cause confusion, such as load_codebase_context and load_project_context, or create_memory_session and create_collection. However, many tools like discover_packages, explore_existing_apis, and prevent_reinvention_check have distinct functions, and descriptions help clarify some overlaps, preventing complete ambiguity.
Most tools follow a consistent verb_noun pattern (e.g., analyze_memories, create_collection, export_memories_to_file), with only minor deviations like prevent_reinvention_check and update_project_index. The naming is readable and predictable overall, though not perfectly uniform.
With 17 tools, the count is borderline heavy for a memory or codebase management server, as it might feel overwhelming. However, given the broad scope implied by tools like discover_packages and validate_package_usage, it's not unreasonable, but could benefit from consolidation to improve focus.
The tool set covers core memory and project management operations well, including creation, revision, export, and validation. Minor gaps exist, such as no explicit delete or search tools for memories or collections, but agents can likely work around these with existing tools like analyze_memories or merge_collection.