Memory for Your AI Assistants _

> Persistent Agent memory that just works!
> Your AI remembers conversations, learns patterns, grows smarter
> Simple config. Sensible defaults. Local-first. Privacy by default.

$ pipx install memorygraphMCP Read the Docs

Cloud Backend coming mid-December — memory across all your environments

Loading...
// automatic_memory

Memory is stored and recalled automatically as you work

claude-code ~ auth-service
you> Add rate limiting to the /api/users endpoint
claude> recall_memories query="rate limiting"
→ Found: Rate limit pattern (Redis) - used in /api/auth
claude> I'll use the same Redis-based approach from /api/auth...
[implements rate limiting]
claude> store_memory type="pattern" title="Rate limit /api/users"
✓ Pattern stored automatically on commit
// explicit_memory

Or explicitly store and recall important solutions

claude-code ~ session
you> Remember the Redis timeout fix we just implemented
claude> store_memory type="solution" title="Redis timeout fix"
✓ Memory stored: mem_a1b2c3d4
you> Have we solved timeout issues before?
claude> recall_memories query="timeout solutions"
✓ Found 3 memories:
→ Redis timeout fix (solution) - 0.92 relevance
→ Connection pool tuning (pattern) - 0.87 relevance

See it in action

MemoryGraph in action - Claude Code recalling priority projects and their status
Real example: Claude recalls project status and priorities across sessions

// QUICKSTART

> Get started in under a minute

Default (SQLite) RECOMMENDED

Simple setup with local storage. No external dependencies.

# Install
pipx install memorygraphMCP

# Add to Claude Code
claude mcp add memorygraph memorygraph

# Configure memory directives (important!)
# Add to ~/.claude/CLAUDE.md

Configure memory directives to enable automatic storage.

With FalkorDBLite OPTIONAL

Embedded graph database with native Cypher queries. No server needed.

# Install with FalkorDBLite
pipx install "memorygraphMCP[falkordblite]"

# Configure backend
export MEMORYGRAPH_BACKEND=falkordblite

# Add to Claude Code
claude mcp add memorygraph memorygraph
With FalkorDB Server OPTIONAL

High-performance graph database for production deployments.

# Run FalkorDB via Docker
docker run -d -p 6379:6379 falkordb/falkordb

# Install with FalkorDB client
pipx install "memorygraphMCP[falkordb]"

# Configure backend
export MEMORYGRAPH_BACKEND=falkordb
export MEMORYGRAPH_FALKORDB_URL=redis://localhost:6379

# Add to Claude Code
claude mcp add memorygraph memorygraph

// CORE_FUNCTIONS

> MCP tools that give your AI persistent memory

store_memory() 
store_memory(
  type="solution",
  title="Redis timeout fix",
  tags=["redis", "timeout"]
)

Capture solutions, patterns, decisions. Your AI builds a knowledge base from every interaction.

recall_memories() 
recall_memories(
  query="timeout solutions",
  memory_types=["solution"]
)

Fuzzy search with semantic matching. Find relevant context even with imprecise queries.

create_relationship() 
create_relationship(
  from="problem_123",
  to="solution_456",
  type="SOLVES"
)

Link problems to solutions, causes to effects. Build a knowledge graph, not just a list.

get_related_memories() 
get_related_memories(
  memory_id="error_789",
  relationship_types=["CAUSES"]
)

Traverse the graph. Find what caused this, what solved that, what works with what.

$ Why Knowledge Graphs?

> Traditional vector stores lose relationships between memories

> FalkorDB-powered graphs preserve causality and context

> Ask "What solves X?" not just "What's similar to X?"

// DATA_PORTABILITY

> Your data. Your choice. No lock-in.

Migrate between any backend with full verification and rollback. Start local, scale to cloud, or move between providers—your memories follow you.

🔄

Backend Migration

Move memories between SQLite, Neo4j, Memgraph, FalkorDB, and more with a single command.

✓

Verified Transfers

Automatic validation ensures every memory and relationship transfers correctly.

↩

Safe Rollback

If anything fails, automatic rollback protects your data. Always test with --dry-run first.

📦

Export Anywhere

Export to JSON anytime. Your data is never trapped in a proprietary format.

Supported Backends:
SQLiteNeo4jMemgraphFalkorDBFalkorDBLite
// quick_start
# Validate migration
$ memorygraph migrate --to falkordb --dry-run
# Execute migration
$ memorygraph migrate --to falkordb --verbose
# Verify new backend
$ memorygraph health
✓ Migration completed successfully!
Migrated: 150 memories
Migrated: 342 relationships
Duration: 3.2 seconds
Migration Guide →

// CLOUD_SYNC

Share memories across environments, devices, and teams with our managed cloud backend.

// PRICING_PLANS

> Start free. Scale as you grow. No hidden fees.

PRO RECOMMENDED
$5 /month
  • [✓] 100,000 memories
  • [✓] Advanced search
  • [✓] Graph visualization
  • [✓] API access
  • [✓] Priority support
$ ./init --pro
ULTRA
$50 /month
  • [✓] 500,000 memories
  • [✓] Advanced search
  • [✓] Graph visualization
  • [✓] API access
  • [✓] Priority support
$ ./init --ultra
TEAM
$100 /month
  • [✓] Unlimited memories
  • [✓] Up to 10 users
  • [✓] Team workspaces
  • [✓] SSO & SAML
  • [✓] Dedicated support
$ ./init --team

> Self-hosting available. Open source MCP server is free forever.

// FAQ

> man memorygraph