Anythink Cli

What anythink-cloud/anythink-cli MCP server does

The anythink-cloud/anythink-cli MCP server gives an agent access to Anythink's headless backend platform through MCP. It covers platform administration as well as application-backend operations. An agent can create or list billing accounts, provision projects, connect a project to a saved local profile, and inspect or remove stored configuration.

Once a project is active, the server can operate on backend resources such as entities, fields, records, workflows, users, files, roles, menus, secrets, API keys, migrations, plans, and payments through the general cli tool. The available dedicated tools also cover platform login, Google sign-in, project selection, account selection, logout, and destructive project deletion.

How it works

The anythink-cloud/anythink-cli MCP server combines focused MCP tools with a catch-all cli tool. Dedicated tools handle common account, project, authentication, and profile actions. The cli tool accepts an Anythink CLI command such as entities list or data list posts and returns its output, with --json available where the underlying command supports machine-readable output.

A typical setup starts with platform authentication, followed by selecting or creating a billing account and project. projects_use connects a project and stores project-scoped credentials; subsequent CLI operations use the active project profile. config_use switches between profiles that already exist, while config_show reports saved profiles and active platform settings without making network calls.

Setup and configuration

The anythink-cloud/anythink-cli MCP server can be launched with npx -y @anythink-cloud/mcp. The repository also documents Homebrew installation, downloadable release binaries, a .NET global tool, and building from source. Homebrew installs both the anythink CLI and the anythink-mcp server.

Local credentials and project profiles are stored in ~/.anythink/config.json. Use login for email and password authentication, or login_google for Google sign-in. Google sign-in opens a browser and works only over stdio. If credentials are already available, login_direct accepts an organization ID with an API key or JWT token.

After authentication, use accounts_list and accounts_use to select a billing account. Use projects_list to find a project, or accounts_create and projects_create to create the required resources. Newly created projects provision asynchronously and should be checked with projects_list until they become Active.

Tools and capabilities

• Authenticate with email and password, Google, or direct project credentials.
• List and select billing accounts and provision isolated projects.
• Connect, switch, inspect, or remove local project profiles.
• Run Anythink CLI commands for entities, fields, data, search, workflows, users, files, roles, menus, integrations, payments, OAuth, migrations, and related operations.
• Create, inspect, update, and delete backend entities and their data through CLI commands.
• Permanently delete projects, including their database and stored data, when an active billing account is available.

Limitations and notes

The cli tool can execute destructive commands, so commands that delete entities, data, or projects require care. Project deletion is irreversible, and the dedicated deletion tool recommends confirming the target with the user and preferring a full project ID over a short prefix.

Project and account management depends on the relevant authentication and billing state. A project must be Active before it can be connected with projects_use, and project creation requires an active billing account. config_remove and logout only remove local credentials or profiles; they do not delete projects or revoke server-side tokens.

Google authentication requires a local browser and is not available through the hosted HTTP server. The provided material does not specify compatibility with individual MCP desktop clients, pricing, or service plan requirements.