mcpbeat Sign in

Gitmem MCP Server

by gitmem-dev Your server? Claim it
local only

Gitmem runs on your own machine — the client starts it, so there is no endpoint to ping. 113 installs a week from npm. Last commit 9 Aug 2026.

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

Installs per day peak 69 · avg 18 · -60% w/w
a month agotoday
113
Installs / week
npm · gitmem-mcp
9
Stars
0 open issues
9 Aug 2026
Last commit
0 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 21 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

A line of code looks encrypted src/commands/deactivate.ts:23
  "eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImNqcHR4eWV6dXhkaWludWZncnJtIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NjYxODY3MDMsImV4cCI6MjA4MTc2MjcwM30.L0oZy3LYCMikmZ15IUU5DnfJmucM37DJ14nUkM3AreY";
Checks whether it runs in a sandbox src/services/agent-detection.ts:26
    return fs.existsSync("/.dockerenv");
Builds a file path from a variable src/tools/session-close.ts:113
    path.join(projectsDir, claudeCodeDirName),  // Primary: full path with dashes
Reads files and sends them to the network bin/gitmem.js:24, [пакет] bin/gitmem.js:24
  readdirSync,

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add gitmem -- npx -y gitmem-mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "gitmem": {
      "args": [
        "-y",
        "gitmem-mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.gitmem]
command = "npx"
args = ["-y", "gitmem-mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "gitmem": {
      "args": [
        "-y",
        "gitmem-mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "gitmem": {
      "args": [
        "-y",
        "gitmem-mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: SUPABASE_URL (Supabase project URL for pro tier features (semantic search, analytics). Not required for free tier.), SUPABASE_SERVICE_ROLE_KEY (Supabase service role key for pro tier features. Not required for free tier.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Gitmem

same job, measured the same way
PMB AI
by oleksiijko

Local-first persistent memory for AI coding agents.

293 installs/wk local only
Sage
by l33tdawg

Persistent, consensus-validated institutional memory for AI agents. Runs locally.

local only
Waggle MCP
by abhigyan-shekhar

Persistent graph-backed conversational memory for AI agents.

54 installs/wk local only
Vibo MCP
by vnbochkarev-netizen

Persistent memory for AI agents: L1/L2/L3, web compression, threads.

local only
Omega Memory
by omega-memory

Persistent memory for AI coding agents. #1 on LongMemEval. Local-first.

local only
projectmind
by nodemint-dev

Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo.

65 installs/wk local only
Codeledger
by codeledgerecf

Deterministic context selection for AI coding agents. Local memory that compounds across sessions.

435 installs/wk local only
aide-memory
by aide-memory

Persistent memory layer for AI coding agents — your agent remembers what you taught it.

40 installs/wk local only

Gitmem — questions

Answers built from our own checks of this server.

Why is there no uptime for Gitmem?
Gitmem runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package gitmem-mcp was installed 113 times last week.
How do I connect Gitmem?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls gitmem-mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Gitmem?
The npm package gitmem-mcp was installed 113 times in the last week. Week over week that is -60%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Gitmem open source?
Yes — it is published under the MIT licence, written in TypeScript and 9 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.