mengram vs io.github.gitmem-dev/gitmem
mengram is a plugin bundle for AI coding tools published by Ali Baizhanov. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.gitmem-dev/gitmem is an MCP server published by gitmem-dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-21. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.gitmem-dev/gitmem | |
|---|---|---|
| Community marketplace alibaizhanov/mengram | Listed Version: 0.1.4 Forks (GitHub): 35 Stars (GitHub): 204 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.2.1 Downloads/month (npm): 1 924 Downloads/week (npm): 133 Forks (GitHub): 1 Stars (GitHub): 9 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.11.2 Downloads/month (npm): 1 924 Downloads/week (npm): 133 Forks (GitHub): 1 Stars (GitHub): 9 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | mengram | io.github.gitmem-dev/gitmem |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 204 (better) | 9 (worse) |
| Forks (GitHub) (differs) | 35 (better) | 1 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mengram.io/mcp) | On your machine (gitmem-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Hooks it runs (differs) | 2 | Not published |
| Parts of the bundle (differs) | 5 | Not a bundle |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/alibaizhanov/mengram | github.com/gitmem-dev/gitmem |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
mengram
Persistent memory for Claude Code that survives /clear, machine switches, and team handoffs. Hosted memory backend with hybrid retrieval (vector + BM25 + RRF), Ebbinghaus temporal decay, and importance weighting. Same memory available across Claude Code, Cursor, Codex, and ChatGPT.
io.github.gitmem-dev/gitmem
Persistent institutional memory for AI coding agents. Memory that compounds.
How to run each
mengram As a Claude Code plugin
/plugin marketplace add alibaizhanov/mengram
/plugin install mengram@mengramio.github.gitmem-dev/gitmem As a local MCP server: npm package
claude mcp add --env "SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>" --transport stdio gitmem -- npx -y gitmem-mcpRequires: SUPABASE_SERVICE_ROLE_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only mengram has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of mengram publish no settings it asks for, so we do not compare settings.
What it can do: mengram · What it can do: io.github.gitmem-dev/gitmem · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.