CLI

The teseladb commands: start a node, develop locally, administer the cluster and the MCP server.

A single binary acts as node, administration tool and MCP bridge.

Node

teseladb start [--dbpath <dir>] [--cores <n>] [--bind_ip <dirs>] [--port <n>]
               [--peer-listen <addr>] [--admin-listen <addr>] [--join <addr>] [--enroll-token <t>]
               [--insecure] [--insecure-allow-remote] [--log-format text|json] [--config <file.yaml>]
teseladb dev [--nodes <n>] [--cores <n>] [--port <n>]
teseladb mcp --uri https://<node>:27080
teseladb --version
teseladb --help

Option	Default	What it does
`--dbpath`	`./teseladb-data`	Data directory
`--cores`	logical cores	Worker threads, the same on every node
`--bind_ip`, `--port`	`127.0.0.1`, `27017`	Client addresses and port
`--peer-listen`	`127.0.0.1:27100`	Port between nodes
`--admin-listen`	`127.0.0.1:27200`	Administration port
`--http-port`, `--http-bind`	`27080`	REST API and MCP; `0` turns it off
`--join`, `--enroll-token`	—	Join an existing cluster
`--log-format`	`text`	`json` writes one JSON line per event
`--config`	—	YAML file with `mongod` keys (`storage.dbPath`, `net.port`…) and TeselaDB's own under `teseladb.*`

The TLS, encryption, auditing and resource options are in TLS and certificates, Encryption at rest, Auditing and Production checklist. A mongod option that makes no sense in TeselaDB is a usage error that says so.

Administration

teseladb admin [--node <addr>] nodes
teseladb admin [--node <addr>] metrics
teseladb admin [--node <addr>] ranges [--collection db.c]
teseladb admin [--node <addr>] range split <range_id> [--at <key>]
teseladb admin [--node <addr>] range merge <range_id>
teseladb admin [--node <addr>] range relocate <range_id> --core <n>
teseladb admin [--node <addr>] node drain <node_id>
teseladb admin [--node <addr>] node remove <node_id>
teseladb admin [--node <addr>] backup --at <timestamp|now> --out <dir>
teseladb admin [--node <addr>] restore --from <dir>
teseladb admin [--node <addr>] config get|set <parameter> [value]
teseladb admin [--node <addr>] token create [--ttl 1h]
teseladb admin [--node <addr>] cert rotate
teseladb admin [--node <addr>] apikey create|list|revoke …
teseladb admin [--node <addr>] topology set …
teseladb admin [--node <addr>] tenant create|list|drop [<name>]

--node defaults to 127.0.0.1:27200. The CLI presents itself with --tlsCertificateKeyFile and --tlsCAFile or, without them, with the node certificate of --dbpath. Output is text or --format json; the exit code is 0 on success, 1 on error and 2 on wrong usage.

PreviousGlossary NextPorts