Bietet ein persistentes Lern-Gedächtnis für AI Coding Agents, damit diese Fehler, Erfolge und Architektur-Entscheidungen über verschiedene Sessions hinweg behalten.
Auch bekannt als gitmem-dev/gitmem, gitmem-mcp
- Stars
- 9
- Tools
- —
- Downloads, 30 Tage
- —
- Neueste Version
- 1.2.1
- Letzter Commit
- 13. Nov. 2026
- Lizenz
- MIT
Was ist GitMem MCP?
GitMem ist ein MCP server. Bietet ein persistentes Lern-Gedächtnis für AI Coding Agents, damit diese Fehler, Erfolge und Architektur-Entscheidungen über verschiedene Sessions hinweg behalten.
Zusammenfassung generiert aus dem README des Projekts
Über GitMem MCP server
GitMem bietet eine persistente Memory-Layer für AI Coding Agents, um Wissen über verschiedene Sessions hinweg zu speichern. Es ermöglicht Agents, Fehler als Scars, Erfolge als Wins und Architektur-Entscheidungen als Decisions zu hinterlegen. Das verhindert, dass Entwickler Instruktionen wiederholen oder den Kontext jedes Mal neu erklären müssen, wenn eine neue Chat-Session startet.
Nutzer können den Server mit einem einzigen Befehl einrichten, der Umgebungen wie Claude Code, Cursor, VS Code oder Windsurf automatisch erkennt. Das System ist Local-first und speichert die Daten in einem .gitmem Verzeichnis auf deinem Rechner. Für Teams oder fortgeschrittene Nutzer gibt es einen Pro-Tier, der eine selbst gehostete Supabase Instanz anbindet, um Semantic Search und Cloud-Persistenz zu ermöglichen.
Der Server enthält über 20 MCP Tools zum Verwalten des Memorys, zum Durchsuchen vergangener Lessons und zum Handhaben von unfertigen Work-Threads. Er integriert sich in bestehende Config-Dateien wie .cursorrules oder CLAUDE.md, um sicherzustellen, dass der Agent sofortigen Zugriff auf den relevanten Kontext hat, ohne dass manuell eingegriffen werden muss.
Was du damit machen kannst
- 1Vermeidung wiederkehrender Coding-FehlerEin AI Agent kann sich an spezifische Fehler erinnern, die vermieden werden sollen – wie etwa Validierungsanforderungen –, bevor er neuen Code schreibt.
Geschrieben aus dem README des Projekts. Jeder Use Case wurde gegen ein Zitat daraus geprüft.
So installierst du GitMem MCP
Formate geprüft am 10. Nov. 2026Zu Cursor hinzufügenZu Goose hinzufügenGitMem MCP in Claude Code installieren
$ claude mcp add --env 'SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>' gitmem -- npx -y gitmem-mcpGitMem MCP in Cursor installieren
~/.cursor/mcp.json
{
"mcpServers": {
"gitmem": {
"command": "npx",
"args": [
"-y",
"gitmem-mcp"
],
"env": {
"SUPABASE_SERVICE_ROLE_KEY": "<YOUR_SUPABASE_SERVICE_ROLE_KEY>"
}
}
}
}GitMem MCP in VS Code installieren
.vscode/mcp.json
{
"servers": {
"gitmem": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"gitmem-mcp"
],
"env": {
"SUPABASE_SERVICE_ROLE_KEY": "<YOUR_SUPABASE_SERVICE_ROLE_KEY>"
}
}
}
}GitMem MCP in VS Code CLI installieren
$ code --add-mcp '{"name":"gitmem","type":"stdio","command":"npx","args":["-y","gitmem-mcp"],"env":{"SUPABASE_SERVICE_ROLE_KEY":"<YOUR_SUPABASE_SERVICE_ROLE_KEY>"}}'GitMem MCP in Claude Desktop installieren
claude_desktop_config.json
{
"mcpServers": {
"gitmem": {
"command": "npx",
"args": [
"-y",
"gitmem-mcp"
],
"env": {
"SUPABASE_SERVICE_ROLE_KEY": "<YOUR_SUPABASE_SERVICE_ROLE_KEY>"
}
}
}
}GitMem MCP in Codex installieren
$ codex mcp add gitmem --env 'SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>' -- npx -y gitmem-mcpGitMem MCP in Codex config.toml installieren
~/.codex/config.toml
[mcp_servers.gitmem] command = "npx" args = ["-y", "gitmem-mcp"] [mcp_servers.gitmem.env] SUPABASE_SERVICE_ROLE_KEY = "<YOUR_SUPABASE_SERVICE_ROLE_KEY>"
GitMem MCP in Gemini CLI installieren
$ gemini mcp add -s user -e 'SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>' gitmem npx -- -y gitmem-mcpGitMem MCP in Gemini settings.json installieren
~/.gemini/settings.json
{
"mcpServers": {
"gitmem": {
"command": "npx",
"args": [
"-y",
"gitmem-mcp"
],
"env": {
"SUPABASE_SERVICE_ROLE_KEY": "<YOUR_SUPABASE_SERVICE_ROLE_KEY>"
}
}
}
}Konfiguration
SUPABASE_SERVICE_ROLE_KEYSecretSupabase service role key for pro tier features. Not required for free tier.
OPENROUTER_API_KEYSUPABASE_URLSupabase project URL for pro tier features (semantic search, analytics). Not required for free tier.
| Name | Beschreibung | Typ |
|---|---|---|
| SUPABASE_SERVICE_ROLE_KEY | Supabase service role key for pro tier features. Not required for free tier. | Secret |
| OPENROUTER_API_KEY | — | |
| SUPABASE_URL | Supabase project URL for pro tier features (semantic search, analytics). Not required for free tier. |
Automatisierte Checks
Geluften am 12. Nov. 2026Vollständiger Bericht →Unsere automatisierten Checks bestanden. Das ist kein Security-Audit: Lies den Code und gib dem Server nur den minimal notwendigen Zugriff. Wie die Checks funktionieren
- Source Repository verknüpft und erreichbarBestanden
- Open Source Lizenz (OSI)Bestanden
- Commit oder Release im letzten JahrBestanden
- Package-Name ähnelt keinem populären PackageBestanden
- Remote Endpoint nutzt HTTPSNicht geprüft
- Destruktive Tools sind markiertNicht geprüft
- Keine versteckten Anweisungen an das ModellBestanden
- Keine kritischen Advisories im Paket oder seinen AbhängigkeitenBestanden
README
Auf GitHub ansehenGitMem 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)
.gitignoreupdated
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 initand 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.
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 <name> |
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 <key> |
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 <your-license-key>
The activate command creates all tables, views, RPC functions, and indexes automatically. No manual SQL needed.
See 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 MCP Fragen
Wie füge ich GitMem MCP zu Claude Code hinzu?
Führe claude mcp add --env 'SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>' gitmem -- npx -y gitmem-mcp in deinem Terminal aus. Füge --scope user hinzu, damit der Server in jedem Projekt verfügbar ist.
Wie füge ich GitMem MCP zu Cursor hinzu?
Öffne ~/.cursor/mcp.json und füge den Server unter mcpServers hinzu, mit der Cursor-Config aus dem Installationsabschnitt oben.