Anythink CLI

Your whole backend, from the terminal

The open source Anythink CLI runs a whole project from the terminal: entities, fields, data, workflows, roles, users, files, search, secrets and integrations.

The same task, three ways

Connect Slack to a project.

The Anythink dashboard

Point and click. Good for seeing what is connected.

The Anythink CLI

One command opens the OAuth flow and saves the connection. Scriptable for any project.

$ anythink integrations oauth connect slack --name "Team workspace"$ anythink integrations connections list
  • ✓Browser opens to approve Slack access
  • ✓Connection Team workspace saved

Claude, through MCP

The assistant runs the same command and hands you the link to approve.

you › “Connect our Slack workspace to this project, name the connection Team workspace, and give me the link to approve it.”

  • ✓Started the Slack OAuth flow
  • ✓Named the connection Team workspace
  • ✓Sent you the link to approve
  • ✓Listed connections to confirm it saved

Why teams script Anythink

The CLI is a full client for the Anythink API, not a deploy helper.

Environments

Dry-run a promotion before it happens

migrate compares two projects and shows what it would create before it touches anything. It remaps entity-scoped permissions to the target project's entities.

Access

The permission mistake, caught at creation

A missing permission is the most common reason an integration gets a 403. The CLI checks every name you pass and tells you when the server granted less than you asked for.

AI

MCP runs the same commands

The anythink-mcp server has a cli tool that runs any Anythink CLI command, so Claude, Cursor or another MCP client reaches everything the CLI does.

Integrations

Project-wide or per user

Connect a provider once for the whole project, or add --user-connection so the connection belongs to one user. Test, disable and disconnect connections from the terminal too.

Every part of a project, one command away

The CLI talks to the same API as the dashboard, so anything you script here shows up there straight away.

Workflows as files

Export a workflow to JSON, keep it in your repository and seed it into another project with variables substituted. Add steps, trigger runs and read job history from the terminal.

In practice

Real commands from anythink --help

schema.sh
anythink entities create products --rls
anythink fields add products price --type decimal --required
anythink fields add products status --type varchar \
  --display select --options draft,live

How it works

01

Install

Run brew install anythink-cloud/tap/anythink. You get the anythink CLI and the anythink-mcp server.

02

Sign in and pick a project

Run anythink login, then anythink projects use <id>. Each project you connect is saved as a profile you can switch between with anythink config use.

03

Build

Create entities and fields, add roles and permissions, connect integrations and set up workflows. Every change is live in the dashboard straight away.

04

Promote

Run anythink migrate --dry-run from your staging profile to production, check the preview, then run it for real.

Try it

Create an entity from the terminal

One command makes the entity and its REST API. Add fields with anythink fields add.

Core concepts →

Frequently Asked Questions

How do I install the Anythink CLI?

On macOS or Linux, run brew install anythink-cloud/tap/anythink. That installs both the anythink CLI and the anythink-mcp server. With the .NET 8 SDK you can also run dotnet tool install --global anythink-cli on any platform.

Is the Anythink CLI open source?

Yes. The CLI and the MCP server are MIT-licensed and developed in the open at github.com/anythink-cloud/anythink-cli. Issues and pull requests are welcome.

How do I promote a staging project to production?

Save a CLI profile for each project, then run anythink migrate --from <staging-profile> --to <production-profile> --dry-run to preview the changes. Run it again without --dry-run to apply them.

By default it copies entities and fields. Add --include-workflows, --include-roles, --include-settings, --include-menus, --include-files or --include-data for the rest.

Can I use the Anythink CLI in CI/CD?

Yes. Create a scoped API key with anythink api-keys create, store it in your CI secrets, and run CLI commands in your pipeline. Use --json on data and search commands to pipe output into other tools.

Still have questions?

Get in Touch

More in the same project

Every feature reads from the same data model, so each one you add works with the rest.

Documentation

Guides and reference at docs.anythink.cloud.