RepoMemory MCP server

What does RepoMemory need from you?

API key — Your RepoMemory API key (create one at https://repomemory.dev/dashboard/keys); clients usually read it from the REPOMEMORY_KEY environment variable.

• X-API-KeyrequiredsecretHTTP header

  Your RepoMemory API key (create one at https://repomemory.dev/dashboard/keys); clients usually read it from the REPOMEMORY_KEY environment variable.

What tools does RepoMemory expose? (5)

Read from the live server. Click any tool for its input schema.

• record_entryWrite 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, and a decision whenever an approach is chosen over another. `kind` is decision, lesson, guardrail,
• recallBefore 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 one in its body. Use the words that would appear in the entry, not the words of the symptom: 'captcha
• briefCall 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, so you start where the last session stopped. Bodies are cut short to keep it small: recall with an
• claim_taskTake 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 anyone else, even a session with your own name, is refused with already_claimed; claiming again with your
• retire_entryRetire 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 nothing. Free. Returns the entry with its new status. Free to call.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

• No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

• Maintenance30%not measurable

  No commit history available.

• Adoption20%not measurable

  No usage data available.

• Transparency20%25%

  1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

• Provenance15%0%

  No source repository to trace the code back to.

• Packaging15%100%

  Remote endpoint with documented authentication.

Maintain RepoMemory? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

[![RepoMemory on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/dev-repomemory-repomemory)](https://mcp-skills-hub.vercel.app/mcps/dev-repomemory-repomemory)