Ext Ops Panel
Open dashboard
Comparison

Mind Glaive vs io.github.codeledgerECF/codeledger

Mind Glaive is a plugin bundle for AI coding tools published by TheGlitchKing. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.codeledgerECF/codeledger is an MCP server published by codeledgerECF. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-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

Where each is published
MarketplaceMind Glaiveio.github.codeledgerECF/codeledger
Claude Code: claude-plugins-community Listed
Version: 2.0.1
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.10.7
Downloads/month (npm): 4 831
Downloads/week (npm): 1 146
Forks (GitHub): 3
Stars (GitHub): 8
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

Mind Glaive vs io.github.codeledgerECF/codeledger
FactMind Glaiveio.github.codeledgerECF/codeledger
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)8 (better)
Forks (GitHub) (differs)0 (worse)3 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@codeledger/cli)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)11Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/theglitchking/mind-glaivegithub.com/codeledgerecf/codeledger
Changes in the last 7 days00
First seen2026-10-112026-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

Mind Glaive

In its own words, on Claude Code: claude-plugins-community:

Eliminate context rot in Claude Code with intelligent memory hierarchy, auto-learning hooks, and specialized subagents. Uses an 8-layer memory architecture with SessionStart/End hooks that automatically persist and restore context across sessions. Includes an MCP knowledge base, pattern learning from tool usage, and pre-compaction memory compression to keep Claude informed without bloating context.

io.github.codeledgerECF/codeledger

In its own words, on Official MCP Registry:

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

How to run each

Mind Glaive As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install mind-glaive@claude-community

io.github.codeledgerECF/codeledger As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio codeledger -- npx -y @codeledger/cli mcp start

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

Neither one's marketplaces publish the settings it asks for.

What it can do: Mind Glaive · What it can do: io.github.codeledgerECF/codeledger · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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