-
Notifications
You must be signed in to change notification settings - Fork 7
Quick Start
Temp edited this page Dec 8, 2025
·
41 revisions
Get up and running with Memory Journal in 2 minutes!
PyPI (30 seconds):
pip install memory-journal-mcpDocker (1 minute):
docker pull writenotenow/memory-journal-mcp:latest
mkdir dataAdd to ~/.cursor/mcp.json:
PyPI:
{
"mcpServers": {
"memory-journal-mcp": {
"command": "memory-journal-mcp"
}
}
}Docker:
{
"mcpServers": {
"memory-journal-mcp": {
"command": "docker",
"args": [
"run", "--rm", "-i",
"-v", "./data:/app/data",
"writenotenow/memory-journal-mcp:latest",
"python", "src/server.py"
]
}
}
}The server should show green/connected with:
- 16 tools
- 14 prompts
- 13 resources (including GitHub Actions resources)
create_entry({
content: "Set up Memory Journal for project context management. Now AI can access complete project history across all threads.",
entry_type: "milestone",
tags: ["setup", "context-management", "ai-assistant"],
is_personal: false
})Output:
✅ Created journal entry #1
Type: milestone
Personal: False
Tags: setup, journal, productivity
search_entries({
query: "journal setup",
limit: 5
})Output:
Found 1 entries:
#1 (milestone) - 2025-10-04 16:30:22
Personal: False
Snippet: Just set up Memory **Journal**! Excited to track my development work...
create_entry({
content: "Decided to use Redis for session caching instead of in-memory store. Rationale: Better scalability for multi-instance deployment. Considered memcached but Redis provides persistence we need for disaster recovery.",
entry_type: "development_note",
tags: ["architecture", "caching", "decision"],
significance_type: "technical_decision"
})// Document the implementation
create_entry({
content: "Implemented Redis session caching with 1-hour TTL and automatic refresh on activity.",
entry_type: "technical_achievement",
tags: ["caching", "redis", "implementation"]
})
// Returns: Entry #3
// Link implementation to original decision (builds context chain)
link_entries({
from_entry_id: 3, // Implementation
to_entry_id: 2, // Original decision
relationship_type: "implements"
})
// Now AI can trace: Decision → Implementation → Results// Generate a relationship graph
visualize_relationships({
entry_id: 2,
depth: 2
})Output: Mermaid diagram showing connected entries!
Use the prompt palette (type / in Cursor):
/prepare-standup days_back:1
Output:
📋 Daily Standup - October 4, 2025
What I Did Yesterday:
- Fixed memory leak in caching layer
- Added connection pool monitoring
Blockers/Issues:
(None identified)
What's Next:
- Continue monitoring system performance
get_recent_entries({
limit: 5,
is_personal: false
})// Minimal entry
create_entry_minimal({
content: "Quick note about the API refactor"
})
// Full entry with all options
create_entry({
content: "Detailed technical description...",
entry_type: "development_note",
is_personal: false,
tags: ["api", "refactor", "breaking-change"],
significance_type: "major_milestone",
auto_context: true // Captures Git info
})// Full-text search
search_entries({ query: "API refactor", limit: 10 })
// Semantic search (requires ML dependencies)
semantic_search({ query: "performance optimization challenges" })
// Date range
search_by_date_range({
start_date: "2025-10-01",
end_date: "2025-10-31",
tags: ["bug-fix"]
})// Update an entry
update_entry({
entry_id: 1,
content: "Updated content...",
tags: ["new-tag"]
})
// Soft delete (recoverable)
delete_entry({
entry_id: 1,
permanent: false
})
// Get specific entry with relationships
get_entry_by_id({
entry_id: 1,
include_relationships: true
})// Get statistics
get_statistics({
group_by: "week"
})
// List all tags
list_tags()
// Export to Markdown
export_entries({
format: "markdown",
start_date: "2025-10-01",
tags: ["milestone"]
})Access prompts through your MCP client's prompt palette (type / in Cursor):
/prepare-standup days_back:1
/prepare-retro sprint_start:2025-10-01 sprint_end:2025-10-14
/weekly-digest week_offset:0
/analyze-period start_date:2025-10-01 end_date:2025-10-31 focus_area:performance
/goal-tracker project_name:memory-journal
/find-related entry_id:1
-
development_note- Technical decisions, architecture choices (MOST IMPORTANT for AI context) -
technical_achievement- Implementations, breakthroughs -
milestone- Project milestones, releases, version completions -
bug_fix- Bug resolutions with root cause analysis -
enhancement- Improvements, optimizations, refactorings -
technical_note- API documentation, integration notes -
personal_reflection- Learning insights, retrospectives (optional)
Be consistent:
- Use lowercase
- Use hyphens for multi-word tags
- Create a core set of tags you use regularly
Good tags:
-
performance,bug-fix,api-design -
learning,documentation,testing - Project-specific:
memory-journal,postgres-mcp
-
references- General connection between entries -
implements- Implementation of a spec/plan -
clarifies- Explanation or elaboration -
evolves_from- Iteration or improvement -
response_to- Reply or follow-up
Set auto_context: true (default) to automatically capture Git/GitHub state with every entry:
- Repository context - Repo name, path, working directory
-
Branch information - Current branch (e.g.,
feature/redis-caching) - Commit details - Latest commit hash and message
-
GitHub integration - Open issues, PR status (if
ghCLI installed)
Why this matters: AI can understand WHEN and WHERE work happened, making context reconstruction much more accurate across fragmented threads.
Learn More:
- Tools Reference - Complete guide to all 16 tools
- Tool Filtering - Reduce token usage by up to 69%
- Prompts Guide - All 14 workflow prompts
- Visualization - Relationship graphs
- Examples - Real-world usage patterns
Advanced Features:
- Relationships - Building knowledge graphs
- Semantic Search - ML-powered search
- Analytics - Statistics and insights
Questions? Check the Examples page or open an issue on GitHub.