Getting Started
AMI in a nutshell.
Reference documentation for the AMI Suite — server, CLI, MCP server, Admin UI, and the Compository document store.
What's here
AsanagiDB ships as one engine plus a small set of tools around it. Start with Installation — the license-activation step is the one that most often trips people up, and it's explained there — then read whichever component you're actually going to talk to.
Installation
Installers for macOS, Linux and Windows — where each one puts binaries, config, data and logs, and how to activate a license against the account the service actually runs as.
AsanagiDB
The graph database server. Gremlin over TinkerPop3 GraphBinary, LMDB-backed, no JVM. Flags and YAML configuration.
AsanagiDB-admin
Command-line administration over the Unix domain socket — integrity checks, GraphSON export/import, and bulk CSV/APOC loading.
AsanagiDB-mcp
The Model Context Protocol server that bridges AI tools to the graph, plus the mTLS federation model behind --central and --public.
AsanagiIDX
Turnkey RESO Web API MLS syndication engine powered by AsanagiDB graph storage, REST endpoints, and client SDK integration.
Admin UI
The native desktop app for browsing and managing a graph: explorer, node management, import and export.
Compository
The document store built into the graph engine — nested objects, ordered arrays, and the newline-delimited JSON wire protocol.
Known Limitations
What AsanagiDB's Gremlin support doesn't cover yet, stated plainly.