convez.ai
MCP ServerAutomaçãoIntermediário
gitmem-dev

GitMem — Memória Institucional para Agentes de IA

gitmem-dev/gitmem

Memória persistente que aprende com erros e sucessos entre sessões

Ver no GitHub
BomPluginScore · de 0 a 100

MCP server que fornece memória persistente de aprendizado entre sessões de agentes de IA. Registra erros (cicatrizes), sucessos (vitórias) e padrões de decisão para que o agente evolua com experiência. Compatível com Claude Code, Cursor, VS Code e ferramentas MCP.

Instalação

$npx convez-ai gitmem-dev/gitmem

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
9
Forks
2
Acompanhando
1
Saúde
87%
Último commit
há 6 dias
Versão
v1.11.1
Issues abertas
10
Contribuidores
7

Casos de uso

  • Agentes de IA que precisam reter lições entre sessões de codificação
  • Documentação automática de padrões de decisão e boas práticas
  • Registro de bugs e soluções para reutilização em projetos similares

Veredito

GitMem é uma solução técnica sólida para o problema real de agentes de IA perderem contexto entre sessões. O conceito de cicatrizes com contra-argumentos é bem pensado; execução TypeScript e integração MCP são profissionais. Valor genuíno para fluxos de desenvolvimento com múltiplas sessões.

README

A tradução para o português deste README ainda está na fila.


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  -->  ...
  1. Recall — Before acting, the agent checks memory for relevant lessons from past sessions
  2. Work — The agent does the task, applying past lessons automatically
  3. Learn — Mistakes become scars, successes become wins, strategies become patterns
  4. 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

TypePurposeExample
ScarsMistakes to avoid"Always validate UUID format before DB lookup"
WinsApproaches that worked"Parallel agent spawning cut review time by 60%"
PatternsReusable strategies"5-tier test pyramid for MCP servers"
DecisionsArchitectural choices with rationale"Chose JWT over session cookies for stateless auth"
ThreadsUnfinished 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

ClientSetupHooks
Claude Codenpx gitmem-mcp initFull (session, recall, credential guard)
Cursornpx gitmem-mcp init --client cursorPartial (session, recall)
VS Code (Copilot)npx gitmem-mcp init --client vscodeInstructions-based
Windsurfnpx gitmem-mcp init --client windsurfInstructions-based
Claude DesktopAdd to claude_desktop_config.jsonManual
Any MCP clientnpx gitmem-mcp init --client genericInstructions-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"]
    }
  }
}
ClientConfig file
Claude Code.mcp.json
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Windsurf~/.codeium/windsurf/mcp_config.json

CLI Commands

CommandDescription
npx gitmem-mcp initInteractive setup wizard (auto-detects IDE)
npx gitmem-mcp init --client <name>Setup for specific client (claude, cursor, vscode, windsurf, generic)
npx gitmem-mcp init --yesNon-interactive setup
npx gitmem-mcp init --dry-runPreview changes
npx gitmem-mcp activate <key>Activate Pro tier (auto-applies schema)
npx gitmem-mcp deactivateRemove Pro credentials, free device slot
npx gitmem-mcp setupOutput schema SQL (for manual Supabase setup)
npx gitmem-mcp uninstallClean removal (preserves .gitmem/ data)
npx gitmem-mcp uninstall --allFull removal including data
npx gitmem-mcp checkDiagnostic health check

Pro Tier

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

What you getWhy your agent cares
Semantic searchRecall returns the right scars, not keyword noise
Session analyticsSpot patterns in what keeps going wrong
Sub-agent briefingHand institutional context to sub-agents automatically
Cloud persistenceMemory survives machine changes, shareable across team
A/B testing analyticsMeasure 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.mdGitMem
LoadedEvery turn (system prompt)On-demand (tool calls)
Best forPreferences, shortcuts, quick referenceEarned lessons, unfinished work, decisions
UpdatesAgent writes directlySession 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.

Ver o original no GitHub

Bom para

Relacionados