MCP.Market

CP Memory MCP server

by CJhuochai·io.github.CJhuochai/cp-memory·v1.8.1·1 stars

Local-first, governable long-term memory for AI coding agents

A88/100grade A
What users say
No reviews yet
Be the first
Safety scan
A88/100

full report

Adoption
New

1 stars29 downloads/wk

Reviews

Write one

Nobody has reviewed CP Memory yet.

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

CP Memory tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • Code scan1 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 38 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 88/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How CP Memory compares

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

Safety score
88/100
higher than 75% of 48,243 servers
GitHub stars
1
more than 65% of 28,706 servers
Downloads a week
29
more than 16% of 12,306 servers with a package

Install CP Memory in Claude Code, Cursor or VS Code

claude mcp add cp-memory -- uvx cp-memory-mcp
Add to Cursor

What the publisher says

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

CP Memory

<!-- mcp-name: io.github.CJhuochai/cp-memory -->

Local-first, governable memory for AI coding agents. Remember project rules across sessions, recall only what matters, and correct bad memory without hiding history.

简体中文 | English

Why CP Memory

For reproducible package, protocol and recall checks, see verification evidence and limits.

  • Local first: memory stays in ~/.cp-memory/memory.db by default.
  • Governable: inspect, review, correct, scope, or retire memory instead of silently overwriting it.
  • MCP-ready, Codex-enhanced: the stdio MCP server is the portable baseline; the Codex plugin adds Skills and lifecycle Hooks.

Quick Start — Portable MCP

With Python 3.10+ and uv installed, any stdio MCP client can start CP Memory with:

uvx cp-memory-mcp

The public package passed a clean-cache MCP handshake with all 40 tools and a write/search/correct flow. See MCP client setup for Codex, Claude Code, Cursor, VS Code, and Gemini CLI examples.

For the enhanced Codex integration with lifecycle Hooks and Skills, install the plugin:

codex plugin marketplace add CJhuochai/cp-memory
codex plugin add cp-memory@cp-memory

Restart Codex after installation and approve the lifecycle Hooks if prompted.

See The Result In 30 Seconds

  1. Tell Codex a project rule, such as: “Releases must start on a branch, run tests, and merge through a PR.”
  2. In a later session, CP Memory restores the relevant rule from the local primary store so Codex can continue following it.
  3. If the rule is wrong, preserve correction history and mark the old record wrong, stale, or scoped instead of silently overwriting it.

CP Memory is a local-first memory plugin for Codex. It stores facts, preferences, ongoing work, episodes, decisions, and conversation checkpoints in a local SQLite database, then restores relevant context through MCP tools and lifecycle hooks.

The goal is not to remember as much as possible. The goal is memory that remains trustworthy after long-term use: explainable, reviewable, correctable, and governable.

Current Capabilities

  • Context restore: restores relevant local-primary memory on startup and eligible prompts.
  • Automatic extraction: conservatively creates long-term personal memory candidates from explicit statements.
  • Project scope: prioritizes current-project memories with repo:, project:, and workspace: scopes.
  • Reviewable governance: supports review inbox, review digests, conflict suggestions, correction states, and startup reminders.
  • Safe maintenance: weekly maintenance runs health checks, governance preflight, and low-risk expiry cleanup only.

30-Second Example

You tell Codex:

Remember this: releases for this project must start on a branch, run tests, and merge through a PR.

In a later session, you ask:

What are the release rules for this plugin?

Shortened. The full README is on GitHub.

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

CP Memory: common questions

Is CP Memory MCP server safe?
Yes, by our scan: it is graded A (88/100). Read the CP Memory safety report
How do I install CP Memory?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does CP Memory need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is CP Memory maintained?
The last commit was 58 days ago (2026-09-08). The latest release is v1.8.1.
What can I use instead of CP Memory?
Servers from other publishers that do the same job: Nautilus Compass Memory MCP server, Deja Vu MCP server and Memorix MCP server.
How does CP Memory compare with other MCP servers?
safety score 88/100 (higher than 75% of 48,243 servers); github stars 1 (more than 65% of 28,706 servers); downloads a week 29 (more than 16% of 12,306 servers with a package). Full comparison.

Alternatives to CP Memory

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

  • Nautilus Compass Memory
    Local-first long-term memory for AI agents, with byte-recomputable signed verification receipts.
    B
  • 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