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.
We read the source, 21 h ago · rules 3dff92dd89df
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.
"eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJzdXBhYmFzZSIsInJlZiI6ImNqcHR4eWV6dXhkaWludWZncnJtIiwicm9sZSI6ImFub24iLCJpYXQiOjE3NjYxODY3MDMsImV4cCI6MjA4MTc2MjcwM30.L0oZy3LYCMikmZ15IUU5DnfJmucM37DJ14nUkM3AreY";
return fs.existsSync("/.dockerenv");
path.join(projectsDir, claudeCodeDirName), // Primary: full path with dashes
readdirSync,
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
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.
claude mcp add gitmem -- npx -y gitmem-mcp
{
"mcpServers": {
"gitmem": {
"args": [
"-y",
"gitmem-mcp"
],
"command": "npx"
}
}
}
[mcp_servers.gitmem]
command = "npx"
args = ["-y", "gitmem-mcp"]
{
"mcpServers": {
"gitmem": {
"args": [
"-y",
"gitmem-mcp"
],
"command": "npx"
}
}
}
{
"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.
Local-first persistent memory for AI coding agents.
Persistent, consensus-validated institutional memory for AI agents. Runs locally.
Persistent graph-backed conversational memory for AI agents.
Persistent memory for AI agents: L1/L2/L3, web compression, threads.
Persistent memory for AI coding agents. #1 on LongMemEval. Local-first.
Persistent project memory for AI coding agents: one compact digest instead of re-reading the repo.
Deterministic context selection for AI coding agents. Local memory that compounds across sessions.
Persistent memory layer for AI coding agents — your agent remembers what you taught it.
Answers built from our own checks of this server.