Ext Ops Panel
Open dashboard
Comparison

Memory Kernel vs io.github.keshrath/agent-knowledge

Memory Kernel is an MCP server published by Artem362. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.keshrath/agent-knowledge is an MCP server published by keshrath. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). 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
MarketplaceMemory Kernelio.github.keshrath/agent-knowledge
Official MCP Registry Listed
Version: 0.3.2
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen
Listed
Version: 1.9.8
Downloads/month (npm): 1 018
Downloads/week (npm): 201
Forks (GitHub): 2
Stars (GitHub): 18
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 1.9.3
Forks (GitHub): 2
Stars (GitHub): 18
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

Memory Kernel vs io.github.keshrath/agent-knowledge
FactMemory Kernelio.github.keshrath/agent-knowledge
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)3 (worse)18 (better)
Forks (GitHub) (differs)0 (worse)2 (better)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (amormorri-memory-kernel)On your machine (agent-knowledge)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Parts of the bundle (differs)Not a bundle2
Licence (differs)Not statedMIT
Repository (differs)github.com/artem362/memory-kernelgithub.com/keshrath/agent-knowledge
Changes in the last 7 days (differs)02
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

Memory Kernel

In its own words, on Official MCP Registry:

Local-first memory for AI agents: SQLite FTS5, deterministic recall, no vector DB, no cloud.

io.github.keshrath/agent-knowledge

In its own words, on Official MCP Registry:

Cross-session memory for AI agents - knowledge graph, scoring, semantic search

How to run each

Memory Kernel As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio memory-kernel -- uvx amormorri-memory-kernel

io.github.keshrath/agent-knowledge As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio agent-knowledge -- npx -y agent-knowledge

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 io.github.keshrath/agent-knowledge publish no settings it asks for, so we do not compare settings.

What it can do: Memory Kernel · What it can do: io.github.keshrath/agent-knowledge · Compare two other plugins

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