Gitmem

Name: Gitmem
Author: gitmem-dev

by gitmem-devversion 1.2.1i★ –iRuns on your computer

Registry nameio.github.gitmem-dev/gitmem

Install

Overview

Description from the maker (original English)

Persistent institutional memory for AI coding agents. Memory that compounds.

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: Search & AI memory
You need to fill in: SUPABASE_SERVICE_ROLE_KEY

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).
You fill in yourself: SUPABASE_URL, SUPABASE_SERVICE_ROLE_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx 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": {
    "gitmem": {
      "command": "npx",
      "args": [
        "-y",
        "gitmem-mcp"
      ],
      "env": {
        "SUPABASE_URL": "your-value",
        "SUPABASE_SERVICE_ROLE_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add gitmem --env SUPABASE_URL=your-value --env SUPABASE_SERVICE_ROLE_KEY=your-value -- npx -y gitmem-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

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

{
  "mcpServers": {
    "gitmem": {
      "command": "npx",
      "args": [
        "-y",
        "gitmem-mcp"
      ],
      "env": {
        "SUPABASE_URL": "your-value",
        "SUPABASE_SERVICE_ROLE_KEY": "your-value"
      }
    }
  }
}

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": {
    "gitmem": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "gitmem-mcp"
      ],
      "env": {
        "SUPABASE_URL": "your-value",
        "SUPABASE_SERVICE_ROLE_KEY": "your-value"
      }
    }
  }
}

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.

Values you fill in

SUPABASE_URL env
Supabase project URL for pro tier features (semantic search, analytics). Not required for free tier.
SUPABASE_SERVICE_ROLE_KEY secret env
Supabase service role key for pro tier features. Not required for free tier.

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 gitmem-dev, 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 Search & AI memoryi

More stars than 0% of the other 7258 servers in this category
Published to the registry more recently than 3% of the other 7258 servers in this category
Basic checks equal to or better than 100% of the other 7258 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 Gitmem 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?

You need to fill in: SUPABASE_SERVICE_ROLE_KEY

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 (1.2.1) reached the registry 9 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Context7, Codebase Memory, Exa

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

Context7

by upstash

Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.

Computer or cloud★ 64,224MITUpdated today

Install

Codebase Memory

by DeusData

Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.

Runs on your computer★ 48,148MITUpdated 20 days ago

Install

Exa

by exa-labs

Connect AI agents to Exa for web search, content fetching, and multi-step research.

Runs in the cloud★ 5,213MITUpdated last month

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.

= 18" />

Documentation · npm · Getting Started · Tool Reference

GitMem is an MCP server that gives your AI coding agent persistent learning memory across agent sessions. It remembers mistakes (scars), successes (wins), and decisions — so your agent learns from experience instead of starting from scratch every time.

What's MCP? Model Context Protocol is how AI coding tools connect to external capabilities. GitMem is an MCP server — install it once and your agent gains persistent memory.

Works with Claude Code, Cursor, VS Code (Copilot), Windsurf, and any MCP-compatible client.

Quick Start

npx gitmem-mcp init

One command. The wizard auto-detects your IDE and sets up everything:

.gitmem/ directory with starter scars
MCP server config (.mcp.json, .vscode/mcp.json, .cursor/mcp.json, etc.)
Instructions file (CLAUDE.md, .cursorrules, .windsurfrules, .github/copilot-instructions.md)
Lifecycle hooks (where supported)
.gitignore updated

Already have existing config? The wizard merges without destroying anything. Re-running is safe.

npx gitmem-mcp init --yes                # Non-interactive

npx gitmem-mcp init --dry-run # Preview changes npx gitmem-mcp init --client vscode # Force specific client

How It Works

recall  -->  work  -->  learn  -->  close  -->  recall  -->  ...

Recall — Before acting, the agent checks memory for relevant lessons from past sessions
Work — The agent does the task, applying past lessons automatically
Learn — Mistakes become scars, successes become wins, strategies become patterns
Close — Session reflection persists context for next time

Every scar includes counter-arguments — reasons why someone might reasonably ignore it. This prevents memory from becoming a pile of rigid rules.

What Gets Remembered

Type	Purpose	Example
Scars	Mistakes to avoid	"Always validate UUID format before DB lookup"
Wins	Approaches that worked	"Parallel agent spawning cut review time by 60%"
Patterns	Reusable strategies	"5-tier test pyramid for MCP servers"
Decisions	Architectural choices with rationale	"Chose JWT over session cookies for stateless auth"
Threads	Unfinished work that carries across sessions	"Rate limiting still needs implementation"

Key Features

Automatic Recall — Scars surface before the agent takes similar actions
Session Continuity — Context, threads, and rapport carry across sessions
Closing Ceremony — Structured reflection captures what broke, what worked, and what to do differently
20+ MCP Tools — Full toolkit for memory management, search, threads, and multi-agent coordination
Zero Config — npx gitmem-mcp init and you're running
Non-Destructive — Merges with your existing .mcp.json, CLAUDE.md, and hooks

Supported Clients

Client	Setup	Hooks
Claude Code	`npx gitmem-mcp init`	Full (session, recall, credential guard)
Cursor	`npx gitmem-mcp init --client cursor`	Partial (session, recall)
VS Code (Copilot)	`npx gitmem-mcp init --client vscode`	Instructions-based
Windsurf	`npx gitmem-mcp init --client windsurf`	Instructions-based
Claude Desktop	Add to `claude_desktop_config.json`	Manual
Any MCP client	`npx gitmem-mcp init --client generic`	Instructions-based

The wizard auto-detects your IDE. Use --client to override.

Manual MCP configuration

Add this to your MCP client's config file:

"mcpServers": { "gitmem": { "command": "npx", "args": ["-y", "gitmem-mcp@latest"] } } }

Client	Config file
Claude Code	`.mcp.json`
Cursor	`.cursor/mcp.json`
VS Code	`.vscode/mcp.json`
Windsurf	`~/.codeium/windsurf/mcp_config.json`

CLI Commands

Command	Description
`npx gitmem-mcp init`	Interactive setup wizard (auto-detects IDE)
`npx gitmem-mcp init --client`	Setup for specific client (`claude`, `cursor`, `vscode`, `windsurf`, `generic`)
`npx gitmem-mcp init --yes`	Non-interactive setup
`npx gitmem-mcp init --dry-run`	Preview changes
`npx gitmem-mcp activate`	Activate Pro tier (auto-applies schema)
`npx gitmem-mcp deactivate`	Remove Pro credentials, free device slot
`npx gitmem-mcp setup`	Output schema SQL (for manual Supabase setup)
`npx gitmem-mcp uninstall`	Clean removal (preserves `.gitmem/` data)
`npx gitmem-mcp uninstall --all`	Full removal including data
`npx gitmem-mcp check`	Diagnostic health check

Pro Tier

Self-hosted on your own Supabase. You bring the infrastructure, gitmem sets it up.

What you get	Why your agent cares
Semantic search	Recall returns the right scars, not keyword noise
Session analytics	Spot patterns in what keeps going wrong
Sub-agent briefing	Hand institutional context to sub-agents automatically
Cloud persistence	Memory survives machine changes, shareable across team
A/B testing analytics	Measure which scar phrasings actually change agent behavior

Quick start

npx supabase login                                          # one time

export SUPABASE_URL="https://yourproject.supabase.co" export SUPABASE_SERVICE_ROLE_KEY="eyJ..." export OPENROUTER_API_KEY="sk-or-v1-..." npx gitmem-mcp activate

The activate command creates all tables, views, RPC functions, and indexes automatically. No manual SQL needed.

See [docs/pro-setup-guide.md](docs/pro-setup-guide.md) for the full guide.

The free tier gives you everything for solo projects. Pro makes recall smarter and memory portable.

GitMem + MEMORY.md

Your AI agent likely has its own memory file (MEMORY.md, .cursorrules, etc.). Here's how they work together:

	MEMORY.md	GitMem
Loaded	Every turn (system prompt)	On-demand (tool calls)
Best for	Preferences, shortcuts, quick reference	Earned lessons, unfinished work, decisions
Updates	Agent writes directly	Session lifecycle (close ceremony)
Example	"User prefers terse output"	"Always validate UUID before DB lookup"

Tip: Include .gitmem/agent-briefing.md in your MEMORY.md for a lightweight bridge between the two systems.

Privacy & Data

Local-first — All data stored in .gitmem/ on your machine by default
No telemetry — GitMem does not collect usage data or phone home
Cloud opt-in — Pro tier Supabase backend requires explicit configuration via environment variables
Your data — Sessions, scars, and decisions belong to you. Delete .gitmem/ to remove everything

Development

git clone https://github.com/gitmem-dev/gitmem.git

cd gitmem npm install npm run build npm test

See CONTRIBUTING.md for full development setup.

License

MIT — see LICENSE.

Gitmem

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

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 Search & AI memoryi

Common questions

Alternatives

Context7

Codebase Memory

Exa

README from the maker

Quick Start

How It Works

What Gets Remembered

Key Features

Supported Clients

CLI Commands

Pro Tier

Quick start

GitMem + MEMORY.md

Privacy & Data

Development

License