---
id: d0d1a325-a308-474a-baf7-6939a76a136b
type: general
title: "MemoryGraph MCP Installation and Protocol"
tags: [pai, claude-code, memorygraph, mcp, setup, configuration]
importance: 0.8
confidence: 0.8
created: "2025-12-06T16:25:59.811824+00:00"
updated: "2026-03-01T22:16:57.236741+00:00"
relations:
  - target: 991e1162-d73c-4b6c-a27f-77aa0f9b9a68
    type: RELATED_TO
    direction: incoming
    strength: 0.5
    context: "Both part of PAI infrastructure improvements - NoteDiscovery skill migration and MemoryGraph setup happened in same session as part of context management strategy"
  - target: 5fb6b3c0-cc6a-4baa-8552-8d2731379b0b
    type: RELATED_TO
    direction: incoming
    strength: 0.79
    edge_id: ac0d00ea-f279-49b5-b186-b8c3cc4deffe
  - target: e301095c-7d4c-45d8-8352-9491e4ad6603
    type: RELATED_TO
    direction: incoming
    strength: 0.75
    edge_id: 36a8e59c-08c6-4efe-b154-6277ea5cf1e7
---

Installed MemoryGraph MCP for persistent graph-based memory across sessions. Used SQLite backend (zero config, stores at ~/.memorygraph/memory.db). Installation: pipx install memorygraphMCP, then 'claude mcp add --scope user memorygraph -- memorygraph --profile extended'. Extended profile provides 11 tools including get_memory_statistics. Added Memory Protocol section to ~/.claude/CLAUDE.md with: required recall before complex work, automatic storage triggers (bug fix, git commit, architecture decision, pattern, config, troubleshooting), importance scale (0.8-1.0 critical, 0.5-0.7 standard, 0.3-0.4 minor), tag requirements (project, technology, category), and relationship types (SOLVES, CAUSES, BUILDS_ON, etc.).