An LLM-maintained wiki in Trilium Notes, built and kept up by Claude: a Claude Code plugin on top of the Trilium Notes MCP server.
PluginsHTML · PythonGitHub @MarceltovOnlineOwner unconfirmed
Have you tried it? One tap is enough. No sign-in needed.
Claude Code plugin: build and maintain an LLM wiki in Trilium Notes (Karpathy's pattern), with schema, templates, graph, review queue and a write lock.
Loading the full README.
Read the full README ↗A Claude Code plugin that builds and maintains an LLM wiki in Trilium Notes, after Karpathy's LLM-wiki pattern: you collect sources, Claude writes interlinked summary, concept, entity and hub pages, answers questions from them and lints them. The rules live in a schema note in your Trilium Notes instance.
[!IMPORTANT] This plugin uses the MCP server built into Trilium Notes 0.106+ (Options → AI / LLM → MCP server). Connect to it with an ETAPI token, or put trilium-mcp-proxy in front of it to sign in with your Trilium Notes password instead (the password never leaves your server). The plugin sets up the connection, but runs neither.
Full documentation: trilium-llm-wiki.marceltov.de
Optional: trilium-recall lets Claude find what the wiki (and the rest of your notes) knows on its own, through a prompt hook and an MCP recall tool. It used to live in this repo, up to 0.4.x.
/plugin marketplace add Marceltov/trilium-llm-wiki
/plugin install trilium-llm-wiki
Then start a new session: Claude offers to connect your Trilium Notes instance if none is configured. Ask it to "set up the LLM wiki" to create the structure.
Want Claude to work with your existing notes rather than build a wiki? That's the Trilium Notes plugin. Both can be installed together and share one connection.
| Path | What it is |
|---|---|
skills/trilium-llm-wiki/ | the wiki skill, schema.html (the default rulebook) and setup.py (creates the structure) |
skills/trilium-manage-instances/ | connects Trilium Notes instances with claude mcp add |
hooks/, scripts/check-trilium-credentials.sh | offers the connection setup once if no instance is configured |
shared/rules.md | rules every skill gets a copy of; scripts/sync-shared.sh copies it |
tests/test_setup.py | runs setup.py twice against a fake ETAPI |
scripts/sync-shared.sh # after editing shared/rules.md
bash scripts/test-check-trilium-credentials.sh
python3 -I tests/test_setup.py
trilium-manage-instances, shared/rules.md and the credential check are copies of the ones in trilium-plugin. Keep them in step when one changes.