
gknowledge
io.github.openapiPublished by GitHub account openapiv0.3.0Updated Nov 2, 2026
Search, read and grow a Karpathy-style LLM wiki of linked Markdown pages, with cited answers.
Overview
MCP server for a local Markdown knowledge wiki, letting an assistant search, read, query and grow linked pages with citations.
- What you can do
- Search and list wiki pages by keyword or type
- Read a page together with its sources and backlinks
- Ask questions answered from the wiki with citations, optionally saved back
- Import and ingest a file as a new source
- Check recent activity to see what changed
- When to use it
- Useful when you keep a gknowledge project folder of Markdown notes and want Claude Code, Codex, Cursor or another agent to work against that same wiki instead of re-reading raw documents. Suited to incremental, cited knowledge building over documents you own.
- Requirements
- Runs as a local stdio process started with uvx from the gknowledge-mcp PyPI package, pointed at a project folder path. The desktop app is Linux/GNOME-oriented; the README installs it via APT or Flatpak. No API key is needed for the offline engine; a model provider is optional.
Installation
In SourceWeft
- Open gknowledge in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
gknowledge
English · 简体中文 · Italiano · Français · Português (BR) · Español
Karpathy's LLM Wiki as a native GNOME app.
Drop in your documents. Get a linked wiki that an LLM keeps up to date.
A native GNOME app. Offline by default, plain Markdown on disk, Obsidian-compatible.
Bring your own brain: a local model, any OpenAI-compatible endpoint, or your own ChatGPT plan.
[License: MIT] [GTK 4] [Libadwaita] [Ubuntu 24.04+]
[CI] [Stars] [Issues] [Last commit] [Latest release] [Python 3.10+] [Offline first] [No API key needed] [Obsidian compatible] [Karpathy LLM Wiki pattern] [Sign in with ChatGPT] [Ollama] [Flatpak] [PRs welcome]
Real output of the offline engine on six AI papers (data/demo/papers), no API key.
Regenerate with make demo-svg.
Install
One line, on Ubuntu 24.04+ and Debian 13+. It adds the signed gknowledge APT repository, so updates arrive with apt upgrade (other distributions get a per-user install):
Or add the APT repository yourself. apt also pulls GTK 4, Libadwaita and PyGObject:
On any distribution, with Flatpak (the GNOME runtime comes from Flathub):
Both repositories are described at openapi.github.io/gknowledge.
Then open gknowledge from the app grid. To remove it: sudo apt remove gknowledge (or flatpak uninstall io.github.openapi.Gknowledge).
Other distributions, from source, and release builds
- Fedora, Arch and others: install PyGObject, GTK 4 and Libadwaita with your package manager, then run the one-line installer above. It installs into
~/.localwithout root. - From source:
git clone https://github.com/openapi/gknowledge && cd gknowledge && make install. - Single files: every version's
.deband Flatpak bundle is on the Releases page, e.g.sudo apt install ./gknowledge_all.debafter downloading gknowledge_all.deb.
Why gknowledge
If you have used LLM Wiki, Tolaria, OpenKnowledge, Reor or Khoj, you already know the loop: ingest sources, let the model build and maintain a wiki, then ask questions against it. gknowledge does the same thing as a real GNOME application.
- Native, not a web view. GTK 4 and Libadwaita, built to follow the GNOME HIG. No Electron, no Tauri, no browser engine.
- Works with no account. A built-in heuristic engine ingests and answers offline. Add a model when you want better synthesis.
- Your data stays yours. Markdown with YAML frontmatter plus a readable SQLite index. Open the folder in Obsidian or any editor.
- Cited, reviewable, incremental. Every generated page records its sources, answers cite pages, and a review queue keeps you in control.
The workflow you already know
See ROADMAP.md for dates and TODO.md for the backlog.
Karpathy's LLM Wiki, native on GNOME
In April 2026 Andrej Karpathy described the LLM Wiki pattern: instead of re-reading raw documents on every question, an LLM builds and maintains a persistent wiki that compounds over time. gknowledge implements it as a desktop app.
What we kept
- Three layers: immutable
sources/, the generatedknowledge/wiki, and settings that tell the engine how to work. - The operations: ingest (read a source, update the pages it touches) and query (answer from the wiki, with citations). Lint is next.
index.mdas the catalogue andlog.mdas the append-only history.- Plain Markdown with
[[wikilinks]]and YAML frontmatter, so the folder opens in Obsidian. - The human curates, the model maintains.
What we changed and added
- A native app instead of an idea file. GTK 4 and Libadwaita, with sources, wiki, assistant and review in one window.
- Works with no model at all. An offline engine ingests and answers; a model makes it better.
- Bring your own brain. Your ChatGPT plan through Sign in with ChatGPT, Ollama, or any OpenAI-compatible endpoint.
- Two-step ingest with provenance. Analysis first, then pages; every page records its sources.
- No empty pages, no duplicates. Pages are created only with real content, names are merged across sources ("Kasparov" and "Garry Kasparov"), minor names stay as mentions until a second source cites them.
- A review queue for what the model is unsure about.
- An MCP server, so Claude Code, Codex or Cursor can search, read and grow the same wiki.
Use your wiki from Claude Code, Codex or Cursor
gknowledge ships an MCP server. Point any agent at a project folder:
For Cursor or other clients, add this to the MCP configuration:
Try it from source
make start also restarts the app whenever you edit the source, which makes it the fastest way to hack on gknowledge. Install it for daily use with make install.
Bring your own brain
Nothing is sent anywhere unless you pick a provider that is not offline.
How it compares
Details and history of each project are in DISTRIBUTING.md.
gknowledge is an alternative to…
gknowledge sits at the intersection of LLM-powered knowledge bases, local-first note tools, and document RAG systems. If you have used any of the tools below, you already understand the shape of the problem — gknowledge addresses it as a native GNOME/GTK application that is local-first, provider-agnostic, and usable fully offline (no API key required, thanks to a built-in heuristic extraction engine).
LLM wiki / auto-knowledge-base builders (the closest peers, several studied in NOTES.md):
- LLM Wiki (
nashsu/llm_wiki) — Tauri desktop app implementing Karpathy's incremental "LLM builds and maintains a wiki" pattern - Tolaria — files-first, git-first Markdown knowledge base with AI-assisted editing
- WeKnora (Tencent) — enterprise RAG + agents + auto-wiki framework
- OpenKnowledge (Inkeep) — WYSIWYG Markdown editor with agent/MCP integrations for LLM wikis
- Reor — local-first AI note-taking that auto-links related notes
- Khoj — self-hostable AI "second brain" over your documents
Not a peer: Google NotebookLM offers a similar cited-notebook experience but is closed-source and cloud-only.
Document RAG / "chat with your knowledge" engines:
Local-first / networked-thought note tools (which gknowledge complements with automated ingestion and provenance):
- Obsidian (+ Smart Connections / Copilot plugins), Logseq, SiYuan, Trilium Notes, Zettlr, Foam, Dendron, Joplin, Notion, Tana, Capacities, Heptabase, RemNote
Document / reference managers with growing AI features:
How gknowledge differs
- Native to GNOME, not Electron/Tauri or web-first — GTK 4 + Libadwaita, HIG-aligned, Flatpak-friendly.
- Offline-first and provider-agnostic — a local heuristic engine ships in the box; OpenAI-compatible endpoints (OpenAI, Ollama, LM Studio, vLLM, OpenRouter, …) are optional, swappable, and configured per project.
- Inspectable, user-owned format — knowledge is plain Markdown with YAML frontmatter (Obsidian-compatible) plus a readable SQLite index; nothing is locked behind a sync service.
- Incremental, not stateless RAG — sources are ingested once into a persistent, cross-linked knowledge space with provenance, rather than re-retrieved from scratch on every question.
- Human-in-the-loop — generated content is clearly marked and a review queue keeps you in editorial control.
Project docs
ROADMAP.md— milestones and the features we are borrowing from peersTODO.md— actionable backlogDISTRIBUTING.md— positioning and distribution study of comparable projects (Italian)CONTRIBUTING.md— how to contributedocs/DESIGN.md— the original product and design documentCHANGELOG.md— what changed in each release
License
MIT. Contributions are welcome, see CONTRIBUTING.md.
Star history
[Star history]If gknowledge is useful to you, a star helps other GNOME users find it.
Source: README.md at commit d946b2f
Tools
0Version history
2- v0.3.0LatestOct 19, 2026
- v0.2.2Oct 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
