About
Command-line interface and MCP server for oxibrain
README
A standalone, local-first second brain for humans and agents: an immutable episode ledger plus a knowledge projection that can be rebuilt from it, byte for byte.
Highlights
- No account, no API key, no external services. Extraction and embeddings run on local GGUF models by default; HTTP providers are an optional quality tier. A default build pulls zero oxi-ecosystem crates.
- One engine, three shapes — a Rust library (
oxibrain), one binary (oxibrain: CLI + caller-owned server), and a desktop brain UI. - Agent-native. Fourteen MCP tools (capped) over caller-owned stdio or a foreground loopback HTTP session. Anything reachable over MCP is reachable in-process, and vice versa.
- Assertions, not facts. The ledger records who claimed what, over which interval; knowledge is folded from assertions, and every derived summary carries its sources and uncertainty.
- No language is privileged. Character n-grams and multilingual embeddings; no stemmers, no stopword lists, no script checks. Retrieval and resolution quality is held to parity across writing systems.
Table of contents
- Install
- Quick start
- Agent skill
- Architecture
- Project structure
- Oxi ecosystem
- Documentation
- Development
- Contributing
- License
Install
cargo install oxibrain-cli
The binary is named oxibrain.
Managed install (ecosystem standard)
Hosts that supervise the binary (oxios BrainInstaller, or
oxios brain install) place it at the ecosystem-standard location:
~/.oxi/oxibrain/bin/oxibrain # launcher symlink → ../versions/<v>/oxibrain
~/.oxi/oxibrain/versions/<v>/ # one directory per release (newest 2 kept)
cargo install oxibrain-cli (→ ~/.cargo/bin/oxibrain) stays a fully
supported channel; managed and cargo installs coexist, with the managed
launcher taking precedence in hosts that resolve both.
Quick start
# Create the store and a brain space (more spaces: oxibrain admin space add <name>).
oxibrain admin init --space personal
# Pull the local GGUF model set (otherwise pulled lazily on first extraction).
oxibrain admin model pull
# Register a document root by editing ~/.oxi/brain/documents.toml (there is no
# CLI verb for registration), then reconcile the documents cache and embed
# missing chunks.
oxibrain admin index --embed
# Drain uncached memory-plane episodes through the configured extractor.
oxibrain admin extract --pending
# Query the op surface: every op takes its JSON payload via --json or stdin.
oxibrain search --json '{"space":"personal","query":"database decision","planes":["documents"],"limit":5}'
echo '{"space":"personal","query":"database decision","limit":5}' | oxibrain search
# Serve caller-owned JSON-RPC over stdio for an MCP client integration.
oxibrain admin serve --stdio
The store lives under ~/.oxi; every subcommand accepts --dir <DIR> (env
OXIBRAIN_DIR) to relocate it. admin space add provisions each space's
vault directory and document root. oxibrain describe and oxibrain schema
are the orientation and introspection entries into the op surface.
Agents use CLI operations directly or launch a caller-owned admin serve --stdio
child through oxibrain-client. The foreground admin serve --http <address>
variant exposes the local operations console.
Agent skill
oxibrain ships its own agent skill — a SKILL.md + CONTEXT.md pair that
teaches an agent the op surface (all fourteen ops), the payload contract
(space is required on every op; ids are resolved, never guessed), and the
safety rails (dry-run plan tokens, meta.dropped, locked backoff). Install
it into your agent's skill directory:
oxibrain admin skill install # omp → ~/.omp/skills/oxibrain
oxibrain admin skill install --target claude # claude → ~/.claude/skills/oxibrain
oxibrain admin skill install --target raw # print both files to stdout
Both files are generated from the op registry (oxibrain-ops), not
hand-maintained, so they cannot drift from the installed binary's surface.
Re-run the install after upgrading so the skill matches your binary.
Architecture
The immutable episode ledger is the durable source of truth. The knowledge projection — entities, assertions, search indexes, vectors, and rendered views — is derived from that ledger and can be rebuilt. The core engine stays free of transport and provider dependencies; CLI, MCP, and desktop surfaces compose it at the boundary. ARCHITECTURE.md is authoritative.
Project structure
| Crate | Role |
|---|---|
oxibrain-ports |
Port traits — LLM, embedding, tokenizer, rerank, clock |
oxibrain-core |
Domain types, temporal fold, extraction, ranking, packing |
oxibrain-index |
Lexical/graph primitives — n-gram, MinHash, adjacency |
oxibrain-store |
SQLite ledger, projection, migrations, queries |
oxibrain-views |
Pure renderers — Markdown briefs, exports |
oxibrain |
Facade library — the engine |
oxibrain-llm-local |
GGUF inference, grammar-constrained decoding |
oxibrain-llm-http |
HTTP LLM adapter (OpenAI-compatible) |
oxibrain-embed-local |
Multilingual embedding adapter |
oxibrain-connectors |
Source connectors — vault readers, file ingest |
oxibrain-client |
Client SDK — caller-owned stdio session |
oxibrain-mcp |
MCP server tools — fourteen-tool cap |
oxibrain-cli |
The oxibrain binary: CLI + caller-owned server |
Oxi ecosystem
oxibrain is intentionally standalone: it owns its ledger, projection, and local storage. oxicode, oxios, and oximemo use its public CLI or client contracts for durable memory rather than depending on its storage internals. See the ecosystem guide for the boundary map.
Documentation
- doc/ARCHITECTURE.md — authoritative architecture and invariants (P1–P11)
- doc/ROADMAP.md — sequencing and milestone exit criteria
- doc/ECOSYSTEM.md — how oxibrain composes with the oxi ecosystem
- doc/adr/ — architecture decision records
Development
cargo build
cargo fmt --all -- --check
cargo clippy --all-targets --all-features -- -D warnings
cargo test
# The standalone guarantee — no oxi crates in the tree
cargo build -p oxibrain --no-default-features --features http-llm
cargo tree -p oxibrain | grep -E 'oxios-|oxicode-' && exit 1
Releases: tag v* publishes all crates in dependency order and creates the
GitHub release (.github/workflows/publish.yml, scripts/publish.sh).
Contributing
Read AGENTS.md before contributing. It defines the architectural invariants, quality gates, and documentation authority for this repository.
License
MIT OR Apache-2.0
Installing Oxibrain Cli
This server has no published package — it is built from source. Open the repository and follow its README.
▸ github.com/a7garden/oxibrainFAQ
Is Oxibrain Cli MCP free?
Yes, Oxibrain Cli MCP is free — one-click install via Unyly at no cost.
Does Oxibrain Cli need an API key?
No, Oxibrain Cli runs without API keys or environment variables.
Is Oxibrain Cli hosted or self-hosted?
Self-hosted: the server runs locally on your machine via the install command above.
How do I install Oxibrain Cli in Claude Desktop, Claude Code or Cursor?
Open Oxibrain Cli on unyly.org, pick your client tab (Claude Desktop, Claude Code, Cursor) and press Install — the config is generated automatically, no JSON editing.
Related MCPs
GitHub
PRs, issues, code search, CI status
by GitHubFilesystem
Secure file operations with configurable access controls.
Memory
Knowledge graph-based persistent memory system.
Template MCP Server
A CLI tool to create a new Model Context Protocol server project with TypeScript support, dual transport options, and an extensible structure
by mcpdotdirectAmap Maps Mcp Server
MCP server for using the AMap Maps API
by duxiaohuiSupabase
Database, auth and storage
by SupabaseEverything
Reference / test server with prompts, resources, and tools.
Git
Tools to read, search, and manipulate Git repositories.
Sequential Thinking
Dynamic and reflective problem-solving through thought sequences.
Time
Time and timezone conversion capabilities.
Compare Oxibrain Cli with
Not sure what to pick?
Find your stack in 60 seconds
Author?
Embed badge for your README
Browse similar
All development MCPs
