autopedia
Enables using the autopedia wiki directory as an Obsidian vault, with wikilinks, graph view, and backlinks working out of the box.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@autopediaadd note: GPU prices dropped"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
autopedia
Personal knowledge wiki maintained by your AI tool via MCP.
Your AI tool (Claude Code, Cursor, etc.) maintains a Karpathy-style wiki through MCP. No separate LLM client. No API keys. Your existing AI tool IS the brain.
Requires Node.js 20+
Get started
1. Install
npm install -g autopedia2. Initialize
autopedia initCreates ~/.autopedia/ with:
wiki/ ← synthesized knowledge (AI-maintained)
sources/ ← raw inputs (URLs, text notes, files)
ops/ ← audit trail (log, metrics, queue)
schema/ ← your profile and rules3. Connect to your AI tool
Add to your AI tool's MCP config (one-time setup):
Claude Code (~/.claude.json):
{
"mcpServers": {
"autopedia": {
"command": "autopedia",
"args": ["serve"]
}
}
}Cursor (.cursor/mcp.json):
{
"mcpServers": {
"autopedia": {
"command": "autopedia",
"args": ["serve"]
}
}
}4. Verify
autopedia status
# Should show: Wiki pages: 1, Queued: 05. Start using it
Start a new Claude Code or Cursor session. On first connection, autopedia interviews you (~30 seconds) to personalize your wiki. After that, it's silent until you need it.
Add stuff anytime (from any terminal):
autopedia add "GPU prices dropped 20% this quarter"
autopedia add https://example.com/article
autopedia add ~/research/notes.mdProcess when ready (tell your AI tool):
You: "sync my wiki"
AI: Processing 1/3: gpu-pricing-note → created gpu-pricing.md
Processing 2/3: example.com/article → updated market-trends.md
Processing 3/3: notes.md → created research-notes.md
Done. Created 2 pages, updated 1.Ask questions anytime:
You: "What do I know about GPU pricing?"
AI: → answers from YOUR research, not training dataautopedia never hijacks your conversation. It's a quiet knowledge layer — there when you need it, invisible when you don't.
Related MCP server: Librarian
CLI Commands
Command | What it does |
| Create |
| Queue a URL, text note, file, folder, or repo |
| Scan a codebase and create an architectural bundle |
| Check wiki health: orphans, stale pages, broken links |
| Remove a wiki page (or source with |
| Detect files added outside autopedia (Obsidian, IDE) and queue them |
| Show wiki stats and unprocessed sources |
| Search wiki pages from the terminal |
| Browse your wiki in a local dashboard |
| Export wiki as a single markdown file |
| Start MCP server (used by AI tools, not run manually) |
Braindump from anywhere
autopedia add "GPU prices dropped 20% this quarter" # text note
autopedia add https://example.com/article # URL
autopedia add ~/research/gpu-report.pdf # file
autopedia add ~/research/ # whole folder
autopedia add ~/code/my-project/ # auto-detect repo (.git/)
autopedia add --repo ~/code/my-project/ # explicit repo modeEverything is saved instantly. Tell your AI tool "sync" to process.
Dashboard
Run autopedia view to open a local dashboard.
Wiki index with rendered markdown and clickable [[wikilinks]]
Knowledge graph — force-directed visualization of page connections
Backlinks — each page shows what links to it
Source browser with content-derived titles
Status — page count, queue, untracked files
Light/dark theme with Newsreader + DM Sans typography
Obsidian integration
Open ~/.autopedia/ as an Obsidian vault. Wikilinks, graph view, and backlinks work out of the box.
Drag-and-drop workflow: Drop files into the vault via Obsidian, then run autopedia scan to queue them. Tell your AI tool "sync" to process.
How it works
Implements Karpathy's three wiki operations:
INGEST — Fetch URLs, save notes, synthesize into wiki pages
QUERY — Search and read, answer grounded in your research
LINT — Find orphans, stale content, contradictions, fix them
MCP Tools (9)
Tool | Operation | Purpose |
| INGEST | Fetch URL or save text (queue or ingest mode) |
| INGEST | Create/update wiki pages |
| QUERY | Read a saved source |
| QUERY | Search wiki pages |
| QUERY | Read a specific page |
| STATUS | Page count, queue, untracked files |
| LINT | Orphans, stale pages, broken links, low crossrefs |
| LINT | Challenge high-confidence claims |
| ONBOARDING | Write identity + interests |
MCP Resources (3)
Resource | What |
| System prompt (auto-updates on upgrade) |
| Your profile |
| What you care about |
Security
Sacred boundary: Server writes only to
wiki/,ops/,sources/agent/. User content is never modified.Path traversal:
path.resolve()+startsWith()+ symlink chain validationSSRF protection: Blocks localhost, private IPs, IPv6, metadata endpoints, redirect bypasses
XSS prevention: All rendered content HTML-escaped, link text escaped, graph JSON escaped
No API keys: Server makes zero LLM calls — your AI tool does all the thinking
Architecture
src/wiki.ts — File I/O, boundary enforcement, wikilink graph, lint, scan
src/mcp.ts — 9 MCP tools + 3 resources
src/cli.ts — CLI: init, add, lint, scan, serve, status, view, search, export, remove
Repo scanner: smart file discovery, role scoring, bundle formatting
src/dashboard.ts — Server-rendered HTML dashboard (graph, backlinks, source titles)
schema/prompt.md — System prompt (served via MCP, auto-updates on upgrade)7 runtime dependencies. No LLM SDK. No database. No Express.
Development
git clone https://github.com/devp1/autopedia
cd autopedia
npm install
npm run build
npm test # 259 tests
npm run typecheck
npm run lintLicense
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/devp1/autopedia'
If you have feedback or need assistance with the MCP directory API, please join our Discord server