Generated banner for LLM Wiki
Generated logo for LLM Wiki

LLM Wiki

Memory server

First committed by lucasastorian

Published in lucasastorian/llmwiki. Publisher page

1,764 GitHub stars

What it is

Open Source Implementation of Karpathy's LLM Wiki. Upload documents, connect your Claude account via MCP, and have it write your wiki !
— the description by lucasastorian

AutoGineer overview, from the brain’s own files

LLM Wiki is a memory system designed to transform scattered research, documents, and web clippings into a structured, AI-maintained second brain. By connecting to Claude via the Model Context Protocol (MCP), the system allows an AI agent to read, write, and organize content within a local or hosted workspace. It supports various file types including PDFs, Office documents, and Markdown, indexing them for search and retrieval. The system emphasizes autonomous maintenance, where scheduled prompts enable the AI to synthesize new information, update existing pages, and manage cross-references, ensuring the knowledge base evolves alongside the user's input.

How it works

Memory model: LLM wiki

AutoGineer overview, from the brain’s own files

The system operates by indexing a designated folder on the user's disk or a cloud-based storage. It uses a background watcher to detect new files, which are processed by a converter service to extract text from formats like PDF, Word, and PowerPoint. These files are stored in a local SQLite index or a remote Postgres database. An MCP server provides Claude with tools to search, read, create, edit, and lint wiki pages. Users can trigger updates manually or via scheduled routines, allowing the AI to read new content and update the wiki's Markdown files accordingly.

Folders
FolderRoleFiles
.githubagent-config2
teststests94
apifolder70
converterfolder20
dockerfolder3
extensionfolder54
mcpfolder31
screenshotsfolder2
sharedfolder2
supabasefolder11
webfolder192

The agent writes

Requirements

Databases: PostgreSQL, SQLite

API keys (by name): AWS_SECRET_ACCESS_KEY, CLOUDFLARE_AUTH_TOKEN, CONVERTER_SECRET, MISTRAL_API_KEY, TURBOPUFFER_API_KEY, VOYAGE_API_KEY

Works with: Claude apps

Set it up

  1. Not scanned by AutoGineerThe author’s README also describes installing it from a clone of its repository. Read its install section: AutoGineer did not scan that path. https://github.com/lucasastorian/llmwiki/blob/4d887e8378237fd4042ccd268a731059b6b87f20/README.md#getting-started
  2. First committed by lucasastorian. Published in lucasastorian/llmwiki. Licence: Apache License 2.0.

Usage

AutoGineer overview, from the brain’s own files

  • Connect Claude via MCP to enable autonomous wiki maintenance.
  • Clip web pages and PDFs using the browser extension to save highlights and comments.
  • Upload documents directly to the workspace folder for indexing.
  • Use scheduled routines to have the AI synthesize new content into the wiki.
  • Navigate the wiki and visualize concept relationships via the web interface.
  • Edit wiki pages manually using any text editor while keeping them in sync with the index.
“Read the guide, then ingest my sources and start building the wiki.”
Claude initializes the workspace, reads the available documents, and begins generating or updating wiki pages.
“Find everything added to the workspace since your last run and update the wiki.”
The AI identifies new clips, notes, or files and integrates them into existing wiki pages with updated citations.

Documentation by lucasastorian

LLM Wiki

An autonomous, self-maintaining personal Wikipedia built and maintained by AI.

Image: License

</div>

LLM Wiki transforms your scattered reading and research into a persistent, AI-maintained second brain. Capture documents, notes, and web clippings as you work, and deploy a nightly Claude Routine to autonomously synthesize those sources into a permanent knowledge base. Because the clipper captures your highlights and margin notes alongside the source, the wiki becomes a record of not just what you read but what you thought about it — one that compounds over months and years, long after the original context would have faded. This architecture is heavily inspired by Andrej Karpathy's LLM Wiki concept, with an increased emphasis on autonomous maintenance.

<p align="center"> <img src="wiki-page.png" alt="LLM Wiki — a compiled wiki page with citations and table of contents" width="820" /> </p>

LLM Wiki is designed to work at three distinct scales:

  • For you — a personal Wikipedia of what you've read that you don't have to remember to update.

  • For your AI — a context layer for LLMs to apply your own mental models when working with you.

  • For your organization — most organizations have poor institutional memory, because know-how generally lives in people's heads. We hope companies will consider adopting this model to build a self-maintaining institutional knowledge layer.

Features

  • Connect via MCP Connect Claude.ai, Claude Cowork, Claude Code, or Codex (or any other MCP-compatible app)

  • A Chrome extension Clip webpages and PDFs as you read, highlight key sections, and leave comments that Claude can see over MCP.

  • Uploads Markdown, PowerPoint, PDFs, Word documents, and more.

  • A clean Next.js web app to navigate your own wikipedia — and view the underlying sources.

  • Native cross-linking between wiki pages, and back to the sources they came from.

  • A graph viewer to see how your concepts and entities relate.

  • Visualizations — Charts and other visualizations, including SVGs and Mermaid diagrams.

Getting started

LLM Wiki supports two modes: remote & local. You can self-host the remote app, or try it out for free at llmwiki.app. Or you can git clone the repository, and use the CLI to get started.

Here's how to get started locally.

Requirements: Python 3.11+, Node.js 20+. Optional: LibreOffice to extract Word/PowerPoint files, and a MISTRAL_API_KEY for higher-quality PDF OCR.

1. Install. Clone the repo and install the Python and web dependencies.

macOS / Linux:

git clone https://github.com/lucasastorian/llmwiki.git
cd llmwiki
python -m venv .venv && source .venv/bin/activate
pip install -r api/requirements.txt -r mcp/requirements.txt
cd web && npm install && cd ..

Windows (PowerShell):

git clone https://github.com/lucasastorian/llmwiki.git
cd llmwiki
python -m venv .venv
.venv\Scripts\Activate.ps1
pip install -r api/requirements.txt -r mcp/requirements.txt
cd web; npm install; cd ..

If activation is blocked by your execution policy, run Set-ExecutionPolicy -Scope CurrentUser RemoteSigned once, or skip activation and use .venv\Scripts\python in place of python below.

2. Point it at a folder of your files — PDFs, Word documents, PowerPoints, Markdown, notes. Use any folder on your disk (it does not go inside this repo): the one that already holds your documents, or a fresh empty one. LLM Wiki indexes it into a local search index so the files show up in the app and Claude can read them. It never moves, modifies, or uploads your files — the only things it adds are a wiki/ folder for generated pages and a hidden .llmwiki/ index (see What happens on disk).

./llmwiki open ~/research                     # macOS / Linux
python llmwiki open C:\Users\you\research     # Windows

This initializes the workspace, indexes the folder, starts the API and web app, and opens localhost:3000. Local mode is intentionally loopback-only: the API listens on 127.0.0.1 and does not support LAN or remote binding.

To preview the hosted onboarding UX locally without authentication or API writes, start the web app with the development-only preview flag and open localhost:3000/onboarding:

cd web
NEXT_PUBLIC_ONBOARDING_PREVIEW=true npm run dev

Restart the development server after changing this flag. The preview simulates creation and completion in memory; it does not create a wiki or change onboarding state.

3. Connect Claude over MCP. MCP enables Claude to read, write, and search your wiki.

./llmwiki mcp-config ~/research                     # macOS / Linux
python llmwiki mcp-config C:\Users\you\research     # Windows

Paste the printed JSON into claude_desktop_config.json (Claude Desktop) or .claude/settings.json (Claude Code). One workspace is one MCP server entry, so add one per folder. Then tell Claude: "Read the guide, then ingest my sources and start building the wiki."

4. Make it self-maintaining. Set up a Claude Routine — a scheduled prompt that runs on its own — so Claude refreshes the wiki without you having to remember to. Each run, it reads whatever's new in the workspace since last time (uploads, notes, and clips and highlights from the Chrome extension) and updates the pages those sources touch. You curate the sources; the wiki keeps itself current.

A routine prompt that works well:

Read the guide. Find everything added to the workspace since your last run — new sources, clips, and highlights. For each one, read it and update the wiki: write new pages where they're warranted, fold new material into existing pages, and fix any cross-references or citations it affects.

Then schedule that prompt to run nightly. Claude Code Routines run it on Anthropic's cloud on a fixed cadence even when your laptop is closed — create one at claude.ai/code/routines, with /schedule in the CLI, or from Claude Cowork — while a Desktop scheduled task runs the same prompt on your own machine. Either way the wiki compounds: a year from now you can open it and read back the ideas you were working through a year ago.

Adding content

There are two ways to get material into your wiki.

Upload. Drag files into the web app, or just drop them into the workspace folder — the background watcher picks them up and indexes them. Markdown, PDF, Word, PowerPoint, Excel, images, and more. Each file becomes searchable and readable by Claude.

Chrome extension. Clip web pages and PDFs as you read, highlight the parts that matter, and leave comments. Everything you save lands in the same workspace, and your highlights and notes are visible to Claude over MCP — so a nightly routine can fold them into the wiki on its own.

Install from the Chrome Web Store →

The extension works in both modes. By default it talks to the hosted app; flip the toggle to Local and it points at your running workspace at http://localhost:8000 — so anything you clip while ./llmwiki open is running goes straight into your local wiki. Pick a destination folder (default /webclipper/) and start saving.

Supported files

TypeFormatsHow it's handled
PDF.pdfText and figures extracted locally. Set MISTRAL_API_KEY for higher-quality OCR on tables and complex layouts.
Office.docx .doc .pptx .pptConverted with LibreOffice, then extracted — requires a local LibreOffice install.
Spreadsheets.xlsx .xlsExtracted sheet by sheet.
Web pages.html .htmCleaned to readable Markdown, stripping nav and ads.
Text & data.md .txt .csv .json .xml .yaml .svg, and moreIndexed and chunked directly.
Images.png .jpg .webp .gifStored and viewable inline; Claude can read them when asked.

What happens on disk

LLM Wiki adds exactly two things to the folder you point it at. Your source files are never moved, modified, or uploaded — they stay exactly where they are.

~/research/                  # your files, untouched
  papers/paper.pdf
  notes.md
  data.xlsx
  wiki/                      # generated pages — created by LLM Wiki
    overview.md
    concepts/
      attention.md
  .llmwiki/                  # index + cache — hidden, rebuildable
    index.db
    cache/
  • wiki/ holds ordinary Markdown files. Claude writes and updates them over MCP, but they're just files — open them in any editor, commit them to git, edit them by hand.

  • .llmwiki/ holds the SQLite index (index.db) and extracted artifacts (cache/). Search can be rebuilt from your files with ./llmwiki reindex ~/research, but highlights, comments, agent replies, course progress and clip metadata live only in index.db — back it up, and don't delete it. reindex saves a timestamped copy before rebuilding.

The filesystem is the source of truth; the index just makes it fast to search. A background watcher notices changes you make outside the app and re-indexes them, so editing a wiki page in your own editor stays in sync.

What Claude can do

Once connected over MCP, Claude works the wiki through a small, deliberate set of tools — the same set in local and hosted mode:

ToolWhat it does
guideOrients Claude — how the vault works and which knowledge bases exist. It calls this first.
create_knowledge_baseCreates a knowledge base and starter overview.md; local mode returns the existing singleton workspace.
list_knowledge_basesLists your knowledge bases and their slugs (every other tool takes one).
searchBrowse files, full-text search across content, or query the citation graph — what cites what, plus stale or uncited pages.
readRead documents — a single file or a glob batch, PDF/office page ranges, optionally with embedded images.
createCreate a wiki page, note, or asset (SVG diagram, CSV) with footnote citations back to sources.
editFind-and-replace exact text in an existing page.
appendAdd content to the end of a page.
deleteRemove pages or sources by path or glob (overview.md and any legacy log.md are protected).
lintDeterministic hygiene checks — citation resolution, dangling links, orphan and stale pages, frontmatter consistency.

Writes go to the source of truth first — a file on disk in local mode, Postgres in hosted mode — then the search index updates. So when Claude creates /wiki/concepts/attention.md, it's a real file (or row) immediately, not a pending change.

Architecture

Three kinds of client reach the workspace, through two entry services, over one storage abstraction:

  Claude  ──MCP──►  MCP server ─┐
                                │                local mode  →  SQLite + your filesystem
  Web app ──HTTP─►  API ────────┼──►  VaultFS  ─┤
                                │                hosted mode →  Postgres + S3
  Chrome  ──HTTP─►  API ────────┘
                      └──►  Converter  (PDF / Office text extraction)

VaultFS is the seam: the same wiki operations run against a SQLite-plus-filesystem backend locally or a Postgres-plus-S3 backend when hosted, so Claude's tools behave identically either way. The MCP server speaks to Claude; the API serves the web app and the Chrome extension; the converter handles heavier PDF and Office extraction. Whatever the backend, the durable store is the source of truth and the search index is derived from it.

What's next

Today you add content two ways: upload, or the Chrome extension. The wiki is only as good as what reaches it, so the roadmap is mostly about widening that funnel — more channels for capturing what you read, write, and discuss:

  • Slack — save messages and threads, and ask the wiki questions, without leaving Slack. This is the natural channel for the institutional-memory case: most of what an organization knows is already flowing through chat.

  • Granola — pull in your meeting notes automatically, so the conversations you have become part of your memory alongside the things you read.

  • Email / forward-to-save — a dedicated address you forward articles, newsletters, and notes to; they land in the workspace and the nightly routine folds them in.

  • Public ingest API + webhooks — a documented endpoint so scripts and other tools can push content into a workspace programmatically, plus a Zapier integration to wire up the apps you already use without writing code.

The throughline: capture should meet you wherever you already read and think, and the wiki keeps itself current from there.

License

Apache 2.0 — see LICENSE.

LICENSE

Shown as plain text.


                                 Apache License
                           Version 2.0, January 2004
                        http://www.apache.org/licenses/

   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION

   1. Definitions.

      "License" shall mean the terms and conditions for use, reproduction,
      and distribution as defined by Sections 1 through 9 of this document.

      "Licensor" shall mean the copyright owner or entity authorized by
      the copyright owner that is granting the License.

      "Legal Entity" shall mean the union of the acting entity and all
      other entities that control, are controlled by, or are under common
      control with that entity. For the purposes of this definition,
      "control" means (i) the power, direct or indirect, to cause the
      direction or management of such entity, whether by contract or
      otherwise, or (ii) ownership of fifty percent (50%) or more of the
      outstanding shares, or (iii) beneficial ownership of such entity.

      "You" (or "Your") shall mean an individual or Legal Entity
      exercising permissions granted by this License.

      "Source" form shall mean the preferred form for making modifications,
      including but not limited to software source code, documentation
      source, and configuration files.

      "Object" form shall mean any form resulting from mechanical
      transformation or translation of a Source form, including but
      not limited to compiled object code, generated documentation,
      and conversions to other media types.

      "Work" shall mean the work of authorship, whether in Source or
      Object form, made available under the License, as indicated by a
      copyright notice that is included in or attached to the work
      (an example is provided in the Appendix below).

      "Derivative Works" shall mean any work, whether in Source or Object
      form, that is based on (or derived from) the Work and for which the
      editorial revisions, annotations, elaborations, or other modifications
      represent, as a whole, an original work of authorship. For the purposes
      of this License, Derivative Works shall not include works that remain
      separable from, or merely link (or bind by name) to the interfaces of,
      the Work and Derivative Works thereof.

      "Contribution" shall mean any work of authorship, including
      the original version of the Work and any modifications or additions
      to that Work or Derivative Works thereof, that is intentionally
      submitted to Licensor for inclusion in the Work by the copyright owner
      or by an individual or Legal Entity authorized to submit on behalf of
      the copyright owner. For the purposes of this definition, "submitted"
      means any form of electronic, verbal, or written communication sent
      to the Licensor or its representatives, including but not limited to
      communication on electronic mailing lists, source code control systems,
      and issue tracking systems that are managed by, or on behalf of, the
      Licensor for the purpose of discussing and improving the Work, but
      excluding communication that is conspicuously marked or otherwise
      designated in writing by the copyright owner as "Not a Contribution."

      "Contributor" shall mean Licensor and any individual or Legal Entity
      on behalf of whom a Contribution has been received by Licensor and
      subsequently incorporated within the Work.

   2. Grant of Copyright License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      copyright license to reproduce, prepare Derivative Works of,
      publicly display, publicly perform, sublicense, and distribute the
      Work and such Derivative Works in Source or Object form.

   3. Grant of Patent License. Subject to the terms and conditions of
      this License, each Contributor hereby grants to You a perpetual,
      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
      (except as stated in this section) patent license to make, have made,
      use, offer to sell, sell, import, and otherwise transfer the Work,
      where such license applies only to those patent claims licensable
      by such Contributor that are necessarily infringed by their
      Contribution(s) alone or by combination of their Contribution(s)
      with the Work to which such Contribution(s) was submitted. If You
      institute patent litigation against any entity (including a
      cross-claim or counterclaim in a lawsuit) alleging that the Work
      or a Contribution incorporated within the Work constitutes direct
      or contributory patent infringement, then any patent licenses
      granted to You under this License for that Work shall terminate
      as of the date such litigation is filed.

   4. Redistribution. You may reproduce and distribute copies of the
      Work or Derivative Works thereof in any medium, with or without
      modifications, and in Source or Object form, provided that You
      meet the following conditions:

      (a) You must give any other recipients of the Work or
          Derivative Works a copy of this License; and

      (b) You must cause any modified files to carry prominent notices
          stating that You changed the files; and

      (c) You must retain, in the Source form of any Derivative Works
          that You distribute, all copyright, patent, trademark, and
          attribution notices from the Source form of the Work,
          excluding those notices that do not pertain to any part of
          the Derivative Works; and

      (d) If the Work includes a "NOTICE" text file as part of its
          distribution, then any Derivative Works that You distribute must
          include a readable copy of the attribution notices contained
          within such NOTICE file, excluding those notices that do not
          pertain to any part of the Derivative Works, in at least one
          of the following places: within a NOTICE text file distributed
          as part of the Derivative Works; within the Source form or
          documentation, if provided along with the Derivative Works; or,
          within a display generated by the Derivative Works, if and
          wherever such third-party notices normally appear. The contents
          of the NOTICE file are for informational purposes only and
          do not modify the License. You may add Your own attribution
          notices within Derivative Works that You distribute, alongside
          or as an addendum to the NOTICE text from the Work, provided
          that such additional attribution notices cannot be construed
          as modifying the License.

      You may add Your own copyright statement to Your modifications and
      may provide additional or different license terms and conditions
      for use, reproduction, or distribution of Your modifications, or
      for any such Derivative Works as a whole, provided Your use,
      reproduction, and distribution of the Work otherwise complies with
      the conditions stated in this License.

   5. Submission of Contributions. Unless You explicitly state otherwise,
      any Contribution intentionally submitted for inclusion in the Work
      by You to the Licensor shall be under the terms and conditions of
      this License, without any additional terms or conditions.
      Notwithstanding the above, nothing herein shall supersede or modify
      the terms of any separate license agreement you may have executed
      with Licensor regarding such Contributions.

   6. Trademarks. This License does not grant permission to use the trade
      names, trademarks, service marks, or product names of the Licensor,
      except as required for reasonable and customary use in describing the
      origin of the Work and reproducing the content of the NOTICE file.

   7. Disclaimer of Warranty. Unless required by applicable law or
      agreed to in writing, Licensor provides the Work (and each
      Contributor provides its Contributions) on an "AS IS" BASIS,
      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
      implied, including, without limitation, any warranties or conditions
      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
      PARTICULAR PURPOSE. You are solely responsible for determining the
      appropriateness of using or redistributing the Work and assume any
      risks associated with Your exercise of permissions under this License.

   8. Limitation of Liability. In no event and under no legal theory,
      whether in tort (including negligence), contract, or otherwise,
      unless required by applicable law (such as deliberate and grossly
      negligent acts) or agreed to in writing, shall any Contributor be
      liable to You for damages, including any direct, indirect, special,
      incidental, or consequential damages of any character arising as a
      result of this License or out of the use or inability to use the
      Work (including but not limited to damages for loss of goodwill,
      work stoppage, computer failure or malfunction, or any and all
      other commercial damages or losses), even if such Contributor
      has been advised of the possibility of such damages.

   9. Accepting Warranty or Additional Liability. While redistributing
      the Work or Derivative Works thereof, You may choose to offer,
      and charge a fee for, acceptance of support, warranty, indemnity,
      or other liability obligations and/or rights consistent with this
      License. However, in accepting such obligations, You may act only
      on Your own behalf and on Your sole responsibility, not on behalf
      of any other Contributor, and only if You agree to indemnify,
      defend, and hold each Contributor harmless for any liability
      incurred by, or claims asserted against, such Contributor by reason
      of your accepting any such warranty or additional liability.

   END OF TERMS AND CONDITIONS

   APPENDIX: How to apply the Apache License to your work.

      To apply the Apache License to your work, attach the following
      boilerplate notice, with the fields enclosed by brackets "[]"
      replaced with your own identifying information. (Don't include
      the brackets!)  The text should be enclosed in the appropriate
      comment syntax for the file format. We also recommend that a
      file or class name and description of purpose be included on the
      same "printed page" as the copyright notice for easier
      identification within third-party archives.

   Copyright [yyyy] [name of copyright owner]

   Licensed under the Apache License, Version 2.0 (the "License");
   you may not use this file except in compliance with the License.
   You may obtain a copy of the License at

       http://www.apache.org/licenses/LICENSE-2.0

   Unless required by applicable law or agreed to in writing, software
   distributed under the License is distributed on an "AS IS" BASIS,
   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
   See the License for the specific language governing permissions and
   limitations under the License.
495 files · 492 not served here

Advantages

  • Maintains a persistent record of both source material and user thoughts through highlighted notes. evidence: README.md
  • Supports autonomous updates through scheduled prompts, reducing the need for manual maintenance. evidence: README.md
  • Uses standard Markdown files as the source of truth, allowing for manual edits and portability. evidence: README.md

Limitations

  • Local mode is restricted to loopback-only connections and does not support remote or LAN binding. evidence: README.md
  • Requires external dependencies like LibreOffice for processing certain document formats. evidence: README.md
  • Metadata such as agent replies and clip history are stored in the index and require manual backup. evidence: README.md

Security

Risk level: No risk found

This brain runs

This brain runs nothing: AutoGineer found no hooks, scripts, plugin code or MCP servers in its files.

Attribution and licence

First committed by
GitHub avatar of lucasastorianlucasastorian
Publisher
Lucas Astorian (Community)
Source
lucasastorian/llmwiki · commit 4d887e8
Licence
Apache License 2.0 (files served here)
  • ATTRIBUTION.md (written by AutoGineer)
Synced
Contributors
lucasastorian, LeoStehlik, YoheiTak

AutoGineer is not affiliated with or endorsed by lucasastorian.

Install from source

492 of its files are not served here, so there is no ZIP. lucasastorian/llmwiki at 4d887e8