agent-memory
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PROVIDER | No | LLM provider to use (e.g., 'gemini', 'openai', 'ollama'). | |
| QDRANT_HOST | No | Host of the Qdrant vector database. | localhost |
| QDRANT_PORT | No | Port of the Qdrant vector database. | 6333 |
| OPENAI_API_KEY | Yes | API key for the LLM provider (e.g., Gemini or OpenAI). | |
| EMBEDDING_MODEL | No | Model used for generating embeddings. | |
| EXTRACTION_MODEL | No | Model used for fact extraction (Phase 1). | |
| EMBEDDING_DIMENSION | No | Dimension of the embedding vectors. | |
| RECONCILIATION_MODEL | No | Model used for conflict reconciliation (Phase 2). | |
| SIMILARITY_THRESHOLD | No | Threshold for semantic similarity. | 0.60 |
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 |
|---|---|
| remember_conversationA | Extracts durable facts from conversation text and reconciles them into long-term memory (ADD, UPDATE, DELETE, NOOP). Args: user_id: The unique identifier for the user. conversation_text: The conversation transcript or user statement to remember. |
| recall_memoriesA | Retrieves semantically relevant memories from vector storage given a natural language query. Args: user_id: The unique identifier for the user. query: The topic, question, or context to retrieve facts for. limit: Maximum number of memory records to return (default: 5). |
| list_user_memoriesA | Lists all active stored memories for a user. Args: user_id: The unique identifier for the user. limit: Maximum number of memories to return (default: 50). |
| forget_memoryA | Deletes a specific memory record by its unique ID. Args: memory_id: The UUID of the memory record to remove. |
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 4 tools
Each tool has a distinct core action: list, recall, remember, and forget. The only potential confusion is between list_user_memories and recall_memories, but the descriptions clearly separate 'all active memories' from 'semantically relevant' retrieval.
All tool names follow a consistent verb_noun snake_case pattern: list_user_memories, forget_memory, remember_conversation, recall_memories. The verbs are meaningful and align with their actions.
Four tools is a well-scoped size for a memory server, covering ingestion, retrieval, listing, and deletion. Each tool maps to a clear capability without redundant or excessive surface area.
The set covers the core memory lifecycle: adding memories, recalling them, listing them, and deleting them. A direct get-by-ID or explicit update tool is missing, but remember_conversation's reconciliation covers updates through its ADD/UPDATE/DELETE/NOOP behavior.