@repomem/cli

One-command installer for repomem.

@repomem/cli wires the repomem MCP servers into your AI tool in a single pass. It is a thin orchestrator over two independent servers:

• @repomem/memory — your repo's reviewable markdown memory, searchable over MCP.
• @repomem/map — a structure map and dependency graph (optional companion).

You do not need to install anything: npx fetches everything on demand.

Usage

Interactive — choose which servers to configure and for which agent:

npx @repomem/cli setup

Non-interactive — pass the agent and the servers (handy for CI and scripts):

npx @repomem/cli setup --agent kiro --servers all        # both servers
npx @repomem/cli setup --agent kiro --servers memory     # just memory
npx @repomem/cli setup --agent kiro --servers memory,map # explicit list

Options

| Flag | Description | |---|---| | --agent <name> | Target agent. Supported today: kiro. | | --servers <list> | Comma-separated server ids (memory, map) or all. | | --root <dir> | Repository root to write .kiro/ into. Defaults to the enclosing git root. | | --force | Refresh repomem's own entries and files (skills, hook scripts, MCP config) to the version you're running. Changed files are listed as updated. Foreign servers and your own hooks are never touched. Use it after upgrading to pick up fixes. |

When both --agent and --servers are provided, the installer runs non-interactively. Otherwise it opens an interactive menu.

Versions and updates

npx @repomem/cli --version

prints the installed versions of @repomem/cli, memory, map and core, and marks any that have a newer release on npm, with the command to run the latest (npx @repomem/cli@latest setup). npx caches what it downloaded, so an old copy can keep running until you ask for @latest.

The interactive menu does the same check once and prints a one-line notice before prompting. Details:

• The check only sends package names to the public npm registry, has a 2 s timeout, and fails silently when offline.
• It never runs in non-interactive mode (--agent + --servers), so CI and scripts make no network call.
• Set REPOMEM_NO_UPDATE_CHECK=1 to disable every registry lookup.
• It does not update anything by itself and does not change the MCP config written by setup.

What it does

For each selected server, the installer runs that package's own setup, writing (idempotently, under the repository root):

• .kiro/skills/<id>/SKILL.md — the server's skill(s)
• .kiro/hooks/<name> — hook scripts (memory only)
• .kiro/agents/repomem.json — a shared repomem agent accumulating both servers
• .kiro/settings/mcp.json — the MCP server entries

All writes are additive and non-destructive: existing files are left untouched (or merged, for JSON) unless --force is set. To bring an existing install up to date after upgrading, re-run with --force:

npx @repomem/cli@latest setup --agent kiro --servers all --force

Configuring a single server directly

You can skip the installer and configure one server at a time:

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

License

MIT