Ext Ops Panel
Open dashboard
Comparison

Mind Glaive vs io.github.jarmstrong158/context-keeper

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.jarmstrong158/context-keeper is an MCP server published by jarmstrong158. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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.jarmstrong158/context-keeper
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.19.0
Downloads/month (PyPI): 239
Downloads/week (PyPI): 63
Forks (GitHub): 1
Stars (GitHub): 1
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.jarmstrong158/context-keeper
FactMind Glaiveio.github.jarmstrong158/context-keeper
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub) (differs)0 (worse)1 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (context-keeper-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 0
Parts of the bundle (differs)11Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/theglitchking/mind-glaivegithub.com/jarmstrong158/context-keeper
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.jarmstrong158/context-keeper

In its own words, on Official MCP Registry:

Durable project-memory MCP: decisions, constraints, and pipelines across Claude 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.jarmstrong158/context-keeper As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio context-keeper -- uvx context-keeper-mcp

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

What it can do: Mind Glaive · What it can do: io.github.jarmstrong158/context-keeper · 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