Ext Ops Panel
Open dashboard
Comparison

thinking-habit vs io.github.gitmem-dev/gitmem

thinking-habit is a plugin bundle for AI coding tools published by fullo. 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-20. 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

Where each is published
Marketplacethinking-habitio.github.gitmem-dev/gitmem
Community marketplace fullo/claude-plugins-marketplace Not seen in the last pass
Version: not stated
Forks (GitHub): 0
Stars (GitHub): 3
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

thinking-habit vs io.github.gitmem-dev/gitmem
Factthinking-habitio.github.gitmem-dev/gitmem
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)3 (worse)9 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (gitmem-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)3Not a bundle
Licence (differs)Not statedMIT
Repository (differs)github.com/fullo/claude-thinking-habitgithub.com/gitmem-dev/gitmem
Changes in the last 7 days (differs)20
First seen (differs)2026-10-192026-10-11

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

thinking-habit

In its own words, on Community GitHub marketplaces:

Cognitive thinking profiler — discovers how you think across 5 dimensions (channel, strategy, direction, medium, logic), translates prompts to match your style, and bridges communication between different cognitive profiles.

io.github.gitmem-dev/gitmem

In its own words, on Official MCP Registry:

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

How to run each

thinking-habit As a Claude Code plugin

Claude Code
/plugin marketplace add fullo/claude-plugins-marketplace
/plugin install thinking-habit@fullo-plugins

io.github.gitmem-dev/gitmem As a local MCP server: npm package

Claude Code
claude mcp add --env "SUPABASE_SERVICE_ROLE_KEY=<YOUR_SUPABASE_SERVICE_ROLE_KEY>" --transport stdio gitmem -- npx -y gitmem-mcp

Requires: SUPABASE_SERVICE_ROLE_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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 thinking-habit publish no settings it asks for, so we do not compare settings.

What it can do: thinking-habit · 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.

Where the data comes from: how the catalog is built