Cline Memory Bank
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| initialize_memory_bankB | Initialize Memory Bank structure for a project |
| update_contextB | Update active context with current session information |
| record_decisionB | Add a new technical decision with rationale and metadata |
| track_progressC | Update project progress and milestones |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Project Context | Project overview, technical stack, and guidelines |
| Active Context | Current session state and tasks |
| Progress Log | Project milestones and task tracking |
| Decision Log | Technical decisions and rationale |
TDQS
Scored across 4 tools
Each tool has a clear, distinct purpose: initialization, decision recording, progress tracking, and context updating with no overlaps.
All tool names follow a consistent verb_noun pattern in lowercase snake_case, making them predictable.
Four tools are well-scoped for a memory bank server, covering essential operations without excess or deficiency.
Core memory bank operations are covered, but retrieval and search capabilities are missing, which is a minor gap.