
Llm Wiki Mcp
io.github.flsteven87Published by GitHub account flsteven87v0.1.1Updated Oct 24, 2026
MCP server for Karpathy-style LLM wikis: persistent markdown your agent grows over time.
Overview
Local stdio MCP server that gives an assistant a persistent markdown wiki it can read, write, log and inventory over time.
- What you can do
- Read a single wiki page, returning its body, parsed frontmatter, outgoing links and etag
- Create or update pages atomically with etag conflict checks
- Append dated entries to an append-only session log
- Snapshot the whole wiki graph: pages, frontmatter, link edges, log entries and optional mention scans
- Optionally pair with bundled Claude Code skills for init, ingest, query and lint workflows
- When to use it
- Useful when you want an agent to accumulate durable, human-readable notes across sessions instead of losing context, for example a research or topic wiki built from papers and articles. Best suited to Claude Code users who want the guided ingest/query/lint workflow; other clients get only the four tools.
- Requirements
- Runs locally over stdio via uvx from the PyPI package llm-wiki-mcp. Needs Python 3.11+ and uv, plus an absolute path passed as --wiki-root pointing at the curated wiki folder. No accounts, API keys or environment variables are declared. The client must be restarted after configuration.
Installation
In SourceWeft
- Open Llm Wiki Mcp 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
llm-wiki-mcp
Persistent markdown wiki for your AI agent, built on Karpathy's LLM wiki gist. Four MCP tools (wiki_read, wiki_write_page, wiki_log_append, wiki_inventory) plus four Claude Code skills (wiki-init, wiki-ingest, wiki-query, wiki-lint). stdio transport, local filesystem.
The server handles the boring layer LLMs keep getting wrong: atomic writes, etag conflict checks, append-only log integrity, path containment. The skills give the agent a workflow to follow. The wiki schema lives in your own wiki/CLAUDE.md and grows with your domain. There is no Layer 3 schema validation in the server.
Status: alpha (v0.1.1). Local backend only. MIT licensed.
Quick start
Requires Python 3.11+ and uv.
Pick an absolute path for the wiki folder. The server creates pages/ and log.md under it on first run if they don't exist:
Wire it into your MCP client.
Claude Code:
Claude Desktop (~/Library/Application Support/Claude/claude_desktop_config.json on macOS) or Cursor (~/.cursor/mcp.json):
Restart the client. Four tools should appear: wiki_read, wiki_write_page, wiki_log_append, wiki_inventory.
Claude Code skills
Claude Code users can install the bundled workflow skills as a plugin:
Each skill reads wiki/CLAUDE.md for the active schema on every run, so you can evolve the schema without re-installing anything. Ask the agent things like:
wiki-init is a one-shot scaffolder; the other three are Karpathy's three operations.
Other MCP clients (Claude Desktop, Cursor) get the four tools but not the skills. The agent has to derive the workflow from tool descriptions alone, which works for one-off reads and writes but tends to skip the bookkeeping (log entries, backlink audits) the skills make explicit.
The four tools
index.md and raw/ are intentionally not exposed as tools. The index is LLM-curated content edited via the host's Read/Write. The raw layer is immutable from the server's perspective.
Wiki layout
wiki-init scaffolds a project that looks like this:
--wiki-root points at the curated wiki/ folder, not the parent project folder containing raw/. Easy to get wrong on first install; the troubleshooting section below covers the error you'll see.
Design boundary
The server enforces mechanics, not content shape:
- Atomic writes.
tmp-file + fsync + renamefor pages.O_APPENDsingle-write for log entries. - Optimistic concurrency. Every page has an etag (
sha256(body) || mtime_ns). Updates supply the etag they read; a mismatch raisesWikiConflictError, and the agent re-reads, merges, and retries. - Path containment. Slugs are regex-validated. Resolved paths are checked against the realpath of the root, blocking the CVE-2025-53109 symlink-escape class.
- Format-locked log line.
## [YYYY-MM-DD] operation | Title. Operation names are free strings; only characters that would break the line shape are rejected.
The server does not validate frontmatter shape, page categories, or link targets. That layer lives in your wiki/CLAUDE.md schema doc and grows with the LLM. Karpathy's gist is deliberately silent on content shape; baking a schema into the server would defeat the point.
Python API
If you want to wrap the MCP server with your own storage backend (SQLite, Notion, GDrive, a test fake), implement the WikiStorage Protocol and pass an instance to build_server:
build_server is the composition root. The CLI main() is a thin caller that constructs LocalFilesystemStorage from --wiki-root and hands it in.
The bundled Claude Code skills ship as package data under llm_wiki_mcp/skills/ and load via importlib.resources if you want to wire them into a non-Claude-Code agent. Typed domain errors (WikiConflictError, WikiNotFoundError, WikiPermissionError, WikiPathError, WikiSchemaViolationError) are importable from the package root for catching at your own boundary.
Troubleshooting
llm-wiki-mcp: command not found after uv tool install. uv puts the binary in ~/.local/bin (or %USERPROFILE%\.local\bin on Windows). Add it to PATH, or use uvx llm-wiki-mcp ... to invoke without a persistent shim.
wiki_* tools don't appear after editing the client config. Restart the MCP client. Claude Desktop, Claude Code, and Cursor only re-read mcpServers at startup.
WikiPathError: path escapes wiki root. You pointed --wiki-root at the project folder containing raw/ instead of the curated wiki/ folder inside it. /Users/me/wikis/ai-safety/wiki is correct; /Users/me/wikis/ai-safety is not.
Skills not loading in Claude Code. Run claude plugin list. If llm-wiki-skills is missing, rerun the marketplace commands in the Claude Code skills section.
Development
License
MIT. See LICENSE.
Source: README.md at commit 16463f0
Tools
0Version history
1- v0.1.1LatestSep 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