gitmem
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@gitmemwhat did we decide about password hashing?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
 š§ gitmem Git-native persistent memory & task graph for AI coding agents. The lightweight, TypeScript-native alternative to Beads. Zero Dolt. Zero Go. Just pure git.
ā” The Problem
AI coding agents (Claude Code, Cursor, Windsurf, Antigravity) lose their memory between sessions. Every time you open a new conversation, change branches, or have a teammate pull the code:
Architectural decisions are forgotten.
Past bugs and lessons are repeated.
Complex multi-step task graphs get lost.
Beads introduced versioned agent memory, but requires a heavy Go binary and an external Dolt SQL database daemon running on your machine.
gitmem gives your agents persistent, dependency-aware memory stored as plain JSON and Markdown committed directly into your repository.
Related MCP server: ITHZ MCP
š„ Beads vs. gitmem
Feature | Beads | š§ gitmem |
Runtime | Go binary | Node.js / TypeScript Native |
Storage Engine | Dolt SQL Database Daemon | Plain Git (JSON + Readable Markdown) |
Installation | Heavy custom install / Dolt setup |
|
Install Size | ~150 MB+ | < 3 MB |
PR & Code Review | Hidden in Dolt binary storage | Clean, reviewable |
MCP Standard | Custom protocol wrappers | Native |
Human Readable | Requires SQL queries | Auto-syncs |
š 30-Second Quickstart
In your repository root:
npx gitmem initThat's it! gitmem will scaffold .gitmem/ and automatically configure your Cursor (.cursor/mcp.json) or Claude Desktop environment.
Attach to Claude Code
claude mcp add gitmem npx -y gitmem mcpAttach to Cursor / Windsurf
Add this to your MCP configuration (.cursor/mcp.json or settings):
{
"mcpServers": {
"gitmem": {
"command": "npx",
"args": ["-y", "gitmem", "mcp"]
}
}
}š ļø MCP Tools for Agents
When attached to an agent, gitmem exposes these standard MCP tools:
gitmem_context: Dumps instant project briefing (tech stack, conventions, critical gotchas, and top unblocked tasks).gitmem_remember: Records an architectural decision, lesson, or preference.gitmem_recall: Fuzzy-searches past decisions and gotchas to avoid repeating mistakes.gitmem_task_create: Adds a task with dependency tracking (blockedBy: ["task-1"]).gitmem_task_claim: Claims a task for the active agent session.gitmem_task_complete: Marks task complete and automatically unblocks downstream tasks.gitmem_task_list: Queries tasks (e.g.--readyfor unblocked tasks only).
š» CLI Usage
You can also use gitmem directly from your terminal:
Remember a Decision
npx gitmem remember "Use Argon2 for password hashing" \
--category decision \
--message "Argon2id is memory-hard and prevents ASIC/GPU attacks." \
--tags auth securityRecall Memories
npx gitmem recall "password"Manage Task Dependency Graph
# 1. Create root task
npx gitmem tasks create "Design database schema" --priority high
# 2. Create dependent task (blocked by task-1)
npx gitmem tasks create "Build authentication API" --blocked-by task-1
# 3. View task board
npx gitmem tasks list
# 4. Complete root task (unblocks task-2)
npx gitmem tasks done task-1 --outcome "Prisma schema created"Instant Agent Bootstrap
# Dump formatted project context to terminal or clipboard
npx gitmem contextš Repository Layout
Everything is stored inside your repository under .gitmem/:
your-repo/
āāā .gitmem/
ā āāā config.json # gitmem settings (auto-commit, prefix)
ā āāā memories.json # Structured decisions, lessons, context
ā āāā MEMORIES.md # Auto-generated human-readable memory log
ā āāā tasks.json # Dependency graph (blockedBy, claimedBy)
ā āāā TASKS.md # Auto-generated markdown task board
ā āāā context.json # Stack, conventions & non-negotiablesBecause it lives in git:
Branch-aware: Branches keep their own context or inherit from main.
Team-shared: Every
git pullupdates your local agent's memory.Reviewable: You can see every AI agent decision in standard GitHub pull requests!
š License
MIT Ā© KuraPiee ā Built with ā¤ļø by the Docwyrm Team.
This server cannot be deployed
Maintenance
Related MCP Connectors
Project memory for coding agents: requirements, decisions, code graph and delivery telemetry.
Shared memory for coding agents. Stop re-explaining your codebase every session.
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
- vibsyncOAuthcom.vibsync
One shared brain for your AI coding agents: team memory, agent Q&A, tasks, and file claims.
Related MCP Servers
- AlicenseAqualityAmaintenanceLocal-first memory layer for AI coding agents ā captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.17235 PyPI799MIT
- FlicenseNot gradedqualityCmaintenanceLocal-first deterministic project memory for AI coding agents, with context packs, decisions, gates, risks, scoped claims and explicit checkpoints in project-owned files.-
- AlicenseAqualityBmaintenanceLocal-first project memory for AI coding agents. Records failed attempts, fragile files, and decisions per repo, and warns the agent via hooks before it repeats a recorded mistake.647 npmMIT
- AlicenseAqualityAmaintenanceA lightweight, Git-backed permanent memory for AI agents.33339MIT