@repomem/memory

repomem

Your repo's memory and structure, available to every AI tool your team uses.

repomem keeps a team's hard-won context — decisions, conventions, limitations, learnings, and a map of what lives where — next to the code, in git, where both humans and AI assistants can find it. It is exposed to AI tools through local Model Context Protocol (MCP) servers, with no external database and no API keys.

This repository is a monorepo (npm workspaces). All four packages are published under the public @repomem scope: three library packages plus the @repomem/cli installer that wires them into your AI tool in one command.

Packages

See each package's README for its tools, configuration, and usage.

How the packages relate

memory and map are independent MCP servers that each build their agent setup on the same shared toolkit. Neither depends on the other. The repomem installer is a thin orchestrator that configures both in one pass.

graph TD
  core["@repomem/core<br/>setup toolkit"]
  memory["@repomem/memory<br/>bin: repomem-memory"]
  map["@repomem/map<br/>bin: repomem-map"]
  installer["@repomem/cli<br/>bin: repomem (installer)"]
  memory --> core
  map --> core
  installer --> memory
  installer --> map
  installer --> core

Quick start

Install nothing — npx fetches everything on demand. Run the installer and pick the servers to register with your AI tool (Kiro today; Claude Code and other MCP clients are on the roadmap):

npx @repomem/cli setup                         # interactive: choose memory / map + agent

Prefer non-interactive (CI, scripts)? Pass the agent and the servers:

npx @repomem/cli setup --agent kiro --servers all      # both servers
npx @repomem/cli setup --agent kiro --servers memory   # just memory

To scaffold the reviewable .repomem/memory/ folder in your repo:

npx --package @repomem/memory repomem-memory init

You can also configure a single server directly, without the installer:

npx --package @repomem/memory repomem-memory setup --agent kiro
npx --package @repomem/map    repomem-map    setup --agent kiro

Full configuration and tool reference live in the per-package READMEs linked above.

Making agents follow the protocol

Registering the servers is not enough if the agent never calls them. Both servers therefore reinforce the protocol over MCP itself, so it works with a generic agent and not only with the repomem Kiro agent: each sends instructions on initialize and writes when to call into every tool description (for example "call this BEFORE you modify a file"). The skills installed by setup add the longer playbooks. This guides the model; it cannot force it, and it depends on your MCP client passing server instructions and tool descriptions to the model.

Development

Requires Node.js 22+. From the repository root:

npm install        # install and link all workspaces
npm run build      # build every package (tsc / vite)
npm test           # run all workspace test suites (vitest)
npm run typecheck  # typecheck every package

Per-package scripts are available via -w, e.g. npm run build -w @repomem/map, or the convenience aliases npm run build:core, test:memory, typecheck:map, etc.

Releasing

Publishing to npm is automated by a tag-triggered GitHub Actions workflow with npm provenance. See RELEASING.md for the full process.

Contributing

See CONTRIBUTING.md for the branching model, commit conventions, and the test-driven workflow.

License

MIT