riponcm/projectmem
latest · 0.3.3Coding agent memory — one local MCP server for every project. Warns before repeating failed fixes.
- GitHub
- riponcm/projectmem
- PyPI
- projectmem
- MCP registry
- io.github.riponcm/projectmem
Install
claude mcp add io-github-riponcm-projectmem -- uvx projectmem/mcp confirms it's connected.
Or add it manually in ~/.cursor/mcp.json:
{
"mcpServers": {
"io-github-riponcm-projectmem": {
"command": "uvx",
"args": [
"projectmem"
]
}
}
}In claude_desktop_config.json (Settings → Developer → Edit Config), then restart:
{
"mcpServers": {
"io-github-riponcm-projectmem": {
"command": "uvx",
"args": [
"projectmem"
]
}
}
}Config entry, any MCP client:
{
"command": "uvx",
"args": [
"projectmem"
]
}Community score
from web signals · no reviews yet · 1 mention · 1 reaction (community v3)
- Web signals (ecosystem baseline)60/100 · 100% of the weight
No reviews yet — be the first.
What the web says
Objective public usage & activity (formula v3) — the community score's web-signals input, and its own sort.
- GitHub stars · 27 days ago
- ★ 828
- Last commit · 27 days ago
- 5 days ago
- Issue close rate · 27 days ago
- 78%
No package-registry data collected yet.
- Glama · 6 days ago
- Listed · Glama quality score 4.1 ↗
Quotes1
- `record_fix` and `pjm fix` cannot target an issue and may silently close the wrong one ↗
Tested against projectmem 0.1.4, main commit 4efc547. Problem record_fix (MCP) and pjm fix (CLI) provide no way to specify which issue should be closed. Unlike record_attempt and pjm attempt, they resolve their target implicitly from mutabl…
No liveness or verification signals yet.
Version history1
- 0.3.3release date unknown
Details
- Transport
- stdio
- Status
- listed
- Source
- Imported from the MCP registry
- Repository
- source ↗