using-axonlisted

# axon axon is a self-hosted RAG engine. Two surfaces, same backend (Spider.rs/Chrome -> Qdrant, SQLite jobs, SearXNG/Tavily for web search): - **MCP (preferred)** — the Axon MCP server exposes a single tool named `axon`; use the host-generated tool name for the current environment. It is routed by `action` (and `subaction` for lifecycle families). Large results are written to a local artifact file under `~/.axon/artifacts/<context>` and the response returns the file `path` plus a compact `shape` summary; small results (≤ ~8 KB) come back inline. See **Response handling (MCP)** below. - **CLI (fallback)** — `axon <command> [flags]`. Use for shell scripting, cron, or when the MCP server is down. This skill leads with MCP request shapes; CLI equivalents are listed alongside. The two surfaces are close but not identical — most notably, `scrape` is a CLI-only one-page projection with no MCP action of its own. ## One pipeline: `source` Every kind of indexing goes through the **unified source pipeline**. There is one entrypoint — a `SourceRequest` — and one job model behind it: ``` SourceRequest → resolve/route → acquire → ledger generation + manifest → prepare → embed → publish → graph → cleanup ``` Axon classifies the input string itself (web URL, local path, git URL, feed URL, YouTube/Reddit target, session selector, registry target) and picks the right adapter. You supply the source and, when the default is wrong, a `scope`. **These action/command families