MCP.Market

Project Memory MCP server

by kaaustubh·io.github.kaaustubh/project-memory-mcp·v1.6.0·1 stars
No reviews yet

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

A92/100grade A
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

1 stars53 downloads/wk

Reviews

Write one

Nobody has reviewed Project Memory yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Project Memory tools (12)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • append_decision

    Append a dated bullet under '## Decisions' in a project's AGENTS.md (auto-loaded memory). Call this PROACTIVELY right after a non-obvious or architectural decision is made — don't wait to be asked — then tell the user in one line what you recorded. For concise, durable decisions and WHY; not bugs (use log_issue) and not trivia.

  • append_learning

    Append a dated bullet under '## Learnings' in a project's AGENTS.md (auto-loaded memory). Call this PROACTIVELY when you discover a durable gotcha/workaround future sessions should know — don't wait to be asked — then tell the user what you recorded. For a specific bug use log_issue instead.

  • find_by_file

    Given a file path or filename fragment, return the issues (matched via their 'files' field) and the decisions/learnings (matched via AGENTS.md bullets that mention it) that touch that file — i.e. 'why is this code the way it is?' answered from memory. Searches all projects unless one is given. Useful when you land on confusing code and want the history behind it.

  • get_project

    Return the full AGENTS.md memory for one project.

  • list_open_issues

    List unresolved issues across all projects (or one).

  • list_projects

    List all projects under ~/code that have an AGENTS.md memory file.

  • log_issue

    Append a structured bug/issue to <project>/issues.jsonl (high-volume memory, NOT auto-loaded). Call this PROACTIVELY whenever you resolve (or get blocked by) a non-trivial bug — don't wait to be asked — then tell the user in one line what you logged. Skip trivial/transient issues.

  • remember_preference

    Append a dated bullet under '## Preferences' in an AGENTS.md (auto-loaded memory), turning a user correction or stated habit into a remembered pattern that comes back next session. Call this PROACTIVELY when the user corrects HOW you work or states a durable preference — code style, workflow habit, a 'from now on' rule (e.g. 'never add a co-author trailer', 'always run the typecheck before committ

  • resolve_issue

    Mark an issue resolved and record the fix.

  • search_issues

    Search bug/issue history across all projects (or one) over the TEXT FIELDS only (symptom, cause, fix, id, tags) — not the raw JSON, so you won't get false hits on field names like 'fix' or 'status'. Optionally filter by tags (issue must carry all of them). Either query or tags may be given. Call this PROACTIVELY when the user reports an error or you hit a familiar-looking failure, BEFORE debugging

  • search_memory

    Case-insensitive search across every project's AGENTS.md. Returns matching lines with their project.

  • sync_registry

    Reconcile the root AGENTS.md projects table with what's actually on disk: list projects that have an AGENTS.md but no table row (and add a stub row for each), flag rows whose directory no longer exists, and show live open-issue counts. Automates the 'new project → add a row' step so the cross-project index never silently drifts. Hand-curated columns (Stack, Status, descriptions) are preserved — st

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 16 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Project Memory compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
12
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
53
more than 44% of 12,191 servers with a package

What its tools let an agent do: 11 read · 1 change

Install Project Memory in Claude Code, Cursor or VS Code

Runs npx -y @kaaustubh/project-memory-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add project-memory-mcp -- npx -y @kaaustubh/project-memory-mcp
Add to Cursor

What the publisher says

From the Project Memory repository's README, as published. We do not edit it. Read it on GitHub

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

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:

no MCP call involved — so a project's identity, decisions, learnings, and preferences still land in the agent's context.

  • The memory itself is just files. AGENTS.md is auto-loaded by the editor reading it —

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).

  • The policy is Copilot-scoped and per-client. It doesn't affect the same server in

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

Tools

  • listprojects, getproject, search_memory — read project memory
  • appenddecision, appendlearning — 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)
  • listopenissues, 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)
  • findbyfile — given a file path, surface the issues + decisions/learnings that touch it ("why is this code like this?")
  • startinitiative, getinitiative, listinitiatives, updateinitiative — 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
  • checkin, checkout — 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

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Project Memory: common questions

Is Project Memory MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Project Memory safety report
How do I install Project Memory?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Project Memory need an API key?
No secret keys are declared. It reads 1 setting from the environment.
Is Project Memory maintained?
The last commit was 56 days ago (2026-09-09). The latest release is v1.6.0.
What can I use instead of Project Memory?
Servers from other publishers that do the same job: State Memory MCP server, Deja Vu MCP server and Memorix MCP server. Compare all Project Memory alternatives.
How does Project Memory compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 12 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Project Memory

Same job from other publishers: the closest match first, then the best rated.

All Project Memory alternatives →
  • State Memory MCP
    Persistent workflow graph server tracking tasks, decisions, spatial entities, and blockers.
    A
  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • Memorix
    Local-first project memory with legacy MCP and 2026 discovery compatibility.
    B
  • Knowl
    Persistent memory for AI agents, for code, research and everyday life. Stale facts retire.
    A
  • Tradememory Protocol
    Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents.
    B