anythink-cloud/anythink-cli

The official command-line interface for Anythink — the headless backend platform for developers and founders. Manage your projects, entities, data, workflows, users, files, and payments without leaving the terminal.
---
Contents
- Installation
- Getting started
- Command reference
- signup / login / logout
- accounts
- projects
- config
- entities
- fields
- data
- search
- workflows
- users
- files
- email
- roles
- api-keys
- menus
- charts
- dashboards
- settings
- integrations
- pay
- oauth
- api
- docs
- migrate
- plans
- MCP server
- Contributing
- License
---
Installation
Both the anythink CLI and the anythink-mcp server are distributed together. The quickest way to get both is Homebrew.
Homebrew (macOS / Linux) — recommended
This installs **both** commands onto your PATH:
- anythink — the CLI
- anythink-mcp — the MCP server (see MCP server)
Or tap first, then install:
Update to the latest release:
Uninstall:
macOS / Linux — download binary
Grab the latest release for your platform from the Releases page:
| Platform | Binary |
| --------------------- | ---------------------- |
| macOS (Apple Silicon) | anythink-osx-arm64 |
| macOS (Intel) | anythink-osx-x64 |
| Linux (x86_64) | anythink-linux-x64 |
| Linux (ARM64) | anythink-linux-arm64 |
The MCP server ships as a matching anythink-mcp- binary on the same release — download and install it the same way (e.g. anythink-mcp-osx-arm64).
Verify the download against checksums.txt in the release assets:
.NET global tool
If you have the .NET 8 SDK installed:
Build from source
---
Getting started
Your credentials and project profiles are stored in ~/.anythink/config.json. You can manage multiple projects by running projects use to switch between them.
---
Command reference
signup / login / logout
signup and login are interactive — they prompt for email and password and walk you through connecting to a billing account and project on first run.
---
accounts
Manage billing accounts. A billing account is the container for one or more projects and holds your subscription and payment details.
**Examples**
---
projects
Create and manage Anythink projects. Each project is an isolated backend instance with its own database, auth, files, and workflows.
**Options — projects create**
| Flag | Description |
| --------------- | ------------------------------- |
| --region | Deployment region (e.g. lon1) |
| --plan | Plan ID (see anythink plans) |
**Examples**
---
config
View and manage saved CLI profiles.
Profiles are named by project alias or ID and stored in ~/.anythink/config.json.
---
entities
Manage entities (database tables) in the active project.
**Options — entities create**
| Flag | Description |
| ------------ | ------------------------------------------ |
| --rls | Enable row-level security |
| --public | Make the entity publicly readable |
| --lock | Lock new records (prevent direct creation) |
| --junction | Mark as a junction (many-to-many) table |
**Examples**
---
fields
Manage fields on an entity. Fields map directly to database columns.
**Options — fields add**
| Flag | Description |
| ------------------- | --------------------------------------------------------------------------------- |
| --type | Field type: varchar, text, int, float, bool, datetime, json, uuid |
| --required | Mark the field as required |
| --unique | Enforce a unique constraint |
| --indexed | Add a database index |
| --default | Default value |
**Examples**
---
data
CRUD operations on entity records.
**Options — data list**
| Flag | Description |
| ----------------- | ---------------------------------------------------------------------------------- |
| --limit | Records per page (default: 20) |
| --page | Page number (default: 1) |
| --filter | Field filters — JSON ({"status":"draft","total":{"gte":10}}) or field=value pairs (status=draft&total=GTE:10). See below. |
| --json | Output raw JSON instead of table |
| --all | Stream all pages as sequential JSON objects (requires --json, constant memory) |
**Filter operators (JSON form)** — {"field": value} matches exactly, {"field": [a, b]} matches any, {"field": null} matches empty. For anything else use an operator object, e.g. {"price": {"gte": 10, "lt": 100}}:
| Operator | Meaning | field=value form |
| ------------------------------ | --------------------------- | ------------------ |
| eq / ne | Equal / not equal | x=v / x=!v |
| gt gte lt lte | Comparisons | x=GT:v … |
| contains / not_contains | Case-insensitive substring | x=C:v / x=NC:v |
| starts_with / ends_with | Case-insensitive prefix/suffix | x=SW:v / x=EW:v |