Anythink all-in-one backend: data, auth, files, workflows, payments, APIs

Make an authenticated API request to the active project. Sends a request to any project endpoint, with the path relative to /org/{project}, using the CLI's credentials, and prints the response body. Use it only where no dedicated tool exists, such as /permissions or integration field options; POST, PUT and DELETE change data. all follows every page of a GET. It changes or deletes existing data, so check with the user before running it.

Add a field to an entity. Adds a column to an existing entity; always pass the database type. The display type defaults from it (varchar to input, boolean to checkbox, relationships to relationship). Relationship types need the target entity's name, and on-delete defaults to CASCADE; user and file fields link to users and files automatically. Returns the new field's id.

Delete a field from an entity. Takes the field's name, not its id, and drops that column from the entity, so the value it held is lost from every record. To remove the whole entity and its records, use `entities_delete`. It changes or deletes existing data, so check with the user before running it.

Get the full definition of one field (including relationship config). Finds the field by name on the entity (not case-sensitive) and returns its full definition as a JSON object, including relationship settings, select options, default value and search flags. To see every field on an entity at once, use `fields_list`.

List fields on an entity. Takes the entity name. Returns each field's id, name, label, database type, display type and its required, unique, indexed and locked flags. For one field's complete definition, including relationship target and select options, use `fields_get`; for the entity's own settings, use `entities_get`.

Update properties of an existing field. Changes a field's label, description, display type, default value, select options and its required, searchable, public-search and indexed flags. Settings you don't pass keep their value, except the description, which is cleared unless passed again. It cannot rename a field or change its database type, and locked fields are refused. It changes or deletes existing data, so check with the user before running it.

Delete a file by ID. Removes the file from the project's storage by its id. Records that reference it through a file field follow that field's on-delete rule; with the default, CASCADE, they are deleted too. To see what is stored first, use `files_get`. It changes or deletes existing data, so check with the user before running it.

Get file metadata by ID. Returns one file's original and stored names, type, size, whether it is public and when it was uploaded. It gives metadata only, not the file's contents or a download link. To browse all files, use `files_list`.

List uploaded files. Returns one page of the project's uploaded files, 25 by default, with each file's id, original name, type, size, whether it is public and when it was uploaded. Use `files_get` for one file's details, including its stored name.

Upload a file. Uploads a file from a path on the machine running the CLI to the project's file storage and returns its new id and stored name. Files are private by default; a public file can be fetched without signing in. Use the returned id as the value of a file field with `data_create` or `data_update`.

Import collections, fields, flows, and data from a Directus instance. Writes into the active project: run with --dry-run first and add --yes only once the user has approved the plan. Copies a Directus instance's collections and fields into the active project as entities and fields; flows, files, roles and records come across only with include_flows, include_files, include_roles and include_data. Call it with dry_run first and show the user the plan, because a call without dry_run applies the import straight away. Returns JSON. It changes or deletes existing data, so check with the user before running it.

Connect to a provider with an API key (prompts for the key if not given). Only for providers whose auth type is api_key (see `integrations_get`); OAuth providers fail here and need `integrations_oauth_configure`. Stores the key encrypted on the server and creates a project-wide connection, or a private one with user_connection, printing its id. Pass the key in api_key, then check the connection with `integrations_test`.

List your integration connections. Shows each connection's id, provider, name, scope (the whole project or one user) and whether it is enabled; stored credentials are never shown. Use the id with `integrations_test`, `integrations_enable`, `integrations_disable` and `integrations_disconnect`.

Disable a connection. Stops `integrations_execute` and workflow steps from using the connection but keeps its stored credentials, so `integrations_enable` can turn it back on. Prefer this to `integrations_disconnect` when the pause may be temporary.

Delete a connection. Removes the connection and its stored credentials from the project; workflow steps that rely on it fail until the provider is connected again with `integrations_connect` or the OAuth flow. Use `integrations_disable` to pause it instead. It changes or deletes existing data, so check with the user before running it.

Enable a connection. Turns a disabled connection back on so `integrations_execute` and workflow steps can use it again; its stored credentials are unchanged. Returns the connection's name and new state. The opposite is `integrations_disable`.

Run an operation on a connected provider. Calls the provider live with the project's first enabled connection to it, using inputs given as key=value pairs or a JSON object, and may incur the provider's charges. The API currently runs only the claude provider (inputs prompt, system_prompt, model, max_tokens); other providers return an error, so use them in workflow steps via `workflows_integration_add`. Returns JSON.

Show details and operations for one provider. Shows the provider's description, auth type and each operation's key, name and description. Operation keys are what `integrations_execute` and workflow integration steps (`workflows_integration_add`) take. It does not say whether the project is connected; `integrations_connections_list` does.

List available integration providers. Start here when connecting a third-party service. Shows each provider's key, category, auth type (api_key or oauth2) and operation count; providers turned off for this project are left out. Next, read a provider with `integrations_get`, then connect it with `integrations_connect` (API key) or `integrations_oauth_configure` (OAuth).

Print the redirect URL to add to OAuth app configurations (same for every provider). Prints only the dashboard redirect URL for this project, worked out locally from the API address and project id without an API call. Give it to the user to add to their OAuth app at the provider before `integrations_oauth_configure`; `integrations_oauth_status` shows it with the provider's setup state.

Set the OAuth client ID + secret for a provider. Saves the client ID and secret of an OAuth app the user created at the provider and enables it for the project (disable saves it switched off). Each run replaces the previous settings, so social sign-in turns off unless use_social_sign_in is passed again. Afterwards users connect from the dashboard or with `integrations_oauth_connect`. It changes or deletes existing data, so check with the user before running it.

Connect via the browser OAuth flow (starts a local listener). Opens the provider's sign-in page in a browser on this machine and waits up to five minutes for the callback on localhost (port 8745 by default), then creates the connection. A person must complete the sign-in, and the provider must first be set up with `integrations_oauth_configure`; for API-key providers use `integrations_connect`.

Show OAuth client setup status for a provider. Shows whether a client ID is saved for the provider, whether it is enabled and also used for end-user social sign-in, and the redirect URL its OAuth app must allow. Check it before `integrations_oauth_configure`, or after to confirm the credentials were saved.

Test a connection. Use after connecting, with an id from `integrations_connections_list`. The API currently only confirms the connection exists in this project and does not call the provider, so a pass does not prove the stored credentials work.

Log in to the Anythink platform with email and password. Returns a session token used for account and project management. For Google sign-in, use the 'login_google' tool.

Store credentials directly for a project (bypasses billing login). Use this when you already have an org ID and API key or JWT token.

Sign in to the Anythink platform with Google. Opens the user's browser to Google's consent screen and waits for them to approve, then stores the session token. The browser step must be completed by the user; everything before and after is tool-driven. This does NOT pick a billing account or project — after it returns, call 'accounts_list' then 'accounts_use', and 'projects_list' then 'projects_use'. Needs a local browser, so it only works over stdio (not the hosted HTTP server).

Remove the saved credentials for a project profile from local CLI config. Use this to disconnect from a project or clear a stale token; it deletes only the stored profile locally and does not revoke the token server-side or affect the project. Omit the profile to remove the currently active one. Run 'config_show' to see profile names.

Add a menu item for an entity. The item links to the entity's data page in the dashboard, is named after the entity in title case unless name is given, uses a Lucide icon (Database by default) and goes last at the top level or under parent. The entity must exist; to link to another path, add the item and then set href with `menus_update_item`.

Create a menu for a role. The new menu is empty; add items with `menus_add_item`. A role is shown only its first menu, so a second menu for the same role may not appear; use `menus_reorder` to choose which comes first.

Delete a menu and all of its items. Removes the menu and every item in it, including locked built-in items, and can't be undone. If it was the role's only menu, that role is left with no dashboard menu; to drop single items, use `menus_remove_item` instead. It changes or deletes existing data, so check with the user before running it.

Show one menu with its items and their child items. Gives the menu's role id and its full item tree, with each item's id, name, icon, href, parent and whether it is a locked built-in item. Use it to find item ids for `menus_update_item`, `menus_remove_item` and `menus_reorder_items`. Returns JSON.

List all menus and their items. Shows every menu with its id, name and the role id it is shown to, plus its items' ids, names, icons and links. Only top-level items and their direct children are listed; use `menus_get` for one menu's full item tree, including which items are locked.

Remove a menu item, along with its child items. Deletes the item and its direct child items from the menu. It refuses locked built-in items, and items whose children are locked or have children of their own; move those out first with `menus_update_item`. It changes or deletes existing data, so check with the user before running it.

Set the order of menus. Menus you name come first in that order and the rest follow in their current order. Order matters when a role has more than one menu, because the role is shown only its first; to change a menu's role, use `menus_update`. It changes or deletes existing data, so check with the user before running it.

Set the order of menu items that share a parent. The items must share one parent: the ones you name take the first places in that group in the order given, other siblings follow in their current order, and locked items keep their place. To move an item under a different parent, use `menus_update_item`. It changes or deletes existing data, so check with the user before running it.

Rename a menu or change the role it is shown to. Changes the menu's name, the role it is shown to, or both; its items stay as they are. A role is shown only its first menu, so moving a menu to a role that already has one may hide it; use `menus_reorder` to choose which comes first. It changes or deletes existing data, so check with the user before running it.

Change a menu item's name, icon, link or parent. Changes only the fields you pass: name, Lucide icon, entity (links to that entity's page) or href (any path), and parent (0 for top level). A moved item goes last under its new parent, and locked built-in items can't be changed. To reorder items without moving them, use `menus_reorder_items`. It changes or deletes existing data, so check with the user before running it.

Set Google OAuth client ID and secret. Saves the Google Cloud OAuth client ID and secret that let the project's end users sign in with Google, and switches that sign-in on or off. It only works interactively, prompting for each value (blank keeps the current one), then prints the callback URL to add to the Google OAuth client. It changes or deletes existing data, so check with the user before running it.

Show Google OAuth configuration status. Reports whether Google sign-in for the project's end users is enabled and whether a client ID and secret are saved, without showing them. This covers user sign-in only; Google as an integration is handled by `integrations_oauth_status` and `integrations_oauth_configure`.

Set up a Stripe Connect account and start onboarding. Creates the project's Stripe Connect account and opens Stripe's hosted onboarding page in a browser, which must be finished before plans can take card payments. It prompts for business type, country and email, so it needs an interactive terminal. Check `pay_status` first.

Show the current user's access / trial entitlement. Reports whether the signed-in user (the one this tool runs as) has paid or trial access in the project's app: status, trial end and days left, subscription id, provider, product and expiry. Read-only. To look up another user, use `pay_subscriptions_by_user`.

List saved payment methods. Lists the cards and other payment methods saved by the signed-in user as a customer of this project: type, brand, last four digits and expiry. It does not list your end users' cards or the card on your Anythink billing account. Read-only.

Activate a paused offer. Sets an offer's status to active so its codes can be redeemed again, still subject to its validity dates and caps. Use it to undo `pay_offers_pause` or to reopen an expired offer.

Add a promo/referral code to an offer. Creates a code users enter to redeem the offer: a shared promo code, or with an owner user id, a personal referral code tied to that user. Returns the new code. There is no tool to remove a single code; codes go only when the offer is deleted with `pay_offers_delete`.

List the promo/referral codes attached to an offer. Lists every code on one offer, both shared promo codes and per-user referral codes, with slug, owner (or shared), redemption count and created date. Read-only. To find a specific user's personal referral code, use `pay_offers_user_code`.

Create an offer (rewards via convenience flags or raw JSON). Creates an offer of kind discount, trial_extension or referral. A redeemer reward is required, as raw JSON or a shortcut such as trial days or discount percent; referrer reward, eligibility, caps and dates are optional. Discount offers also create a Stripe coupon. Add a code users can enter with `pay_offers_add_code`.

Permanently delete an offer and all its codes + redemptions (history is lost; trial bonuses already granted are preserved). Returns how many codes and redemptions were deleted and how many trial bonuses were kept. The offer's Stripe coupon is not removed. To stop redemptions while keeping the history, use `pay_offers_pause` instead. It changes or deletes existing data, so check with the user before running it.

Show one offer by id (guid). Shows one offer in full: kind, description, status, primary code, redeemer and referrer rewards, eligibility rules, per-user and total caps, validity dates and linked Stripe coupon id. Read-only; its codes and redemptions come from `pay_offers_codes` and `pay_offers_redemptions`.

List offers. Lists the project's offers (discounts, trial extensions and referral schemes that users redeem with a code): id, name, kind, primary code, redeemer and referrer rewards, and status. Read-only. Offers are separate from subscription plans (`pay_plans_list`).