agent-memory-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MEMORY_DEBUG | No | Set to "1" for info logs, "verbose" for debug | |
| MEMORY_DB_PATH | No | Path to SQLite database | ~/.agent-memory/memory.db |
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 |
|---|---|
| memory_storeB | Store a new memory with provenance tracking. Use for lessons learned, strategic insights, operational facts, or preferences. |
| memory_recallB | Recall memories ranked by decay-weighted relevance. Supports keyword search and category/tag filtering. Returns memories with provenance and confidence scores. |
| memory_feedbackA | Record whether a recalled memory was useful. This drives the learning flywheel — memories marked useful bubble up, unused ones decay away. |
| memory_statsB | Get statistics about the memory store (counts, categories, avg confidence). |
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 clearly distinct purpose: memory_feedback for rating usefulness, memory_recall for retrieving memories, memory_stats for analytics, and memory_store for creating new memories. There is no overlap or ambiguity in their functions.
All tool names follow a consistent 'memory_' prefix with a descriptive suffix (feedback, recall, stats, store), using snake_case uniformly. This pattern is predictable and enhances readability.
With 4 tools, the server is well-scoped for managing agent memory, covering core operations like storing, recalling, providing feedback, and viewing statistics. Each tool earns its place without being excessive or insufficient.
The tool set provides complete CRUD-like coverage for the memory domain: store (create), recall (read), feedback (update/rate), and stats (monitor). There are no obvious gaps, supporting a full lifecycle from storage to decay management.