AutoRAG Lite setup

Use this skill only to bootstrap, register, or repair AutoRAG Lite MCP: initialize trusted config, connect the host, build indexes, and verify search. Normal Lite use is MCP tool calling, not a search skill or shell command. Use autorag-setup instead when the model-backed librarian must be configured.

Safety

• Inspect only non-secret config metadata: searchPaths, workspacePath, memoryPath, minSync, jikji, datasources.
• Never print, copy, migrate, compare, or persist credential values. Store only environment-variable names such as tokenEnv or apiKeyEnv.
• Setup and Lite commands never move, rename, edit, or delete source documents. They write indexes only under the configured workspace .autorag/ directory and Jikji's central store (<OS data dir>/jikji/).
• Do not index system trees, app bundles, caches, credential stores, node_modules, .git, dist, build, target, .cache, .autorag, or .jikji.

Install the package if needed

@autorag/librarian ships both autorag (bootstrap/maintenance) and autorag-mcp (stdio server). The executable requires Node.js >= 24 on PATH.

command -v autorag-mcp >/dev/null || bun install -g @autorag/librarian
command -v autorag
command -v autorag-mcp
autorag lite --help

If Bun is unavailable, npm install -g @autorag/librarian is acceptable. If only autorag exists, upgrade the package rather than substituting CLI retrieval for MCP. For a source checkout, run bun run build and register the absolute dist/mcp/index.js path instead of the installed executable.

Initialize a model-free config

autorag lite init \
  --search-paths "/path/to/documents,/path/to/notes" \
  --workspace "/path/to/workspace" \
  --memory-path "/path/to/memory.json"