agent-memory-hub
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| AGENT_MEMORY_DIR | No | Override the default storage directory for memories. Defaults to ~/.agent-memory/memories.json |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_memoryA | Store a new memory — fact, preference, project detail, note, or any information worth remembering. Tags and importance are auto-detected from content if not provided. |
| search_memoryA | Search memories using BM25 full-text search with importance and recency weighting. Supports optional tag filtering to narrow scope. |
| get_relevant_contextA | Auto-retrieve the most relevant memories for a given user query or task. Use this at the start of any session or when the user references past context. Returns formatted context ready to inject into your reasoning. |
| update_memoryB | Update the content, tags, or importance of an existing memory by key. |
| list_memoriesA | Browse stored memories with optional tag filtering and sort order. |
| forget_memoryA | Permanently delete a specific memory by key. |
| memory_summaryA | Get a high-level overview of what the agent knows — total count, top tags, most important memories, and access statistics. Good for orientation at session start. |
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 7 tools
Most tools have distinct purposes, but get_relevant_context and search_memory both retrieve memories based on relevance, which could cause confusion. However, descriptions differentiate automatic context retrieval from explicit search.
Majority follow verb_noun pattern (forget_memory, list_memories, search_memory, store_memory, update_memory). Two exceptions: get_relevant_context adds an adjective, and memory_summary inverts the order. Overall, mostly consistent with minor deviations.
7 tools is well-scoped for a memory management system. Each tool addresses a essential operation: create, read, update, delete, search, browse, and summarize, without unnecessary bloat.
Core CRUD and retrieval operations are covered. However, there is no direct 'get memory by key' tool; agents must infer keys from list or search results. This is a minor gap that agents can work around using existing tools.