Memory.fit vs io.github.gitmem-dev/gitmem
Memory.fit is an MCP server published by memory.fit. Marketplaces we read that list it: 1 (Official MCP Registry). 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-11-14. 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 |   Memory.fit |  io.github.gitmem-dev/gitmem |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.2.1 Downloads/month (npm): 884 Downloads/week (npm): 192 Forks (GitHub): 2 Stars (GitHub): 9 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.11.4 Downloads/month (npm): 884 Downloads/week (npm): 192 Forks (GitHub): 2 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 | Memory.fit | io.github.gitmem-dev/gitmem |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 9 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release (differs) | Not published | 2026-11-13 |
| Where it runs (differs) | Remote server (api.memory.fit/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 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/fun-management-srl/memory-fit-mcp | github.com/gitmem-dev/gitmem |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-27 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 15 h ago, requires authentication | 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
Memory.fit
Your training, sleep, recovery and fuel for the AI you use: it reads your week and plans the next.
io.github.gitmem-dev/gitmem
Persistent institutional memory for AI coding agents. Memory that compounds.
How to run each
Memory.fit As a remote MCP server
claude mcp add --transport http memory-fit https://api.memory.fit/mcpio.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 Memory.fit 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 Memory.fit publish no settings it asks for, so we do not compare settings.
What it can do: Memory.fit · What it can do: io.github.gitmem-dev/gitmem · Compare two other plugins
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.