This document provides a complete inventory of all implemented MCP tools in MemoryGraph, organized by profile tier.
| Profile | Tool Count | Description | Use Case |
|---|---|---|---|
| core | 9 | Essential memory operations | Default for 95% of users, zero-config |
| extended | 11 | Core + advanced analytics | Power users needing stats & complex queries |
| Feature | Core (Default) | Extended |
|---|---|---|
| Memory CRUD | ✅ 5 tools | ✅ 5 tools |
| Relationships | ✅ 2 tools | ✅ 2 tools |
| Discovery | ✅ 2 tools | ✅ 2 tools |
| Database Stats | ❌ | ✅ 1 tool |
| Complex Queries | ❌ | ✅ 1 tool |
| Setup | Zero-config | Zero-config |
| Backend | SQLite | SQLite |
Zero-config default. Provides all essential memory operations for daily use.
-
store_memory - Store a new memory with context and metadata
- Capture solutions, problems, errors, patterns, decisions
- Add tags, importance scores, project context
- Returns memory_id for future reference
-
get_memory - Retrieve a specific memory by ID with full details
- Get complete memory information
- Optionally include relationships
- Use after finding a memory in search
-
search_memories - Advanced search with fine-grained control
- Full-text search across title, content, summary
- Filter by memory types, tags, importance
- Strict or fuzzy matching modes
- Boolean queries (any/all terms)
-
update_memory - Update an existing memory
- Modify title, content, summary, tags
- Update importance scores
- Requires memory_id
-
delete_memory - Delete a memory and all its relationships
- Permanent removal
- Cascades to delete relationships
- Requires memory_id
-
create_relationship - Create a relationship between two memories
- 35+ relationship types (SOLVES, CAUSES, REQUIRES, etc.)
- Optional strength and confidence scores
- Natural language context auto-extracted
- Enables "What solved X?" queries
-
get_related_memories - Find memories related to a specific memory
- Traverse relationships by type
- Control depth (1-5 levels)
- Explore knowledge graph connections
- Filter by relationship types
-
recall_memories - Primary search with fuzzy matching (RECOMMENDED)
- Optimized for natural language queries
- Automatic fuzzy matching (handles plurals, tenses)
- Always includes relationship context
- Best starting point for recall queries
- Match quality hints and suggestions
-
get_recent_activity - Session briefing and progress tracking
- Summary of recent memories (last N days)
- Breakdown by type (solutions, problems, etc.)
- Unresolved problems highlighted
- Project-scoped activity
- "Catch me up" functionality
Core + advanced analytics. For power users who need database statistics and complex relationship queries.
- All tools from Core profile above
-
get_memory_statistics - Get comprehensive database statistics
- Total memories and relationships
- Breakdown by memory type
- Average importance and confidence scores
- Graph metrics overview
-
search_relationships_by_context - Complex relationship queries
- Search by structured context fields (scope, conditions, evidence)
- Filter by implementation scope (partial/full/conditional)
- Find relationships with specific evidence types
- Query by components and temporal information
- Advanced relationship analytics
| Category | Tools | Count | Profile |
|---|---|---|---|
| Memory CRUD | store_memory, get_memory, search_memories, update_memory, delete_memory | 5 | core |
| Relationships | create_relationship, get_related_memories | 2 | core |
| Discovery | recall_memories, get_recent_activity | 2 | core |
| Statistics | get_memory_statistics | 1 | extended |
| Advanced Queries | search_relationships_by_context | 1 | extended |
| Use Case | Recommended Tools | Profile |
|---|---|---|
| Store learnings | store_memory, create_relationship | core |
| Find past solutions | recall_memories, get_related_memories | core |
| Session briefing | get_recent_activity | core |
| Advanced search | search_memories, search_relationships_by_context | core, extended |
| Database insights | get_memory_statistics | extended |
| Complex analytics | search_relationships_by_context, get_memory_statistics | extended |
- ✅ You're getting started
- ✅ You need basic memory storage and retrieval
- ✅ You want zero configuration
- ✅ You're a typical user (95% of use cases)
- ✅ You want the simplest setup
- ✅ You need database statistics
- ✅ You want advanced relationship queries
- ✅ You're analyzing patterns across large memory sets
- ✅ You need scope/evidence-based relationship filtering
- ✅ You're a power user who wants all capabilities
# Core (default)
export MEMORY_TOOL_PROFILE=core
# Extended
export MEMORY_TOOL_PROFILE=extended# Core (default)
memorygraph
# Extended
memorygraph --profile extended{
"mcpServers": {
"memorygraph": {
"command": "memorygraph",
"args": ["--profile", "extended"],
"env": {
"MEMORY_BACKEND": "sqlite"
}
}
}
}| Backend | Compatible Tools | Notes |
|---|---|---|
| SQLite | All 11 tools | Default backend, zero configuration |
| Neo4j | All 11 tools | Requires setup, optimal for large graphs |
| Memgraph | All 11 tools | Requires setup, fastest analytics |
All profiles work with all backends. The profile controls which tools are exposed, not which backend is used.
Previous versions used three profiles (lite/standard/full). The system now uses two profiles (core/extended).
Automatic Migration:
lite→core(9 tools)standard→extended(11 tools)full→extended(11 tools)
Legacy profile names are still supported but will be automatically mapped to the new profiles.
What Changed:
- Removed: 33 unimplemented "vaporware" tools that were documented but not built
- Kept: All 11 actually implemented and tested tools
- Simplified: From 3 tiers to 2 tiers (Core/Extended)
- Focused: Core mode is now the default, works for 95% of users
Current Status (v0.7.1+)
- ✅ All 11 tools fully implemented and tested
- ✅ 409 tests with 93% coverage
- ✅ Profile filtering system working
- ✅ Core/Extended profiles defined
- ✅ Legacy profile compatibility (lite/standard/full → core/extended)
Tools Removed from Documentation
- 33 unimplemented tools removed (intelligence, integration, proactive categories)
- Tools were either redundant (Claude already does it) or YAGNI (not needed)
- Focus shifted to stable, tested, production-ready tools
Primary tool: recall_memories
- Best for: "What did we learn about X?"
- Features: Fuzzy matching, relationship context, match quality hints
- Use when: You want natural language search with smart defaults
Secondary tool: search_memories
- Best for: Exact matching, multi-term boolean queries
- Features: Full control, strict/normal/fuzzy modes, advanced filters
- Use when: You need precise control or recall_memories didn't find what you need
Primary tool: create_relationship
- Creates links between memories (solution SOLVES problem, etc.)
- 35+ relationship types across 7 categories
Secondary tool: get_related_memories
- Explores connections by traversing relationships
- Filter by type, control depth
Primary tool: get_recent_activity
- "Catch me up" functionality
- Shows recent work, unresolved problems
- Project-scoped summaries
Primary tool: get_memory_statistics
- Database overview and metrics
- Breakdown by type, importance, etc.
Secondary tool: search_relationships_by_context
- Complex relationship queries
- Scope/evidence/condition filtering
Last Updated: December 1, 2025 Total Implemented Tools: 11 Profiles: 2 (core/extended) Default Profile: core Backends: 3 (SQLite/Neo4j/Memgraph)