cogni-knowledge vs gknowledge
cogni-knowledge is a plugin bundle for AI coding tools published by Stephan de Haas. Marketplaces we read that list it: 1 (Community GitHub marketplaces). gknowledge is an MCP server published by openapi. 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
| Marketplace |  gknowledge | |
|---|---|---|
| Community marketplace cogni-work/insight-wave | Listed Version: 1.0.125 Forks (GitHub): 2 Stars (GitHub): 13 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.2 Forks (GitHub): 3 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
| Fact | cogni-knowledge | gknowledge |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 13 (worse) | 18 (better) |
| Forks (GitHub) (differs) | 2 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (gknowledge-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 37 | Not a bundle |
| Licence (differs) | Apache-2.0 | Not stated |
| Repository (differs) | github.com/cogni-work/insight-wave | github.com/openapi/gknowledge |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-15 | 2026-10-16 |
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
cogni-knowledge
Wiki-first research that compounds. Binds each run to a wiki knowledge base; future runs read what prior runs filed before hitting the web. v0.1.0 inverted pipeline (plan → curate → fetch → ingest → distill → compose → verify → finalize) with zero-network, citation-consistent claim verification — opt-in live-source resweep via `knowledge-refresh --resweep`. The shallow `knowledge-query` rung is read-only by default and can optionally file its answer back as an un-verified synthesis page via `--file-back`.
gknowledge
Search, read and grow a Karpathy-style LLM wiki of linked Markdown pages, with cited answers.
How to run each
cogni-knowledge As a Claude Code plugin
/plugin marketplace add cogni-work/insight-wave
/plugin install cogni-knowledge@insight-wavegknowledge As a local MCP server: PyPI package
claude mcp add --transport stdio gknowledge -- uvx gknowledge-mcp --init "<YOUR_PROJECT_FOLDER>"Requires: <project_folder>
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: cogni-knowledge · What it can do: gknowledge · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.