Memory Journal MCP

Memory Journal MCP Server

[📚 Full Documentation (Wiki)](https://github.com/neverinfamous/memory-journal-mcp/wiki) • [Changelog](CHANGELOG.md) • [Security](SECURITY.md) • [Release Article](https://adamic.tech/articles/memory-journal-mcp-server)

[!TIP]

Value Proposition

Bridge disconnected AI sessions seamlessly. Enable persistent project memory instantly. Automate handoffs with robust GitHub integration. Eliminate AI amnesia today.

🚀 Quick Deploy:

• [npm Package](https://www.npmjs.com/package/memory-journal-mcp) - npm install -g memory-journal-mcp (or pnpm add -g memory-journal-mcp)
• [Docker Hub](https://hub.docker.com/r/writenotenow/memory-journal-mcp) - Alpine-based with full semantic search

🧠 Eliminate AI Amnesia

Large projects face a critical challenge. You lose context between sessions.

• Stop Thread Amnesia - AI conversations start fresh. They ignore previous work.
• Retain Deep Context - Decisions and code scatter across threads; Memory Journal preserves them automatically.
• End Repeated Work - AI repeats failed solutions; persistent history tracks every prior attempt.
• Prevent Context Overload - Manual history copying wastes tokens; dynamic briefings deliver targeted context automatically.

Memory Journal builds your project's long-term memory. It acts as a Project Context Graph for AI-assisted engineering. It bridges human workflows (Issues, PRs, Kanban, Milestones) with agent execution (Git, tests, decisions).

---

Experience true context-aware development:

• _"Why did we choose SQLite over Postgres for this service last month?"_ (Semantic search)
• _"Run the /issue-commander (triage workflow) 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)
• _"Commit the changes and automatically generate a structured journal entry using the \--journal\ wrapper flag."_ (Automated lifecycles)
• _"Draw a visual graph showing how my last 10 architectural decisions relate to each other."_ (Knowledge graph)

Comprehensive access to internal state via resources (`memory://briefing`, `memory://workflows`, `memory://rules`, `memory://health`, `memory://help`, `memory://staleness`, GitHub status/milestones, team stats, and metrics/latency). Dynamic repo variants also support cross-repo targeting (like `memory://briefing/{+repo}` or `memory://kanban/{+repo}/{project_number}`). [Resources documentation →](https://github.com/neverinfamous/memory-journal-mcp/wiki/Resources)

---

🎯 What Sets Us Apart

MCP Tools · Workflow Prompts · Resources · 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)

---

Isolate Environments with Multi-Tenancy

Memory Journal supports multi-tenancy out of the box via the workspace_id construct, acting as a strict isolation barrier for multiple journals sharing the same SQLite database file.

• Auto-Resolution: When workspace_id is omitted, the server automatically resolves the target workspace. It matches project_number against PROJECT_REGISTRY, checks content/tag keyword aliases, or inspects process.cwd() before falling back to DEFAULT_WORKSPACE_ID (default: default).
• Data Partitioning & Cross-Workspace Queries: Core CRUD, Soft-Delete/Restore, FTS5 Search, Vector Semantic Search (semantic_search), and Analytics tools enforce workspace_id isolation end-to-end. Read and search tools accept workspace_id: "*" to query across all workspaces. External write and mutation paths reject wildcard overrides.
• Immutability & Controlled Migration: Entries receive a workspace_id upon creation that standard updates cannot overwrite directly. To migrate an entry across workspaces, call update_entry with workspace_id: "*" and target_workspace_id.
• Server Config: Set --default-workspace-id (or the DEFAULT_WORKSPACE_ID environment variable) to configure the default fallback workspace for the server instance. This lets you run multiple isolated journal interfaces on a single physical database.

---

flowchart TB

subgraph Session["🤖 AI Session Start"] Briefing["📋 Read Briefing (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

---

_Suggested Rule (Add to AGENTS.md, GEMINI.md, system prompts, etc.)_

View Session Initialization Routine

🛑 Session Initialization Routine

When the user initializes the session context by executing the load-briefing prompt:

1. You will receive the output of the memory://briefing/{repo_name} resource.
2. Prepend your response EXACTLY as:

📋 Briefing loaded — {repo_name}

_{paste ENTIRE briefing here}_

1. Address the user's request below the briefing.
2. NEVER autonomously execute tasks listed in the briefing.
3. Do NOT proactively ask the user to load the briefing. Wait for them to use the prompt.

---

Control Access with Tool Filtering

[!IMPORTANT]

All shortcuts and tool groups always include Code Mode (mj_execute_code) and Runtime Configuration (update_configuration) as escape-hatch tools so agents can never lock themselves out of the configuration system or Code Mode.

Control which tools are exposed using any of the 3 configuration sources (precedence: CLI flag > environment variable > config file):

• CLI flag: --tool-filter
• Environment variable: MEMORY_JOURNAL_MCP_TOOL_FILTER _(Note: TOOL_FILTER is only a fallback display variable in the session briefing and does not activate tool filtering on its own)_
• `memory-journal.config.{yaml,yml,json}` key: "toolFilter"

| readonly | Disable all m