Memory Journal MCP

Name: Memory Journal MCP
Author: neverinfamous

作者：neverinfamous版本 1.1.3i★ –i在你的电脑上运行

注册名称io.github.neverinfamous/memory-journal-mcp

安装

概览

作者提供的说明（英文原文）

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

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
注册中心没有列出需要填写的密钥。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

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

在终端中运行这条命令

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

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

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

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 neverinfamous 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“搜索与 AI 记忆”中的其他服务器比较i

星标数多于此分类中其他 7258 个服务器的 0%
发布到注册中心的时间比此分类中其他 7258 个服务器的 0% 更新
基础检查结果等于或优于此分类中其他 7258 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

Memory Journal MCP 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.1.3）于13个月前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Context7, Codebase Memory, Exa

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Context7

作者：upstash

Up-to-date docs for AI agents

电脑或云端★ 64,224MIT今天更新

安装

Codebase Memory

作者：DeusData

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

在你的电脑上运行★ 48,148MIT20天前更新

安装

Exa

作者：exa-labs

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

在云端运行★ 5,213MIT上个月更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

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

只显示了开头部分；其余内容请在仓库中阅读