The Anythink MCP server exposes 16 tools. Fifteen manage sign-in, local profiles, billing accounts and projects; the cli tool does everything else by running an Anythink CLI command. Argument names are shown as an MCP client sends them. A ? marks an optional argument. To set the server up, see Connect Claude to your backend with MCP.
| Tool | Arguments | What it does |
|---|---|---|
signup |
firstName, lastName, email, password, referralCode? |
Registers a new Anythink account. Doesn't create a billing account or project. If a confirmation email is sent, confirm it before calling login. |
login |
email, password |
Signs in with email and password and saves the session locally. |
login_google |
none | Opens your browser to sign in with Google and waits for you to approve it. |
login_direct |
orgId, profile?, apiKey?, token?, baseUrl? |
Saves credentials for one project without a billing account sign-in. Needs apiKey or token. The profile is named after orgId unless you pass profile. |
logout |
profile? |
Removes a saved profile from local config, defaulting to the active one. Doesn't revoke the token or touch the project. |
| Tool | Arguments | What it does |
|---|---|---|
config_show |
none | Lists saved profiles and platform sign-ins, and which is active. Reads local config only. |
config_use |
profile |
Makes a saved profile the active one. |
config_remove |
profile |
Deletes a saved profile from local config. Doesn't delete the project. |
| Tool | Arguments | What it does |
|---|---|---|
accounts_list |
none | Lists your billing accounts with their id, name, billing email, currency, status and which is active. |
accounts_create |
name, email, currency? (gbp, usd or eur; default gbp) |
Creates a billing account and makes it active. The currency can't be changed later. |
accounts_use |
id (full id or a unique prefix) |
Makes a billing account active for the project tools. |
| Tool | Arguments | What it does |
|---|---|---|
projects_list |
accountId? |
Lists projects in the active billing account with their id, name, region, org id, status and API URL. |
projects_create |
name, planId, region? (default lon1), description?, accountId? |
Creates a project. Provisioning runs in the background, so call projects_list until its status is Active. Run plans through the cli tool to find plan ids. |
projects_use |
id (name, org id or id prefix), apiKey?, accountId? |
Connects to a project and saves it as the active profile. Without apiKey, generates a project-scoped access token. |
projects_delete |
id, accountId? |
Permanently deletes a project and all its data. This can't be undone. |
cli tool| Tool | Arguments | What it does |
|---|---|---|
cli |
command: the arguments you'd type after anythink, such as entities list or data get orders 42 |
Runs the command against the active profile and returns its output. Don't include anythink or --profile. |
Add --json where a command supports it for machine-readable output. Commands that ask for confirmation, such as entities delete, need --yes.
command can't contain query strings (?, &), currency symbols or most punctuation beyond - . / : = , @ " ' { } [ ]. Commands that break this rule are rejected before they run.
A local anythink-mcp runs your installed anythink binary, so every CLI command works. The hosted copy behind the Anythink dashboard's AI panel runs a subset:
| Command | Supported in the dashboard's AI panel |
|---|---|
entities |
list, get <name>, create <name>, delete <name> |
fields |
list <entity>, add <entity> <field> --type <type> (with --display and --required), delete <entity> <field> |
data |
list <entity>, get <entity> <id>, create <entity> --data '{...}', update <entity> <id> --data '{...}', delete <entity> <id> |
workflows |
list, get, create, update, delete, trigger, enable, disable, jobs, step-add, step-get, step-update, step-link |
users |
list, me, get <id> |
roles |
list, get <id> |
secrets |
list, create <key> --value <value>, delete <key> |
files |
list, get <id>, delete <id> |
fetch |
A raw request to your project's API. See below. |
docs |
Returns your project's OpenAPI document. |
Everything else, including integrations, menus, pay, search, migrate, api and plans, only works through a local server. The sign-in, profile, billing account and project tools are for local sessions too: the dashboard panel already works on the project you're signed in to.
fetch syntaxfetch sends a request to a path under your project's API, for example /entities/orders/items/42.
| Where | Syntax |
|---|---|
| Local server | fetch <path> --method <METHOD> --body '{...}' |
| dashboard AI panel | fetch <METHOD> <path> --data '{...}' |
The method defaults to GET. Because command can't contain ?, fetch can't send query-string filters.
These run on a local server:
entities create feedback
fields add feedback rating --type integer --required
data list orders --all --json
data create orders --data '{"customer_email":"sam@example.com","total":149.5,"status":"pending"}'
workflows jobs 4
fetch /entities/orders/items/42 --method PUT --body '{"status":"paid"}'