All MCP Servers

No recent activity. No commits in 6 months. It may still work, but issues are unlikely to be fixed. See 4 alternatives.

AI & MemoryMCP RegistrynpmB · 71

repomemory MCP server

io.github.DanielGuru · Updated

Persistent memory for AI coding agents. Hybrid search, auto-session capture, context routing.

At a glance

repomemory is an MCP server in the AI & Memory category. It runs locally over stdio via `npx -y repomemory`, and declares no required credentials. It scores B (71/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source 2GitHub stars

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install repomemory in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install repomemory in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add repomemory -- npx -y repomemory
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes. It discovers them automatically.

What tools does repomemory expose?

This server runs as a local package. We only query remote servers for their tool list — asking this one would mean executing it, so its tools are listed in the documentation below.

What the code can do

Read from the published package source — never executed. Parsed 25 of 25 source files.

This server can run other programs on your machine, read and write files and make network requests.

How it was published

  • Has a provenance attestation tying this artifact to the commit it was built from.
  • 1 npm maintainer — a single point of compromise · last published by danielguru.

Maintainer of this package and think something here is wrong? Tell us and we'll correct it.

Before you install

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

What it can reach

  • Runs code on your machine — Executes as a local process with your user's permissions, including filesystem access.
  • Downloads at launch — The package is fetched from its registry each run unless you pin a version.
  • Last commit 6 months ago — No commits in over six months.
  • 2 GitHub stars — Very little community usage so far.

Client compatibility

Claude Code: NativeClaude Desktop: NativeCursor: NativeCodex CLI: NativeWindsurf: NativeCline: NativeVS Code: Native

Health score

B · 71

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

  • Maintenance30%76%

    Last commit 196 days ago.

  • Adoption20%14%

    2 stars.

  • Transparency20%75%

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

  • Provenance15%100%

    Package and registry entry point at the same repository.

  • Packaging15%100%

    Publishes a pinned version (1.3.0).

Documentation

Full README

repomemory

Your codebase never forgets.

AI agents lose context every session. repomemory fixes that — one command creates a persistent, searchable knowledge base that any AI tool can read, search, and write to.

bash
npx repomemory go

<video src="https://github.com/DanielGuru/repomemory/raw/main/repomemory-demo.gif.mp4" width="100%" autoplay loop muted playsinline></video>

The Problem

Every time you open a project with Claude Code, Cursor, Copilot, or any AI coding agent:

  • It re-discovers your architecture from scratch
  • It proposes changes that were already debated and rejected
  • It re-introduces bugs that were already fixed

Your CLAUDE.md / .cursorrules helps, but it's static and gets stale.

The Solution

text
.context/
├── index.md              ← Quick orientation (loaded every session)
├── facts/                ← Architecture, database, deployment
├── decisions/            ← "We chose Drizzle over Prisma because..."
├── regressions/          ← "This broke before. Here's what happened."
├── preferences/          ← Your coding style — follows you across all repos
├── sessions/             ← Auto-captured AI session summaries
└── changelog/            ← Monthly git history syncs

Facts tell agents how things work. Decisions prevent re-debating. Regressions prevent re-breaking. Preferences teach agents how you code.

Quick Start

Excerpt — the full document is on GitHub.

Maintain repomemory? Add a badge to your README

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

markdown
[![repomemory on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/io-github-danielguru-repomemory)](https://mcp-skills-hub.vercel.app/mcps/io-github-danielguru-repomemory)

Catalog data refreshed . Something wrong? Report it.