Store a Memory

Use the memory_add MCP tool to store information for future recall.

Usage

When the user says "remember this" or you discover something worth persisting:

1. •Determine the content to store
2. •Choose the appropriate scope:
   • •personal (default) — only you see it
   • •shared — visible to the whole team
3. •Pick a category: preferences, conventions, architecture, decisions, workflow, or general
4. •Extract the project context from git remote for scoped recall

Project Context

Always include the project reference when in a git repository:

1. •Run: git remote get-url origin
2. •Extract org/repo from the URL:
   • •SSH git@github.com:org/repo.git → org/repo
   • •HTTPS https://github.com/org/repo.git → org/repo
3. •Pass as source_ref: "project:org/repo"

MCP Tool Call

{
  "tool": "memory_add",
  "arguments": {
    "content": "The description of what to remember",
    "scope": "personal",
    "category": "decisions",
    "tags": ["auth", "security"],
    "source_ref": "project:org/repo"
  }
}

What to Store

• •User preferences and style choices
• •Project conventions and naming patterns
• •Architecture and infrastructure decisions
• •Debugging insights and solutions to recurring problems
• •Workflow patterns and deployment processes

What NOT to Store

• •Session-specific context (current task, temporary state)
• •Information already in the codebase
• •Build output or error messages being debugged right now
• •Speculative conclusions from a single observation