repo-memory-mcp

Name: repo-memory-mcp
Author: Umarjaum

by Umarjaumversion 0.2.0i★ –iRuns on your computer

Registry nameio.github.Umarjaum/repo-memory-mcp

Install

Overview

Description from the maker (original English)

Persistent local memory for MCP-compatible AI coding agents, stored per repository in SQLite.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Developer tools

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
The registry lists no key to fill in.

You need

PyPIPython’s uv installed (for the uvx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "repo-memory": {
      "command": "uvx",
      "args": [
        "repo-memory-mcp-ai"
      ]
    }
  }
}

Run this in your terminal

claude mcp add repo-memory -- uvx repo-memory-mcp-ai

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "repo-memory": {
      "command": "uvx",
      "args": [
        "repo-memory-mcp-ai"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "repo-memory": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "repo-memory-mcp-ai"
      ]
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account Umarjaum, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

More stars than 0% of the other 4901 servers in this category
Published to the registry more recently than 51% of the other 4901 servers in this category
Basic checks equal to or better than 100% of the other 4901 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is repo-memory-mcp safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 43 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

by github

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

Computer or cloud★ 34,245MITUpdated 4 days ago

Install

Desktop Commander

by wonderwhy-er

MCP server for terminal commands, file operations, and process management

Runs on your computer★ 10,225MITUpdated 16 days ago

Install

Cloudflare MCP

by cloudflare

Cloudflare MCP servers

Runs in the cloud★ 4,446Apache-2.0Updated 14 months ago

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

repo-memory-mcp

mcp-name: io.github.Umarjaum/repo-memory-mcp

Persistent memory for AI coding agents

AI coding agents are powerful, but they forget repository-specific corrections, conventions, constraints, and architectural decisions. repo-memory-mcp gives MCP-compatible coding agents a persistent, local, repository-aware memory layer.

Teach your coding agent once. Let your repository remember.

What it does

MCP hosts decide when tools are called; MCP does not automatically intercept every conversation. This project exposes explicit tools that let an agent load important context at session startup, search relevant memories, store corrections and decisions, update stale guidance, and archive obsolete memories.

The memory database lives in .repo-memory/memory.db inside the detected repository. It uses SQLite, deterministic local ranking, and no cloud service.

Why developers use it

Persistent project memory: corrections, rules, conventions, constraints, decisions, and bug-fix lessons survive sessions.
Repository-aware isolation: unrelated repositories do not share memory.
Local-first privacy: no API keys, remote database, external embeddings, telemetry, or background upload.
Explicit MCP workflow: the agent chooses when to remember and recall; there is no claim of automatic conversation interception.
Fast and inspectable: SQLite storage, JSON export, CLI diagnostics, and human-readable records.
Security-minded: likely API keys, bearer tokens, passwords, cloud credentials, and private keys are rejected by default.

Install and use in two minutes

The public PyPI distribution is named repo-memory-mcp-ai because the shorter repo-memory-mcp name is already owned by another project. The MCP server and GitHub project identity remain repo-memory-mcp.

pip install repo-memory-mcp-ai

repo-memory doctor

Start the MCP server directly:

repo-memory-mcp

Or run it without a permanent installation:

uvx --from repo-memory-mcp-ai repo-memory-mcp

The server is local and communicates over stdio. It does not need an API key.

Configure an MCP client

The common stdio configuration is:

"mcpServers": { "repo-memory": { "command": "uvx", "args": ["--from", "repo-memory-mcp-ai", "repo-memory-mcp"] } } }

Use the client-specific configuration location and format documented by your MCP host. Ready-to-copy examples are in examples/:

claude-desktop.json
cursor.json
workflow.md

The project is vendor-neutral and is intended for Claude Code, Cursor, Cline, Windsurf, and other MCP-compatible coding agents. Compatibility depends on the host’s MCP support and configuration format.

Recommended agent workflow

At the beginning of a coding session, call get_startup_context(). When the developer corrects a repeated mistake, call remember_correction(topic, lesson). When a relevant question arises, call recall_memory(query). When guidance becomes stale, call update_memory() or archive it with forget_memory().

Example instruction to an agent:

At the start of this session, call get_startup_context. If I correct a repeated mistake or establish a durable project rule, store it with the appropriate repo-memory tool. Do not store credentials or transient chat context.

Available MCP tools

Tool	Use it for
`get_startup_context`	Load concise, high-value repository guidance at session start
`remember_correction`	Store a lesson learned from a correction or bug fix
`remember_rule`	Store a durable project rule or convention
`remember_decision`	Store an architectural decision and rationale
`recall_memory`	Search active memory with deterministic local scoring
`list_project_rules`	List active project rules
`list_memories`	Filter memories by type or status
`update_memory`	Correct an existing memory without creating a replacement
`forget_memory`	Archive obsolete memory for audit-friendly retention
`export_memory` / `import_memory`	Move validated memory between safe copies of the same repository

CLI

repo-memory init

repo-memory list repo-memory rules repo-memory search "database migrations" repo-memory export ./memory-backup.json repo-memory import ./memory-backup.json repo-memory doctor

Privacy and security boundaries

Memories stay on the machine running the server. This implementation does not require API keys, cloud accounts, remote databases, external embeddings, or telemetry. It only inspects text explicitly submitted to memory tools. Your operating system, package manager, backups, and MCP host may have separate behavior.

Likely secrets are rejected by default. Do not submit passwords, tokens, private keys, or credentials to memory tools. The .repo-memory/ directory is ignored by Git so private memory is not accidentally committed.

Development

git clone https://github.com/Umarjaum/repo-memory-mcp.git

cd repo-memory-mcp python -m venv .venv . .venv/bin/activate pip install -e '.[dev]' pytest

Discovery and publishing

Project site: repo-memory-mcp.negoshades.workers.dev
Documentation: quickstart and tools
Client guides: Claude, Cursor, VS Code, Cline, and Windsurf
Extensions: VS Code and Bing-compatible browser companion
Contributions: open-source contribution guide
Source: GitHub
Package: PyPI
Registry metadata: server.json
Publishing guide: PUBLISHING.md

Developer

Muhammad Umar Jabbar — Khanewal, Punjab, Pakistan. Personal website: umarjaum.netlify.app.

Roadmap

Future work may improve ranking, add confidence feedback, provide optional local embeddings, generate project context, add a memory inspection UI, and publish the companion extensions to official marketplaces. Team/shared memory remains explicitly opt-in.

Companion extensions

extensions/vscode provides local setup commands for VS Code.
extensions/bing provides a privacy-safe Manifest V3 context-menu helper for turning selected Bing research into a repo-memory prompt.

The browser companion intentionally does not invoke the local stdio MCP process. Direct browser-to-MCP integration would require a separately reviewed native-messaging bridge.

License

MIT. See LICENSE.

repo-memory-mcp

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Developer toolsi

Common questions

Alternatives

GitHub

Desktop Commander

Cloudflare MCP

README from the maker

repo-memory-mcp

Persistent memory for AI coding agents

What it does

Why developers use it

Install and use in two minutes

Configure an MCP client

Recommended agent workflow

Available MCP tools

CLI

Privacy and security boundaries

Development

Discovery and publishing

Developer

Roadmap

Companion extensions

License