Download one file
then check it
One self-contained binary. No package manager and nothing else to install.
curl -sSO https://dl.cameodb.com/mac/cameodb shasum -a 256 ./cameodb
87f362d62f8ee98e1e1b934e5d1dab7eeff4f90aaf81c942c7abab135b7314e1curl -sSO https://dl.cameodb.com/linux/cameodb sha256sum ./cameodb
a77d6ce372d4a72c55647effd0149bb0ed48db9490f413ad3e3d2869de44f063curl.exe -sSO https://dl.cameodb.com/windows/cameodb.exe Get-FileHash .\cameodb.exe -Algorithm SHA256
b4c5ffa238b1c2ef8a927da9ccf36c4db14f1176a8cd64770778e023508945acThat digest is the one published with this release. If your machine prints anything else, stop and do not run the binary. Each artifact is also cosign-signed, and both SPDX and CycloneDX SBOMs ship alongside it: signatures, SBOMs and the full check.
Mark it executable
Unix-like systems need the execute bit set once after download.
chmod +x ./cameodb
chmod +x ./cameodb
# Nothing to do - .exe is runnable as downloaded. # On first run Windows may ask to confirm: More info > Run anyway, # or: Unblock-File .\cameodb.exe
Run it
Starts in the foreground, which is what you want for a first run. Storage is created at ./data/cameodb in the directory you start it from.
Starts in the foreground, which is what you want for a first run. Storage is created at .\data\cameodb in the directory you start it from.
./cameodb
# or leave it running in the background
nohup ./cameodb &
./cameodb
# or leave it running in the background
nohup ./cameodb &
.\cameodb.exe
- HTTP API on 127.0.0.1:9480.
- MCP endpoint at /mcp on the same port.
- Embedded storage: no second process to start.
It runs on sensible defaults with no config file at all. For your own settings, write one beside it; the node picks up cameodb.toml from the directory you start it in.
./cameodb generate-config > cameodb.toml # every setting, at its default ./cameodb check-config ./cameodb --http-port 9480 # common settings also work as flags and CAMEODB_* variables
./cameodb generate-config > cameodb.toml # every setting, at its default ./cameodb check-config ./cameodb --http-port 9480 # common settings also work as flags and CAMEODB_* variables
cmd /c ".\cameodb.exe generate-config > cameodb.toml" # every setting, at its default .\cameodb.exe check-config .\cameodb.exe --http-port 9480 # common settings also work as flags and CAMEODB_* variables
Connect the CLI
Open a second terminal and start the interactive client. It ships inside the same binary.
./cameodb client -i
./cameodb client -i
.\cameodb.exe client --interactive
It connects to localhost:9480 by default and greets you with a prompt.
Two commands
to confirm it works
Before loading anything, confirm the node is healthy and see what it currently holds.
cameodb@localhost ▶ health // cluster health, pretty-printed JSON cameodb@localhost ▶ list indexes // every index with document counts and mapped field names
Ingest a dataset
One command downloads the file, parses the TSV, infers a schema and batch-ingests it. There is no schema to write by hand first.
cameodb@localhost ▶ data load books https://dl.cameodb.com/examples/data/booksummaries.tsv
Schema inferred
Field types are detected from the data; delimiters and headers are handled automatically.
Batched ingest
Writes go in batches of 4,000 documents, which is what makes a load this quick.
Indexed on commit
Nothing to reindex afterwards: every document is searchable after the next commit.
Search it
Full-text search over the index you just created. A phrase match on title brings back all seven books. Swap in any title, keyword or field filter.
cameodb@localhost ▶ search books title:"Harry Potter" limit 7
The same index is reachable over MCP, so an agent can ask this question without any further setup.
You have a working
intelligence layer
The fastest next step is pointing an agent at it, and that is one command away.