MAMMOTH / GETTING STARTED

Your first document.

Install Mammoth, start a local database and connect with tools you already know.

Start with an evaluation.

Mammoth is currently a prerelease project. The latest published tag is v0.1.0-beta; the default branch’s VERSION file says 0.0.1. Check release notes and validate your workload before relying on the engine.

01 / Install the engine

You need Go 1.23 or newer and a writable directory for database files. Install the published beta from source:

terminal
go install github.com/mammothengine/mammoth/cmd/mammoth@v0.1.0-beta

Make sure your Go binary directory (go env GOBIN, or the bin directory under go env GOPATH) is on PATH. Run mammoth version to check installation. The CLI’s version string may reflect its build-time default.

Prefer a prebuilt binary? The beta release contains Linux and macOS archives for amd64/arm64, and a Windows amd64 ZIP. Download the archive matching your system, extract it, and add the executable directory to PATH.

02 / Start a local server

Run this command in a terminal and leave it running. It explicitly binds the database connection to your local machine:

local server
mammoth serve --bind 127.0.0.1 --port 27017 --data-dir ./data

The CLI requires the serve subcommand. Data is stored in ./data. Use a dedicated persistent directory for real data.

03 / Connect and write

Install mongosh separately, then open a second terminal:

connect
mongosh mongodb://127.0.0.1:27017
mongosh
use playground

db.ideas.insertOne({
  name: "My next big thing",
  ready: true
});

db.ideas.find({ ready: true });

You can also use an application’s MongoDB driver with the same connection URI. Test your driver version and required commands; protocol support does not guarantee complete MongoDB parity.

Choose your next step

Grounded in the upstream source · snapshot 6b186803 · reviewed 19 October 2026.

CLI implementation Releases Go module