Visual memory manager for AI agents. MCP-native, MIT-licensed, free forever.
AgentMemory has well-structured tool definitions with clear naming (verb_noun pattern), comprehensive schemas with type constraints, and good descriptions. However, parameter descriptions lack depth in several tools, output schemas are not explicitly documented, and error handling guidance is minimal. The server demonstrates solid foundational quality but falls short of production-grade polish. All 10 tools have explicit registration with schemas visible in mcp/server.ts.
Save a new memory rule/fact about the project. Use this whenever the user states a preference, decision, constraint, or piece of context that should persist across sessions.
Generate pgvector embeddings for memories that have none. Only useful on the Supabase backend with HUGGINGFACE_API_KEY set. Idempotent and rate-limited: call repeatedly until remaining=0. Each call costs ceil(N/32) embedding API requests.
Delete a memory by ID.
Find memories semantically similar to a given text or to an existing memory. Useful for deduplication before adding new rules.
Get all rules for the current active project, formatted as a markdown document. Use this at the start of a task to load project context.
Import a Claude Code / OpenCode / Codex JSONL session log. Parses user messages, applies heuristic category detection, and creates memories. Use this to backfill memory from past sessions.
Output schemas not documented. Tools return Memory objects or lists, but LLMs cannot see the structure of returned fields (id, content, category, tags, importance, project_name, source, etc.). This forces LLMs to guess field names for downstream operations.
Parameter descriptions lack actionable constraints. 'query' in search_memories has no guidance on format, length, or expected content. 'limit' lacks min/max rationale. 'importance' in add_memory has no explanation of what 1-5 means semantically.
Error handling lacks recovery guidance. No tool description explains what to do if a memory is not found, if a project doesn't exist, or if import_jsonl fails to parse. LLMs receive no actionable next steps.
Inferred effective spec: 2026-07-28+.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 58 | 2026-07-28+ | v2 |
List all memories, optionally filtered by project and/or category.
List all project names that have memories.
Search through saved memories by keyword. Returns matching rules/facts.
Switch the active project context (affects which project new memories are saved to).
Destructive operations (delete_memory, import_jsonl) lack confirmation or dry-run support. Agents can permanently delete memories or overwrite projects without a safety gate. No idempotency guarantees stated.
Tool descriptions are generic and lack WHEN-to-use guidance. 'List all memories' does not explain when to call this vs search_memories. 'Find memories semantically similar' does not explain the use case (deduplication before adding) clearly enough for LLM selection.