collective-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| OPENAI_API_KEY | Yes | OpenAI API key for embeddings | |
| COLLECTIVE_MEMORY_PATH | No | Storage location for persistent memory (default: ~/.collective-memory/data) | ~/.collective-memory/data |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| rememberA | Persist important context to collective memory. Use after decisions, completed work, architectural choices, status changes. Be specific and self-contained. |
| recallA | Search collective memory. Use at session start, when switching context, when referencing past work. |
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 2 tools
Each tool has a clear, distinct purpose: one for storing context and one for retrieving it, with no functional overlap.
Both tool names are single verbs that follow a consistent pattern, making them predictable and easy to distinguish.
Two tools is minimal but appropriate for a focused read/write memory server; slightly thin but not excessive.
The server covers core create and read operations but lacks update or delete functionality, which could hinder management of stored memories.