Build your own personal LLM wiki in 30 seconds. Multi-agent native, MCP-ready, SEO/GEO-optimized publish target.
Inspired by Andrej Karpathy's "LLM Wiki" gist.
This package is one concrete instantiation of that idea — opinionated about agent rules, directory ontology, frontmatter schema, privacy, and the publish pipeline. The idea is Andrej's; the implementation is this project's. Full credit and quoted lineage in .
Build your own local LLM Wiki in 30 seconds. Multi-agent native (Claude/Codex/Cursor/VSCode/Trae), MCP server built-in, Astro static site publishing.
# Interactive
npx create-opc-wiki my-wiki
# Zero-prompt (any agent, any IM, any CI)
npx -y create-opc-wiki@latest ~/wiki --yes --agents=claude,codex,cursor,openclaw,hermes
That's it. Open the generated folder in Obsidian, fire up your AI agent, and start building your second brain.
Quickstart
npx create-opc-wiki my-wiki # interactive prompts
cd my-wiki
# Open in Obsidian: File → Open Vault → this folder
# Or fire up Claude Code / Codex / Cursor and try /wiki-ingest <url>
🌐 SEO + GEO publish target — npm run wiki:publish produces an Astro Starlight site with sitemap.xml, llms.txt, robots.txt, RSS feed, OpenGraph + JSON-LD
🔒 Privacy-first frontmatter — public / private / secret levels; secret never leaves the box, private never publishes
🩺 Epistemic hygiene — confidence: high|medium|speculative with decay reminders for stale speculative claims
📚 Three reusable skills — /wiki-ingest, /wiki-query, /wiki-lint
Install in any AI agent (paste-in recipes)
The scaffolder is fully non-interactive when given --yes. Any agent that can run a shell command can install the wiki for you in one line. Per-agent recipes in docs/INSTALL-FOR-AGENTS.md.
Or grab them all: --agents=claude,codex,cursor,vscode,trae,openclaw,hermes.
How it differs from RAG / NotebookLM / file uploads
Most LLM-on-files setups (NotebookLM, ChatGPT file uploads, raw RAG) re-derive answers from raw documents at every query. There is no accumulation. Quoting the original gist:
Instead of just retrieving from raw documents at query time, the LLM incrementally builds and maintains a persistent wiki — a structured, interlinked collection of markdown files that sits between you and the raw sources. The wiki keeps getting richer with every source you add and every question you ask.
This package operationalizes exactly that, with concrete choices for ontology, agent rules, MCP, and publishing.
Full help: npx create-opc-wiki --help. Semver scope is documented in STABILITY.md.
FAQ
Q: Why a wiki instead of just RAG?
A wiki compiles and reuses synthesis. RAG re-derives it on every query. See INSPIRATION.md for Karpathy's framing.
Q: Does my data leave the machine?
No. The wiki is a local Obsidian vault. The MCP server runs locally over stdio. The static site only publishes pages with privacy: public in frontmatter.
Q: Which agent should I use?
Any of the nine supported. Use --agents=claude,codex,cursor,openclaw,hermes to target several at once and edit agent-rules/main.md once for all of them.
Q: How is "GEO" different from "SEO"?
SEO targets web search (Google, Bing). GEO = Generative Engine Optimization — making your content discoverable to LLM crawlers (ChatGPT, Claude, Perplexity). The published site emits both: sitemap.xml for SEO, llms.txt + structured prose for GEO.
Q: Will this stay stable across upgrades?
Yes — see STABILITY.md. CLI flags, generated file paths, frontmatter schema, and MCP tool signatures are covered by semver. Template prose is not.
Q: Can I use this without npm/Node?
Today, no. The scaffolder runs once via npx; after that the generated wiki is plain markdown and works without Node. The optional MCP server and Astro site need Node 20+.
On the road to OPC
OPC = One Person Company. Thesis: with AI, a single person can run what used to take a team. A maintained second brain is infrastructure for that. This tool is one of the building blocks.
Ainda não há lista de ferramentas. Servidores remotos recebem uma após a primeira verificação de saúde.
Perguntas frequentes
Perguntas
Como instalo Create Opc Wiki?
Copie nesta página a configuração stdio para Cursor, Claude Desktop, Claude Code ou VS Code. Ela usa a instalação do publicador, não um proxy do PlugMCP.
Create Opc Wiki precisa de uma chave de API?
Este registro não lista nenhuma variável de ambiente obrigatória.
Qual transporte Create Opc Wiki usa?
Create Opc Wiki roda localmente via stdio.
Quando Create Opc Wiki foi verificado pela última vez?
Última verificação: 2026-10-28. Build your own local LLM Wiki in 30 seconds. Multi-agent native (Claude/Codex/Cursor/VSCode/Trae), MCP server built-in, Astro static site publishing.