Moxie Docs MCP vs Mnemo MCP

add_memory

Store NEW information. Use for preferences, decisions, facts. ACTION GUIDE — when to use: - Use when saving new information for the first time. Example: content='User prefers dark mode', category='preference', tags=['ui']

search_memory

Find existing memories by natural language query. Always search before adding. ACTION GUIDE — when to use: - Use BEFORE adding new information to avoid duplicates. Example: query='dark mode preference'

list_memories

Browse all memories, optionally filtered by category. ACTION GUIDE — when to use: - Use when you want to view a broad set of memories, or see what's in a specific category. Example: category='preference', limit=10

update_memory

Modify an EXISTING memory by ID. Get memory_id from search results. ACTION GUIDE — when to use: - Use when an existing fact or preference changes. Example: memory_id='abc123', content='User now prefers light mode'

delete_memory

Remove a memory by ID. ACTION GUIDE — when to use: - Use when a memory is completely outdated, incorrect, or explicitly requested to be forgotten. Example: memory_id='abc123'

export_memories

Export all memories as JSONL. ACTION GUIDE — when to use: - Use when the user requests a backup or raw dump of their memory database.

import_memories

Import memories from JSONL data or a list of objects. ACTION GUIDE — when to use: - Use when restoring from a backup or migrating data into the memory system. Example: data='[{"content": "example"}]', mode='merge'

memory_stats

Show database statistics (total memories, categories, embedding status). ACTION GUIDE — when to use: - Use when you need to understand the scale or health of the memory database, or check if embeddings are enabled.

restore_memory

Restore an archived memory by ID. ACTION GUIDE — when to use: - Use to bring a previously archived memory back into the active search pool. Example: memory_id='abc123'

archived_memories

List archived memories. ACTION GUIDE — when to use: - Use to view memories that have been soft-deleted or automatically archived due to low importance/recency.

consolidate_memories

Summarize similar memories in a category (requires LLM API keys). ACTION GUIDE — when to use: - Use when a category has too many redundant or closely related memories and needs cleanup. Example: category='preference'

memory

[DEPRECATED — use the granular tools (add_memory, search_memory, ...) instead; this composite tool will be removed in a future release] Legacy dispatcher for backward compatibility. Use specialized tools (add_memory, search_memory, etc.) instead. Persistent memory store. Actions: add|search|list|update|delete|export|import|stats|restore|archived|consolidate. ACTION GUIDE — when to use each: - add: Store NEW information. Requires 'content'. Use when saving preferences, decisions, facts for the first time. Example: action='add', content='User prefers dark mode', category='preference', tags=['ui'] - search: Find existing memories by natural language query. Requires 'query'. Use BEFORE add to avoid duplicates. Example: action='search', query='dark mode preference' - update: Modify an EXISTING memory by ID. Requires 'memory_id' (from search/list results). Use when a fact changes. Example: action='update', memory_id='abc123', content='User now prefers light mode' - list: Browse all memories, optionally filtered by category. No query needed. - delete: Remove a memory by ID. Requires 'memory_id'. - stats: Show database statistics (total memories, categories, embedding status). - export: Export all memories to JSONL format. - import: Import memories from JSONL data. Requires 'data'. - archived: List archived memories. Optionally filter by limit. - restore: Restore an archived memory by ID. Requires 'memory_id'. - consolidate: Summarize and consolidate similar memories in a category using LLM. Requires 'category'. WORKFLOW: search -> not found? -> add. Found outdated? -> update (with memory_id from results). PROACTIVE: save user preferences, decisions, corrections, project conventions.