CLI overview and installation

What the kelta CLI covers, how its commands are organised, global flags, discovery for people and agents, and the generated reference pages.

kelta is the command-line interface to everything in this documentation: the admin surface (collections, fields, layouts, list views, pages, menus, dashboards, flows, users, limits, sandboxes, promotion), record CRUD, metadata packages, a raw API escape hatch and a local MCP bridge. It is designed for scripts and AI agents as much as for people: JSON when piped, stable error codes, a machine-readable command catalogue.

Install it with the one-liner on Install the Kelta CLI, then kelta auth login --url https://api.example.com --tenant <slug>.

Command groups#

GroupCommands
authlogin, logout, status
tokenlist, create, revoke
profilelist, use, show, remove, rename
collectionslist, describe, create, update, delete
fieldslist, add, update, remove
picklistslist, get, create, delete, value-add, value-update, value-deactivate
validation-ruleslist, create, update, delete
constraintslist, create, delete
layoutslist, get --tree, create, apply, update, delete
list-viewslist, get, create, apply, update, delete
pageslist, get, create, apply, update, publish, delete
menuslist, get --tree, create, apply, update, delete
dashboards, reportslist / get / apply
flowslist, describe, create, update, execute, runs, run, cancel, retry, publish, versions, webhook-url
userslist, get, invite, portal-invite, reset-password, token-create, logins
limitsget, set-tier, set
auditsetup, security, logins
recordslist, get, create, update, delete, bulk, search, semantic-search
metadataexport, diff, apply
sandbox, promoteenvironment and promotion lifecycle
sdktypes — generate TypeScript types from the tenant’s OpenAPI document
mcpserve, install
top levelapi, docs, manifest, version, update

The complete list with every flag and default is generated from the command registry: Command reference.

Global flags#

FlagEffect
--profile <name>which saved connection to use
--output table|json|yaml|csv|ndjsonoutput format (table on a TTY, JSON when piped)
--rawthe unflattened JSON:API envelope
--quietids only, one per line
--yesconfirm destructive commands non-interactively

Discovery#

  • kelta <group> --help, kelta <group> <command> --help — human help.
  • kelta manifest [--group records] — the full machine-readable catalogue: every command with a JSON Schema of its input, positionals, options, and dangerous/auth flags. Agents start here.
  • kelta docs agent — the agent guide; kelta docs jsonapi|page-layouts|list-views|dashboards|ui-pages|ui-menus|flows|packages — the authoring reference, identical to the pages under Authoring reference.

Examples#

kelta collections list --output json | jq '.[].name'
kelta records list invoices --filter status=open --filter amount.gte=100 --sort -createdAt
kelta records create invoices --data '{"amount": 120, "status": "open"}'
kelta fields add invoices --name due_date --type date --required
kelta flows execute <flowId> --input '{"key":"value"}' --wait
kelta layouts apply invoices --file main.json
kelta api GET '/api/governor-limits'

Next: Authentication and profiles, Output contract and scripting.

Edit this page on GitHub