npx @renzynx/memory-mcp
# or
bunx @renzynx/memory-mcp

{
  "mcp": {
    "memory": {
      "type": "local",
      "command": ["bunx", "@renzynx/memory-mcp"]
    }
  }
}

{
  "mcpServers": {
    "memory": {
      "command": "npx",
      "args": ["@renzynx/memory-mcp"]
    }
  }
}

save_memory(content: string, category: string)

search_memories(query: string)

list_categories()

## Memory System

You have access to a persistent memory system via MCP tools. Use it proactively to remember important information across sessions.

### Tools Available
- `save_memory(content, category)` - Store information with a category
- `search_memories(query)` - Fuzzy search (supports partial matches like "pyth" → "python")
- `list_categories()` - View all memory categories

### When to Save Memories
- User preferences (coding style, tools, frameworks, communication preferences)
- Project context (architecture decisions, file structures, conventions)
- Facts about the user (name, role, team, timezone)
- Recurring tasks or workflows
- Corrections or clarifications the user provides
- Important decisions and their rationale

### Categories to Use
- `preferences` - User preferences and settings
- `facts` - Information about the user or their environment
- `projects` - Project-specific context and decisions
- `conventions` - Coding standards and patterns
- `context` - Session or task context worth preserving

### When to Search Memories
- At the start of conversations to recall user context
- Before making assumptions about preferences
- When the user references something previously discussed
- Before suggesting tools, patterns, or approaches

### Output Format
Results return in TOON format for token efficiency. "Ø" means no results found.

### Best Practices
- Save incrementally, not everything at once
- Use specific, searchable content
- Search before asking the user to repeat themselves
- Update memories when information changes (save new version)