dev.repomemory/repomemory · v1.0.0 · productivity
RepoMemory is healthy: it completed an MCP handshake in 979 ms and exposes 5 tools.
Shared project memory for coding agents: decisions, lessons, guardrails and tasks per repository.
Endpoint: https://api.repomemory.dev/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 5 |
| Latency | 979 ms |
| Last checked (UTC) | 2026-10-29T12:55:29.862Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-29T12:55:29.862Z | Healthy | 979 |
record_entry | Write down something the next agent or teammate on this project must know: a decision and why it was made, a lesson from something that broke or was reverted, a guardrail (a rule not to break), a note, or a task to be done. Record a lesson whenever a change is rolled back or a fix took real digging, |
recall | Before planning a change, removing code that looks unnecessary, or repeating an approach, search the project's ledger for what was already decided, tried or forbidden. Put the area or change in `query`: any of its words match, best matches first, and a word in an entry's title counts for more than o |
brief | Call this first, at the start of a session, before planning any change. It returns every active guardrail (rules not to break, each with its title and the start of its reasoning, rather than left to a word match), the open and claimed tasks, and the titles of the newest decisions, lessons and notes, |
claim_task | Take a task before starting it, so another agent or teammate doesn't work on the same one. Give the task's `id` (TASK-n), or leave it out to take the oldest open task. `agent` names who is working on it ("claude-code on dimaino's laptop"). It returns a `claim_token`: keep it. A task claimed by anyon |
retire_entry | Retire a decision, lesson, guardrail or note that is no longer true, so recall stops returning it, or mark a task done. Give its `id` and, for anything but a finished task, a short `reason`. To replace an entry with a new one, use record_entry with `supersedes` instead. Retiring again changes nothin |