Ext Ops Panel
Open dashboard
Comparison

Cognee Memory vs knowmind

Cognee Memory is a plugin bundle for AI coding tools published by Cognee. Marketplaces we read that list it: 1 (Community GitHub marketplaces). knowmind is an MCP server published by Schubeler-Consulting. 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

Where each is published
MarketplaceCognee Memoryknowmind
Community marketplace topoteretes/cognee-integrations Listed
Version: 1.8.1
Forks (GitHub): 136
Stars (GitHub): 107
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.4.6
Downloads/month (npm): 1 979
Downloads/week (npm): 445
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 0.4.6
Downloads/month (npm): 1 979
Downloads/week (npm): 445
Forks (GitHub): 0
Stars (GitHub): 0
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

Cognee Memory vs knowmind
FactCognee Memoryknowmind
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)107 (better)0 (worse)
Forks (GitHub) (differs)136 (better)0 (worse)
Last release (differs)2026-11-14 (better)2026-11-01 (worse)
Where it runs (differs)Installs as a plugin bundleOn your machine (knowmind)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Hooks it runs (differs)11Not published
Parts of the bundle (differs)23Not a bundle
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/topoteretes/cognee-integrationsgithub.com/schubeler-consulting/knowmind
Changes in the last 7 days (differs)60
First seen (differs)2026-11-092026-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

Cognee Memory

In its own words, on Community GitHub marketplaces:

Persistent memory for Claude Code, built on Cognee's knowledge graph. Captures your prompts, tool calls and answers, recalls what's relevant on every prompt, and carries decisions and lessons into later sessions. Runs locally or on Cognee Cloud.

knowmind

In its own words, on Official MCP Registry:

AI agent memory & knowledge graph, hosted in Germany (GDPR). Recall, relations, store via MCP.

How to run each

Cognee Memory As a Claude Code plugin

Claude Code
/plugin marketplace add topoteretes/cognee-integrations
/plugin install cognee-memory@cognee

knowmind As a local MCP server: npm package

Claude Code
claude mcp add --env "KNOWMIND_TOKEN=<YOUR_KNOWMIND_TOKEN>" --transport stdio knowmind -- npx -y knowmind mcp

Requires: KNOWMIND_TOKEN (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 Cognee Memory publish no settings it asks for, so we do not compare settings.

What it can do: Cognee Memory · What it can do: knowmind · 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