Memory Journal MCP

Name: Memory Journal MCP
Author: neverinfamous

by neverinfamousversion 1.1.3i★ –iRuns on your computer

Registry nameio.github.neverinfamous/memory-journal-mcp

Install

Overview

Description from the maker (original English)

Developer journal with knowledge graphs, relationships, Git context, and semantic search

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Search & AI memory

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

DockerDocker installed

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "memory-journal": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/writenotenow/memory-journal-mcp:v1.1.3"
      ]
    }
  }
}

Run this in your terminal

claude mcp add memory-journal -- docker run -i --rm docker.io/writenotenow/memory-journal-mcp:v1.1.3

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "memory-journal": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/writenotenow/memory-journal-mcp:v1.1.3"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "memory-journal": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "docker.io/writenotenow/memory-journal-mcp:v1.1.3"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account neverinfamous, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Search & AI memoryi

More stars than 0% of the other 7254 servers in this category
Published to the registry more recently than 0% of the other 7254 servers in this category
Basic checks equal to or better than 100% of the other 7254 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Memory Journal MCP safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.1.3) reached the registry 13 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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)

Feature	Description
Session Intelligence	Auto-query project history, create checkpoints, and hand off context between sessions automatically.
GitHub Integration	Manage Issues, PRs, Actions, Kanban boards, and milestones. Access Copilot reviews and repository insights.
Dynamic Project Routing	Switch contexts seamlessly and access CI/Issue tracking across multiple repositories from a single server instance.
Knowledge Graphs	Link specifications, implementations, tests, and PRs visually using Mermaid diagrams.
Hybrid Search	Find entries instantly using a blend of keyword, semantic, and date-range searches.
Code Mode	Execute multi-step operations efficiently in a sandboxed environment to reduce token usage.
Adaptive Session Briefing	Deliver real-time workspace context dynamically, including live CI health, local Git status, and unreleased changes.
Reports & Analytics	Generate standups, retrospectives, PR summaries, digests, and period analyses.
Heuristic Scoring	Optimize context delivery by scoring entries based on veracity and impact.
Team Collaboration	Share databases across teams with cross-project insights, author attribution, and role-based access control.
Data Interoperability	Export schemas safely, sync Markdown directories, and maintain a unified IO namespace.
Backup & Restore	Secure data with automated scheduling, retention policies, and one-command restores.
Auto-Pruning	Soft-delete low-value entries automatically to maintain search relevance over long-running projects.
Security & Transport	Ensure secure connections with OAuth 2.1, Streamable HTTP, rate limiting, and SQL injection prevention.
Structured Error Handling	Provide agents with classification, remediation hints, and recoverability signals on every tool call.
Agent Collaboration	Share context between IDE agents and Copilot. Search review findings and let agents suggest reusable rules.
Native Agent Skills	Establish permanent AI behavior and architecture rules using bundled foundational coding paradigms.
GitHub Commander	Audit code, triage issues, review PRs, and run sprint milestones via automated pipeline skills.

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:

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

📋 Briefing loaded — {repo_name}

_{paste ENTIRE briefing here}_

Address the user's request below the briefing.
NEVER autonomously execute tasks listed in the briefing.
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"

Filter	Use Case
`full`	All tools (default)
`starter`	Core + search + codemode
`essential`	Minimal footprint

| readonly | Disable all m

Only the beginning is shown; read the rest in the repo

Memory Journal MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Memory Journal MCP Server

🧠 Eliminate AI Amnesia

🎯 What Sets Us Apart

Isolate Environments with Multi-Tenancy

Control Access with Tool Filtering