projectmem — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track memory schema and package updates because persisted project context evolves

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Local project memory and repeated-failure prevention for coding agents

What we know

Local-first, event-sourced memory for coding agents that records issues, attempts, fixes and decisions and can warn before repeated failed approaches.

Maintenance / activity evidence

Observed Oct 3, 2026 (UTC)docs: add CITATION.cff, and list the paper under cs.AI

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Activity source · commits ↗Activity source · releases ↗

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Reads/writes projectmem event logs and project metadata. Writes: Store issues/attempts/fixes/decisions; Update local memory files.
Authentication not yet verified.
Sensitive access: Source/project history, Engineering decisions

Local-first operation is bounded, but durable repository memory should be protected like source code.

Security source · repository notice ↗Security source · policy file ↗

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

834 repository stars

Stars observed Sep 25, 2026.

Preserve any already-reviewed adoption metrics in MCP100. Batch 4 did not refresh package downloads because the package-stats provider had insufficient credits.

All limitations / Review context

Which project-memory operations and deployment modes remain supported?

The bounded assessment reviewed the official README, repository notices, security policy path, and security page for known material public-tracking blockers. No such blocker was identified. This is a public-tracking assessment, not an installation safety certification.

Local-first operation is bounded, but durable repository memory should be protected like source code.
Reads/writes projectmem event logs and project metadata.
README states normal operation is local and makes no network calls unless online update checks are enabled.
Reviewed write actions: Store issues/attempts/fixes/decisions; Update local memory files
Sensitive access: Source/project history, Engineering decisions
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No independent runtime, installation, or comprehensive security audit was performed.
No installation, runtime, client matrix, or complete tool-contract audit was performed in this review.
Persistent memory may contain proprietary engineering context.
Online update checks are optional; normal operation is local.

Original activity observations

2026-10-03T00:01:17Z: docs: add CITATION.cff, and list the paper under cs.AI

Technical identity

github.com/riponcm/projectmem

Exact implementation source: https://github.com/riponcm/projectmem ↗
Reviewed resource type: MCP Server
Repository identity: riponcm/projectmem
Package identity: pypi:projectmem

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 6, 2026

GitHub repository ↗
riponcm/projectmem
Recorded repository material and project history.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
projectmem adds long-term code project memory and exposes MCP.
publisher documented step · Publisher instructions
pip install projectmem
publisher documented step · Publisher instructions
pjm init
publisher setup or prerequisite · Publisher instructions
pip install -U projectmem
publisher setup or prerequisite · Publisher instructions
pjm doctor
Configure / authenticate
MCP100 setup guide
`pjm init` activates project Git hooks/file watcher. Connect the MCP server in your chosen client using its published config. Review hooks before running init.
Previously reviewed prerequisites / client guidance: For Claude Desktop or similar JSON clients, configure command as the absolute Python interpreter path and args ["-m","projectmem.mcp_server"]; keep working directory at project root or use publisher autodiscovery. Do not paste this JSON into Codex TOML.
Check connection
Suggested check
`pjm doctor` validates installation/known config issues; separately inspect tools in MCP client.
Remove / uninstall / revoke
MCP100 setup guide
Unregister projectmem from the chosen MCP client; check `pjm doctor` after restart for stale registration. `python -m pip uninstall projectmem` removes the Python package but does not delete .projectmem project memory or Git hooks installed with `pjm init`. Remove hooks separately only after reviewing them.
Client unregistration, program uninstall, persistent-data deletion, and credential revocation must be treated separately.
Package / application uninstall · matching installation environment · MCP100 composed guide
python -m pip uninstall projectmem

Official Documentation & Sources

What it does

Local-first, event-sourced memory for coding agents that records issues, attempts, fixes and decisions and can warn before repeated failed approaches.

Capability: Files & Knowledge
Resource type: MCP Server
Industry: Software & Technology
Best fit: Local project memory and repeated-failure prevention for coding agents

Representative uses

Initialize memory per repository
Recall prior decisions and failed attempts
Precheck files before edits
Serve multiple projects from one MCP process

Limitations

Persistent memory may contain proprietary engineering context.
Online update checks are optional; normal operation is local.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Reads/writes projectmem event logs and project metadata.
Data handling: README states normal operation is local and makes no network calls unless online update checks are enabled.
Cost: free
Risk and cautions: Local-first operation is bounded, but durable repository memory should be protected like source code.

Access scope and cautions

Write actions: Store issues/attempts/fixes/decisions Update local memory files
Sensitive access: Source/project history Engineering decisions
Risk level: moderate

FAQ

Based on reviewed evidence as of 2026-10-06. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Initialize memory per repository; Recall prior decisions and failed attempts; Precheck files before edits; Serve multiple projects from one MCP process.

What setup information is documented?

Recorded installation/entrypoint step: pip install -U projectmem. Recorded transport: stdio. Prerequisites: Python. Client notes: Use `pjm init` in each repo; the MCP command is `python -m projectmem.mcp_server`. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Documented write actions include: Store issues/attempts/fixes/decisions; Update local memory files. Recorded permission boundary: Reads/writes projectmem event logs and project metadata.

What data-handling boundary should I consider?

README states normal operation is local and makes no network calls unless online update checks are enabled. Recorded sensitive-access context: Source/project history; Engineering decisions.

What limitations and risks should I check before use?

Local-first operation is bounded, but durable repository memory should be protected like source code. Persistent memory may contain proprietary engineering context. Online update checks are optional; normal operation is local. No independent runtime, installation, or comprehensive security audit was performed.

Is this an official MCP?

riponcm is listed as Community implementation in MCP100’s current evidence.