MemoryGraph
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@MemoryGraphRemember this for later: Use pytest for Python testing"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Using with Coding Agents
Coding agents already execute shell commands, so they can use MemoryGraph directly. Two steps: install globally, then add instructions.
Install
cd memory-graph/ts && bun install && bun link
# or: bun build src/cli.ts --compile --outfile ~/.local/bin/memorygraph
memorygraph stats # verifymemorygraph is now available from any directory. Data persists in ~/.memorygraph/.
Add Agent Instructions
Paste this into your agent's instruction file (~/.claude/CLAUDE.md, .cursorrules, .windsurfrules, or AGENTS.md):
## Memory
`memorygraph` CLI is installed. Use it for persistent memory across sessions.
Before work: `memorygraph recall --query "<task>" --limit 10` and `memorygraph briefing`
On decisions/fixes: `memorygraph store --type solution --title "<title>" --content "<what>" --tags "<component>,fix"`
On errors: `memorygraph store --type error --title "<error>" --content "<details>" --tags "<component>,error"`
Link: `memorygraph link <from-id> <to-id> SOLVES --strength 0.8`
Session end: `memorygraph store --type conversation --title "Session: <topic>" --content "<summary>" --tags "<tags>"`
Types: solution | problem | code_pattern | fix | error | workflow | command | technology
Tags: lowercase, hyphenated, include component (auth, database, cli), 2-5 per memory
Do NOT wait to be asked. Store automatically on triggers.Example Session
# Start: load context
memorygraph recall --query "authentication redis" --limit 10
memorygraph briefing
# Fix a bug: store problem + solution, link them
memorygraph store --type problem --title "Auth token expiry too short" --content "Tokens expiring after 1h" --tags "auth,bug"
# → abc-123
memorygraph store --type solution --title "Extend token expiry to 24h" --content "Changed JWT expiry, added refresh rotation" --tags "auth,fix" --importance 0.8
# → def-456
memorygraph link def-456 abc-123 SOLVES --strength 0.9
# End: store summary
memorygraph store --type conversation --title "Session: auth token fix" --content "Fixed token expiry, added refresh rotation" --tags "auth,session-summary"Multi-Project Setup
All projects share ~/.memorygraph/falkordblite.db by default. To isolate per project:
export MEMORY_FALKORDBLITE_PATH=~/.memorygraph/my-project.falkor
# or tag memories with project name and filter:
memorygraph search --query "auth" --tags my-projectTroubleshooting
Agent not using commands: Use "REQUIRED"/"MUST" in instructions, include exact commands
Command not found:
bun linkfromts/, or ensure~/.local/binis on PATHMemories not persisting:
memorygraph configto check path,memorygraph healthto verify
Related MCP server: budget-aware-mcp
Why MemoryGraph?
Graph Relationships Make the Difference
Flat storage (CLAUDE.md, vector stores) keeps memories as isolated entries. Graph storage connects them:
[timeout_fix] --CAUSES--> [memory_leak] --SOLVED_BY--> [connection_pooling]
| |
+------------------SUPERSEDED_BY------------------------+Query: "What happened with retry logic?" returns the full causal chain, not just individual memories.
When to Use What
Use CLAUDE.md / AGENTS.md For | Use MemoryGraph For |
"Always use 2-space indentation" | "Last time we used 4-space, it broke the linter" |
"Run tests before committing" | "The auth tests failed because of X, fixed by Y" |
Static rules, prime directives | Dynamic learnings with relationships |
CLI Commands
Memory Operations
Command | Purpose | Example |
| Store a new memory |
|
| Get a memory by ID |
|
| Update an existing memory |
|
| Delete a memory |
|
| Search with filters |
|
| Natural language recall |
|
| Get related memories |
|
| Create a relationship |
|
Context Search
Command | Purpose |
| Search relationships by type, strength, or context text |
| Search within a memory's related items |
Intelligence
Command | Purpose |
| Extract entities (files, functions, classes, technologies) from a memory |
| Find similar problems and suggest patterns |
| Get intelligent context retrieval with entity and keyword matching |
Analytics
Command | Purpose |
| Database statistics (memory count, types, relationships) |
| Recent activity summary with unresolved problems |
| Graph visualization data (nodes and edges) |
| Analyze solution similarity for a given memory |
| Recommend learning paths for a topic |
| Identify knowledge gaps (unsolved problems, missing connections) |
Proactive
Command | Purpose |
| Generate a session briefing with recent activity and open issues |
| Predict what might be needed based on current context |
| Warn about potential issues (deprecated approaches, known errors) |
| Record an outcome for a memory (success/failure tracking) |
Integration
Command | Purpose |
| Capture task context from current environment |
| Analyze the current project codebase |
| Track or suggest workflow improvements |
Temporal
Command | Purpose |
| Query relationships as they existed at a specific time |
| Get full relationship history for a memory |
| Show relationship changes since a timestamp |
Data Management
Command | Purpose |
| Export to JSON or Markdown |
| Import from JSON |
| Migrate between backends |
| Run a health check |
| Show current configuration |
Backends
Backend | Type | Config | Native Graph | Zero-Config | Best For |
falkordblite (default) | Embedded | File path | Cypher | Yes | Default, graph queries without server |
sqlite | Embedded | File path | Simulated | Yes | Zero-dependency fallback |
falkordb | Client-server | Host:port | Cypher | No | High-performance production |
memgraph | Client-server | Bolt URI | Cypher | No | Real-time analytics |
cloud | Cloud | API Key | Cypher | No | Multi-device sync, team sharing |
Backend Configuration
# Use FalkorDBLite (default, zero-config)
bun run src/cli.ts stats
# Use SQLite
MEMORY_BACKEND=sqlite bun run src/cli.ts stats
# Use FalkorDB (client-server)
MEMORY_BACKEND=falkordb MEMORY_FALKORDB_HOST=localhost MEMORY_FALKORDB_PORT=6379 bun run src/cli.ts stats
# Use Memgraph
MEMORY_BACKEND=memgraph MEMORY_MEMGRAPH_URI=bolt://localhost:7687 bun run src/cli.ts stats
# Use Cloud
MEMORY_BACKEND=cloud MEMORYGRAPH_API_KEY=mg_your_key bun run src/cli.ts statsEnvironment Variables
Variable | Description | Default |
| Backend type |
|
| FalkorDBLite database path |
|
| SQLite database path |
|
| FalkorDB server host |
|
| FalkorDB server port |
|
| Memgraph Bolt URI |
|
| Cloud API key | - |
| Cloud API URL |
|
| Tool profile (core or extended) |
|
| Log level |
|
Memory Types
Type | Use Case |
| Tasks and action items |
| Recurring code patterns or conventions |
| Problems or challenges encountered |
| Solutions, decisions, or approaches chosen |
| Project context, environment, setup info |
| Technology choices and evaluations |
| Errors discovered |
| Fixes applied to errors |
| Useful commands or CLI snippets |
| Context about specific files |
| Workflow or process descriptions |
| General purpose memories |
| Conversation summaries |
Relationship Types
Type | Meaning |
| General connection |
| New memory extends an older one |
| New memory supersedes or invalidates an older one |
| New memory provides evidence for an older one |
| A solution solves a problem |
| One memory causes another |
| One memory depends on another |
| An improvement over an existing approach |
| Replaces an older approach |
| Workflow dependency |
Memory Best Practices
Session Workflow
# Start of session: recall recent context
bun run src/cli.ts recall --query "recent work" --limit 10
# During work: store decisions and patterns
bun run src/cli.ts store \
--type solution \
--title "Use JWT for auth" \
--content "JWT tokens with 24h expiry, refresh token rotation" \
--tags "auth,security,api" \
--importance 0.8
# Link it to a prior decision
bun run src/cli.ts link <new-id> <prior-id> BUILDS_ON --strength 0.9
# End of session: store summary
bun run src/cli.ts store \
--type conversation \
--title "Session: auth refactor" \
--content "Refactored auth middleware, added JWT, fixed token refresh bug" \
--tags "auth,session-summary"
# Export backup
bun run src/cli.ts export --format json --output session-backup.jsonAdd to CLAUDE.md or AGENTS.md
## Memory Protocol
### REQUIRED: Before Starting Work
You MUST use `recall` before any task. Query by project, tech, or task type.
### REQUIRED: Automatic Storage Triggers
Store memories on ANY of:
- Git commit: what was fixed/added
- Bug fix: problem + solution
- Architecture decision: choice + rationale
- Pattern discovered: reusable approach
### Memory Fields
- Type: solution | problem | code_pattern | fix | error | workflow
- Title: Specific, searchable
- Content: Accomplishment, decisions, patterns
- Tags: project, tech, category (required)
- Importance: 0.8+ critical, 0.5-0.7 standard, 0.3-0.4 minor
- Relationships: Link related memories when they existArchitecture
Project Structure
memory-graph/
├── ts/
│ ├── src/
│ │ ├── cli.ts # CLI entry point (35+ commands)
│ │ ├── index.ts # Library exports
│ │ ├── config.ts # Configuration management
│ │ ├── database.ts # Database interface
│ │ ├── models.ts # Data models and schemas
│ │ ├── backends/ # Backend implementations
│ │ │ ├── falkordb-shared.ts # Shared FalkorDB base class
│ │ │ ├── falkordblite.ts # Embedded FalkorDBLite
│ │ │ ├── falkordb.ts # Client-server FalkorDB
│ │ │ ├── bolt-shared.ts # Shared Bolt protocol base
│ │ │ ├── memgraph.ts # Memgraph (Bolt protocol)
│ │ │ ├── sqlite.ts # SQLite fallback
│ │ │ ├── cloud.ts # Cloud REST API
│ │ │ └── factory.ts # Backend factory
│ │ ├── tools/ # CLI tool handlers
│ │ ├── intelligence/ # Entity extraction, pattern recognition, context retrieval
│ │ ├── analytics/ # Graph visualization, similarity, learning paths
│ │ ├── proactive/ # Session briefing, predictions, outcome learning
│ │ ├── integration/ # Context capture, project analysis, workflow tracking
│ │ ├── migration/ # Backend-to-backend migration
│ │ ├── sdk/ # Cloud API client SDK
│ │ └── utils/ # Export/import, validation, helpers
│ ├── tests/ # 97 tests
│ └── package.json
├── docs/ # Documentation
└── CLAUDE.md # Agent instructionsBuilding
cd ts
bun install
bun test # Run tests
npx tsc --noEmit # Type check
bun build src/cli.ts --compile --outfile memorygraph # Compile binaryImport / Migration
# Import from JSON export
bun run src/cli.ts import --input backup.json --skip-duplicates
# Migrate between backends
bun run src/cli.ts migrate --to sqlite --to-path ./local.db
bun run src/cli.ts migrate --to falkordblite --to-path ./graph.falkor --no-verify
bun run src/cli.ts migrate --to memgraph --to-uri bolt://localhost:7687SDK
The TypeScript SDK provides a client for the MemoryGraph Cloud API:
import { MemoryGraphClient } from "memorygraph/sdk";
const client = new MemoryGraphClient({ apiKey: "mg_..." });
const memory = await client.createMemory({
type: "solution",
title: "Fixed timeout issue",
content: "Used exponential backoff with retries",
tags: ["redis", "timeout"],
});License
MIT License - see LICENSE.
Start simple. Upgrade when needed. Never lose context again.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/gregorydickson/memory-graph'
If you have feedback or need assistance with the MCP directory API, please join our Discord server