Memory Journal MCP Server
🎯 AI Context + Project Intelligence: Bridge disconnected AI sessions with persistent project memory and automatic session handoff — with full GitHub workflow integration.
GitHub • Wiki • Changelog • Release Article
🚀 Quick Deploy:
- npm Package -
npm install -g memory-journal-mcp - Docker Hub - Alpine-based with full semantic search
🧠 Stop Experiencing AI Amnesia
When managing large projects with AI assistance, you face a critical challenge:
- Thread Amnesia - Each new AI conversation starts from zero, unaware of previous work.
- Lost Context - Decisions, implementations, and learnings scattered across disconnected threads.
- Repeated Work - AI suggests solutions you've already tried or abandoned.
- Context Overload - Manually copying project history into every new conversation.
Memory Journal solves this by acting as your project's long-term memory, bridging the gap between fragmented AI sessions.
Experience true context-aware development:
- "Why did we choose SQLite over Postgres for this service last month?" (Semantic search)
- "Run the
/issue-triageworkflow on the top priority ticket in the Kanban board." (GitHub operations) - "Who has been touching the auth module recently, and what's our team collaboration density?" (Team analytics)
- "I'm stuck on this database error. Raise a 'blocker' flag for @sarah so her agent sees it next session." (Hush Protocol)
- "Close issue #42 and log an entry explaining our architectural fix for the parsing bug." (Context lifecycles)
- "Draw a visual graph showing how my last 10 architectural decisions relate to each other." (Knowledge graph)
See complete examples & prompts →
🎯 What Sets Us Apart
70 MCP Tools · 17 Workflow Prompts · 36 Resources · 10 Tool Groups · Code Mode · GitHub Commander (Issue Triage, PR Review, Milestone Sprints, Security/Quality/Perf Audits) · GitHub Integration (Issues, PRs, Actions, Kanban, Milestones, Insights) · Team Collaboration (Shared DB, Vector Search, Cross-Project Insights, Hush Protocol Flags)
| Feature | Description |
|---|---|
| Session Intelligence | Agents auto-query project history, create entries at checkpoints, and hand off context between sessions via /session-summary and team-session-summary |
| GitHub Integration | 18 tools for Issues, PRs, Actions, Kanban, Milestones (%), Copilot Reviews, and 14-day Insights |
| Dynamic Project Routing | Seamlessly switch contexts and access CI/Issue tracking across multiple repositories using a single server instance via PROJECT_REGISTRY |
| Knowledge Graphs | 8 relationship types linking specs → implementations → tests → PRs with Mermaid visualization |
| Hybrid Search | Reciprocal Rank Fusion combining FTS5 keywords, semantic vector similarity, auto-heuristics, and date-range filters |
| Code Mode | Execute multi-step operations in a trusted-admin execution environment — up to 90% token savings via mj.* API |
| Configurable Briefing | 15 env vars / CLI flags control memory://briefing content — entries, team, GitHub detail, skills awareness, chronological grounding |
| Reports & Analytics | Standups, retrospectives, PR summaries, digests, period analyses, and milestone tracking |
| Hush Protocol (Flags) | Replace Slack/Teams noise with structured, actionable, and searchable AI flags (blockers, reviews) that automatically surface in session briefings |
| Team Collaboration | 25 tools with full parity — CRUD, vector search, relationship graphs, cross-project insights, author attribution, Hush Protocol flags |
| Data Interoperability | Bidirectional Markdown roundtripping, unified IO namespace, and schema-safe JSON exports with hard bounds-checked path traversal defenses |
| Backup & Restore | One-command backup/restore with automated scheduling, retention policies, and safety-net auto-backups |
| Security & Transport | OAuth 2.1 (RFC 9728/8414, JWT/JWKS, scopes), Streamable HTTP + SSE, rate limiting, CORS, SQL injection prevention, non-root Docker |
| Structured Error Handling | Every tool returns {success, error, code, category, suggestion, recoverable} — agents get classification, remediation hints, and recoverability signals |
| Agent Collaboration | IDE agents and Copilot share context; review findings become searchable knowledge; agents suggest reusable rules and skills (setup) |
| Native Agent Skills | Bundled foundational coding paradigms (autonomous-dev, python, docker, tailwind-css, golang, playwright-standard, etc.) establishing permanent AI behavior and architecture rules |
| GitHub Commander | Pipeline skills for issue triage, PR reviews, sprint milestones, and security/quality/performance audits with journal trails (docs) |
flowchart TB
subgraph Session["🤖 AI Session Start"]
Briefing["📋 Read Briefing<br/>(memory://briefing)"]
end
subgraph Core["📝 Journal Operations"]
Create["Create Entry"]
Retrieve["Retrieve & Search"]
Link["Link Entries"]
end
subgraph Search["🔍 Hybrid Search"]
FTS["Keyword (FTS5)"]
Semantic["Semantic (Vector)"]
DateRange["Date Range"]
RRF["Reciprocal Rank Fusion"]
end
subgraph GitHub["🐙 GitHub Integration"]
Issues["Issues & Milestones"]
PRs["Pull Requests"]
Actions["GitHub Actions"]
Kanban["Kanban Boards"]
Insights["Repository Insights"]
end
subgraph Outputs["📊 Outputs"]
Reports["Standups & Retrospectives"]
Graphs["Knowledge Graphs"]
Timeline["Project Timelines"]
end
Session --> Core
Core --> Search
Core <--> GitHub
Search --> Outputs
GitHub --> Outputs
Recommended AI Agent Instructions/Rule
Suggested Rule (Add to AGENTS.md, GEMINI.md, system prompts, etc.)
🛑 MANDATORY SESSION START ROUTINE
Execute BEFORE fulfilling any user request in a new session:
- TARGET: Infer
repo_namefrom the active workspace context or user prompt. If the task is not associated with a specific project, fallback to using the generic resource without a repo name (which defaults to the first registered workspace). - FETCH: Use the MCP
read_resourcetool (Server:memory-journal-mcp) to readmemory://briefing/{repo_name}(ormemory://briefingif falling back).- RESTRICTION: Do NOT use
execute_codefor this step.
- RESTRICTION: Do NOT use
- ACKNOWLEDGE FLAGS: If the briefing JSON contains
activeFlags(count > 0), you MUST print an alert ABOVE the table:⚠️ **{count} active flag(s)** — review before proceeding.followed by each flag (🚩 {flag_type} → @{target_user}: {preview}). - RENDER TABLE: Parse the remaining JSON into a dense 2-column Markdown Table (Field, Value).
- RESTRICTION: NO bulleted lists inside the table. Do NOT truncate summaries or issues.
- FORMATTING: Group related properties (use
<br>for line breaks). - REQUIRED GROUPS: GitHub (Repo, Branch, CI, PRs, Insights), Issues, Entry Counts, Latest Entries/Summaries, Analytics, Milestones, Workspaces.
- STOP & WAIT: Do NOT autonomously resume past tasks or start work on new issues mentioned in the session summary. The briefing is strictly for context.
Tool Filtering
[!IMPORTANT] All shortcuts and tool groups include Code Mode (
mj_execute_code) by default for token-efficient operations. To exclude it, add-codemodeto your filter:--tool-filter starter,-codemode
Control which tools are exposed via MEMORY_JOURNAL_MCP_TOOL_FILTER (or CLI: --tool-filter):
| Filter | Tools | Use Case |
|---|---|---|
full |
70 | All tools (default) |
starter |
~11 | Core + search + codemode |
essential |
~7 | Minimal footprint |
readonly |
17 | Disable all mutations |
-github |
52 | Exclude a group |
-github,-analytics |
50 | Exclude multiple groups |
Filter Syntax: shortcut or group or tool_name (whitelist mode) · -group (disable group) · -tool (disable tool) · +tool (re-enable after group disable)
Custom Selection: List individual tool names to create your own whitelist: --tool-filter "create_entry,search_entries,semantic_search"
Groups: core, search, analytics, relationships, io, admin, github, backup, team, codemode
Complete tool filtering guide →