Project Memory MCP

Name: Project Memory MCP
Author: kaaustubh

by kaaustubhversion 1.6.0i★ –iRuns on your computer

Registry nameio.github.kaaustubh/project-memory-mcp

Install

Overview

Description from the maker (original English)

Persistent memory for AI coding agents — past bugs, decisions, and your corrections, in your repo.

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).
You fill in yourself: PROJECT_MEMORY_ROOT

You need

npmNode.js installed (for the npx command)

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": {
    "project-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@kaaustubh/project-memory-mcp"
      ],
      "env": {
        "PROJECT_MEMORY_ROOT": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add project-memory --env PROJECT_MEMORY_ROOT=your-value -- npx -y @kaaustubh/project-memory-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "project-memory": {
      "command": "npx",
      "args": [
        "-y",
        "@kaaustubh/project-memory-mcp"
      ],
      "env": {
        "PROJECT_MEMORY_ROOT": "your-value"
      }
    }
  }
}

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": {
    "project-memory": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "@kaaustubh/project-memory-mcp"
      ],
      "env": {
        "PROJECT_MEMORY_ROOT": "your-value"
      }
    }
  }
}

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.

Values you fill in

PROJECT_MEMORY_ROOT env
Absolute path to the folder that holds your projects (the memory root). Defaults to the parent of the script if unset, so set it when running via npx.

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 kaaustubh, 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 7258 servers in this category
Published to the registry more recently than 19% of the other 7258 servers in this category
Basic checks equal to or better than 100% of the other 7258 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 Project Memory 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.6.0) reached the registry 4 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js 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.

project-memory MCP server

A small, local MCP server that gives AI agents (Claude Code, Cursor, VS Code / GitHub Copilot, …) a shared, persistent memory of the projects in a code folder — what each project is, decisions made, and every bug/issue faced during development.

It is stateless: every tool reads/writes plain files on disk, so multiple clients (and multiple machines) share one source of truth.

The model

Layer	Lives in	Auto-loaded into context?	For
Project memory	`/AGENTS.md`	✅ yes (via `CLAUDE.md` → `@AGENTS.md`)	identity, stack, run cmds, concise decisions/learnings — keep lean
Issue log	`/issues.jsonl`	❌ no	high-volume bug/issue history — fetched on demand

Design rule: durable, low-volume facts go in AGENTS.md (auto-loaded). High-volume history (bugs) goes in issues.jsonl (queried via search_issues). This keeps the always-loaded context small while keeping everything searchable.

Works even where MCP is locked down

Some orgs disable third-party MCP servers via policy (e.g. GitHub Copilot's MCP allowlist enforcement). Because the memory is plain files, not a service, the core value survives that:

The memory itself is just files. AGENTS.md is auto-loaded by the editor reading it — no MCP call involved — so a project's identity, decisions, learnings, and preferences still land in the agent's context.
The policy is Copilot-scoped and per-client. It doesn't affect the same server in Claude Code or Cursor, and orgs running *allowlist / registry-only* mode can permit it — this server is published to the official MCP Registry (io.github.kaaustubh/project-memory-mcp).

Only the interactive tools (log_issue, search_issues, …) go over the MCP channel; the file-based memory keeps working without it.

Tools

list_projects, get_project, search_memory — read project memory
append_decision, append_learning — append a dated bullet to AGENTS.md
remember_preference — turn a correction / stated habit into a remembered pattern (## Preferences in the root AGENTS.md for a global habit, or a project's for a local one); rides the auto-load, so it comes back next session
log_issue — record a bug/problem → issues.jsonl
search_issues — "have we hit this before?" across all projects (field-scoped; optional tags filter)
list_open_issues, resolve_issue — track / close bugs
sync_registry — reconcile the root AGENTS.md projects table with what's on disk (adds rows for new projects, flags stale ones)
find_by_file — given a file path, surface the issues + decisions/learnings that touch it ("why is this code like this?")
start_initiative, get_initiative, list_initiatives, update_initiative — track a named, multi-session effort (a codename, a plan, an evolving todo list) so it's resumable from any future session by name, not just within the one that started it; see Initiatives below
check_in, check_out — stamp the start/end of the working day and record a standup summary composed from evidence harvested off disk (git commits across every repo, uncommitted WIP, memory writes, initiative progress); the next morning's check_in hands the summary back — that's your standup. Print it any time, no agent needed: npx -y @kaaustubh/project-memory-mcp standup

You don't call these directly — you talk to your agent in natural language and it picks

the tool. See Using it day to day below for what to actually say.

Using it day to day

Most of it runs itself: opening a project auto-loads its AGENTS.md (the agent already knows the project), and capture is proactive (plus the optional Stop hook). Your job is mainly to pull memory at the right moments. Just talk to your agent:

When	Say something like	What fires
Before debugging anything	"Have we hit this before? "	`search_issues` across all projects
Starting something you've done elsewhere	"How did I do Stripe webhook verification in any project?"	`search_memory` (cross-project)
Landing on confusing code	"Why is `index.js` like this? Check the memory."	`find_by_file`
You made a real decision / fixed a real bug	(nothing — it logs on its own and tells you)	`append_decision` / `log_issue`
You correct how the agent works	"No, always run the typecheck before committing — remember that."	`remember_preference` (global or per-project)
Triage	"What's still open across my projects?"	`list_open_issues`
A bug is fixed	"Resolve pulse_stripe-004 — fixed by …"	`resolve_issue`
Added a new project	"Sync the registry."	`sync_registry`

The one habit that matters: make *"have we hit this before?"* reflexive before every debugging session. That's where a memory tool earns its keep; the rest the system handles.

Capture is confirming, not silent — when the agent logs something it tells you in one line. Correct it freely: *"don't log that"*, or *"actually, log this too."*

Escape hatches: PROJECT_MEMORY_HOOK=off silences the Stop hook for one session; uninstall-hook removes it entirely.

Install (npm — recommended)

From your code/projects folder, run:

cd ~/code            # the folder that holds your projects

npx -y @kaaustubh/project-memory-mcp install

That registers the server, using the current directory as your projects root, with every client that has an MCP config location on this machine:

Client	Config written
Claude Code	user scope, via `claude mcp add`
Cursor	`~/.cursor/mcp.json`
VS Code / GitHub Copilot Chat	user-profile `mcp.json` (applies to every workspace)
GitHub Copilot CLI	`~/.copilot/mcp-config.json` (or `$COPILOT_HOME`)
JetBrains Copilot plugin (IntelliJ, PyCharm, WebStorm, …)	`~/.config/github-copilot/intellij/mcp.json`
Visual Studio (Windows)	`%USERPROFILE%\.mcp.json` — global, all solutions
Kimi Code CLI	`~/.kimi-code/mcp.json` (or `$KIMI_CODE_HOME`)
Gemini CLI	`~/.gemini/settings.json`
OpenAI Codex CLI	`~/.codex/config.toml` (the only non-JSON client — merged as TOML)
Windsurf	`~/.codeium/windsurf/mcp_config.json`

Each write merges into the existing file (other MCP servers you've already configured are left alone) and is independently best-effort — a client that isn't installed on this machine is silently skipped, the rest still get registered. Restart whichever app(s) you use, then ask your agent *"set up project memory for this folder"* to scaffold AGENTS.md for each project.

Copilot surfaces (VS Code, CLI, JetBrains, Visual Studio): tools only run in

Agent mode, and config changes need a restart to take effect.

No clone, no global install — the MCP config just runs npx, which fetches and runs

the latest version on demand.

Team memory (beta signup): want this memory shared across your team instead of

just your machine? Register your interest: https://github.com/kaaustubh/project-memory-mcp/issues/1

From source instead

git clone https://github.com/kaaustubh/project-memory-mcp.git ~/code/.memory-server

cd ~/code/.memory-server && ./install.sh

How it works (after install)

A common question: *"once I install it, does it just start doing things?"* Not quite — the server is passive. Here's the actual flow:

Restart your editor. MCP servers are loaded at startup, so the server only becomes available the next time you launch Claude Code / Cursor / VS Code.
Push layer (automatic, not the server): when you open a project, the editor reads AGENTS.md (via CLAUDE.md → @AGENTS.md) into the model's context for you. This is why the agent "just knows" what your project is — it's a built-in editor feature.
Pull layer (the server, on request): the server announces its tools and then waits. It does nothing on its own. The agent calls a tool only when it's relevant — e.g. you say *"log this bug"* or *"have we hit this before?"*, or the model decides a tool is useful. There's no background process or scanning.

Day one is empty. A fresh setup has no AGENTS.md files yet, so the auto-load has

nothing to load and log_issue will refuse until a project's memory exists. Bootstrap

once by asking your agent: *"set up project memory for this folder"* — it creates the

AGENTS.md files. After that, everything works.

In short: a convention (auto-loaded files) + a tool the agent chooses to use + a one-time setup. No magic, no daemon.

Proactive capture (you don't have to say "log this")

The server ships a standing capture policy (sent to the client on connect, plus directive tool descriptions), so the agent records things on its own instead of waiting for you to ask:

Before debugging a reported error → it checks search_issues for a prior fix.
After fixing a non-trivial bug → it calls log_issue.
After a real decision or a durable gotcha → append_decision / append_learning.
After you correct how it works or state a habit → remember_preference, so the one-time correction becomes a pattern it brings back next session.

It's proactive but not silent: the agent tells you in one line what it recorded, asks when unsure rather than logging noise, and skips trivia and secrets. You can always override — "log this", or "don't bother". The standing policy is best-effort (it depends on the model following it); for a hard guarantee, add the opt-in Stop hook below.

Guaranteed capture (opt-in Stop hook)

The standing policy can be forgotten mid-session. The Stop hook makes capture non-optional: when the agent tries to end a turn, it runs once and blocks the stop to ask for one capture pass when either (a) real work happened (file edits or a commit) and nothing was written to project memory, or (b) you corrected how it works and no preference was saved. If memory was already written, or nothing changed and you didn't correct it, the hook stays silent and lets the turn end.

npx -y @kaaustubh/project-memory-mcp install-hook    # turn it on (then restart Claude Code)

npx -y @kaaustubh/project-memory-mcp uninstall-hook # turn it off

Off by default — plain install does not add it; you enable it explicitly.
No loops — it fires at most once per turn (guarded by stop_hook_active), then lets the agent stop.
Per-session kill switch — set PROJECT_MEMORY_HOOK=off to disable without uninstalling.
Cost — it adds one extra model turn only on sessions that changed code but logged nothing, or where you corrected the agent and no preference was saved; silent otherwise.

Automatic recall (opt-in UserPromptSubmit hook)

Capture is only half the loop — the other half is *remembering to look*. The recall hook closes it: every time you submit a prompt, it matches your request against your issue history and decisions/learnings/preferences, and silently injects the strongest hits as context. So a prior fix or decision surfaces without you (or the agent) remembering to search — the "have we hit this before?" habit becomes automatic.

npx -y @kaaustubh/project-memory-mcp install-recall    # turn it on (then restart Claude Code)

npx -y @kaaustubh/project-memory-mcp uninstall-recall # turn it off

Semantic matching (when available) — if the optional embeddings model (@xenova/transformers) is installed, recall matches by meaning, so *"the build is broken"* still surfaces an issue logged as *"compile failure"* even

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

Project Memory MCP

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

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

project-memory MCP server

The model

Works even where MCP is locked down

Tools

Using it day to day

Install (npm — recommended)

From source instead

How it works (after install)

Proactive capture (you don't have to say "log this")

Guaranteed capture (opt-in Stop hook)

Automatic recall (opt-in UserPromptSubmit hook)