Skip to main content
Glama
anythink-cloud

Anythink-MCP

Official

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
PROFILENoThe CLI profile to pin (e.g., 'my-project'). If not provided, the default profile is used.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}
logging
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
pay_statusB

Show Stripe Connect account status

entities_createC

Create a new entity

projects_deleteA

Permanently delete a project and tear down its backend instance, including its database and stored data. This is destructive and irreversible — always confirm with the user first, and prefer matching by a specific id over a short prefix to avoid removing the wrong project. Requires an active billing account (set one with 'accounts_use'). Returns the deleted project's name and id on success.

login_googleA

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).

workflows_file_handler_exampleB

Print a copy-paste-ready FileHandler params JSON

apiB

List all API endpoints (platform + dynamically generated entity routes)

accounts_listA

List the billing accounts (organizations) the logged-in user belongs to. Requires a prior platform login (use the 'login' tool first). Returns each account's id, organization name, billing email, currency, and status (Active/Suspended/Canceled), and flags which one is currently active. A billing account holds your projects and payment details — pick one with 'accounts_use' before creating or listing projects.

secrets_createC

Store a new secret value

integrations_oauth_connectB

Connect via the browser OAuth flow (starts a local listener)

workflows_exportA

Export an existing workflow to JSON (round-trippable with seed)

roles_createC

Create a new role

fields_updateC

Update properties of an existing field

workflows_deleteC

Delete a workflow

workflows_updateB

Update a workflow's name or description

data_listC

List records in an entity

entities_getC

Get entity details and fields

docsA

Print the full CLI reference (markdown or --json for AI/tooling consumption)

login_directA

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

accounts_useA

Set the active billing account that project commands operate on. Call this after 'login' when you belong to more than one account, before using 'projects_list', 'projects_create', or 'projects_use'. Accepts a full account UUID or a unique prefix; run 'accounts_list' to see valid ids. Returns the resolved account name and id, or an error if no account matches.

pay_connectA

Set up a Stripe Connect account and start onboarding

files_uploadC

Upload a file

files_getB

Get file metadata by ID

secrets_listA

List all secret keys (metadata only, values never shown)

menus_listA

List all menus and their items

integrations_oauth_callback_urlA

Print the redirect URL to add to OAuth app configurations (same for every provider)

workflows_step_addC

Add a step to a workflow

integrations_connectA

Connect to a provider with an API key (prompts for the key if not given)

secrets_updateB

Rotate (overwrite) an existing secret value

data_getB

Get a single record by ID

integrations_oauth_statusB

Show OAuth client setup status for a provider

workflows_seedB

Create a workflow and its steps from a JSON file

integrations_disconnectC

Delete a connection

integrations_disableC

Disable a connection

menus_add_itemC

Add a menu item for an entity

entities_deleteB

Delete an entity and all its data

fields_deleteC

Delete a field from an entity

data_updateC

Update a record

workflows_jobsB

View job history for a workflow

integrations_oauth_configureC

Set the OAuth client ID + secret for a provider

data_createC

Create a new record

workflows_file_handler_addC

Add a FileHandler step with named flags (no hand-written params JSON)

roles_permissions_addC

Add entity permissions to a role

roles_permissions_removeC

Remove entity permissions from a role

workflows_createC

Create a new workflow

api_keys_listA

List API keys for the current user

config_removeA

Delete a saved project profile from the local CLI configuration. Removes only the locally stored credentials and settings — it does not delete the project or revoke tokens server-side (to remove the project itself, use 'projects_delete'). Run 'config_show' to see profile names. Returns confirmation, or a not-found message.

data_deleteC

Delete a record

files_listB

List uploaded files

workflows_step_deleteA

Delete a step from a workflow (warns if other steps link to it)

workflows_disableC

Disable a workflow

projects_listA

List the projects (provisioned backend instances) in a billing account. Requires platform login and an active billing account (set one with 'accounts_use'). Returns each project's id, name, description, region, org id, status (Initializing/Provisioning/Active/Suspended/Terminated/Error), API URL, and creation date. Use this to find a project's id before connecting with 'projects_use' or removing it with 'projects_delete'.

integrations_enableC

Enable a connection

files_deleteC

Delete a file by ID

users_meB

Show the currently authenticated user

workflows_step_updateC

Update step parameters and properties

fields_listC

List fields on an entity

projects_createA

Provision a new project — a dedicated, isolated Anythink backend instance with its own database, API, auth, and storage. Requires platform login and an active billing account (set one with 'accounts_use'). Provisioning runs asynchronously: the project starts in a Provisioning state, so poll 'projects_list' until it is Active. Returns the new project's id, name, org id, and API URL. Connect to it with 'projects_use'.

users_inviteB

Create a user and send an invitation email

integrations_executeC

Run an operation on a connected provider

integrations_listA

List available integration providers

pay_paymentsC

List recent payments

api_keys_revokeC

Revoke an API key by ID

integrations_testC

Test a connection

workflows_enableC

Enable a workflow

oauth_google_configureC

Set Google OAuth client ID and secret

secrets_deleteC

Delete a secret

logoutA

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.

roles_listB

List all roles

integrations_getB

Show details and operations for one provider

workflows_listC

List all workflows

workflows_step_linkC

Link workflow steps together (set on-success/on-failure)

projects_useA

Connect to a project and save it as the active profile so the 'cli' tool's data, entities, users, and other commands target it. Resolves the project, then either stores the API key you pass or exchanges a transfer token for project-scoped credentials automatically. Requires an active billing account (set one with 'accounts_use'); the project must be Active (see 'projects_list'). Returns the saved profile name, org id, API URL, and auth method.

workflows_triggerC

Manually trigger a workflow

roles_deleteB

Delete a role by ID

accounts_createA

Create a new billing account (organization) to hold projects and payment details. Requires a prior platform login (use the 'login' tool first). The new account is automatically set as the active account, so subsequent 'projects_create' / 'projects_list' calls target it without further setup. Returns the new account's id and name. Most users need only one account — call 'accounts_list' first to check whether a suitable one already exists.

oauth_google_statusB

Show Google OAuth configuration status

roles_permissions_listB

List entity permissions for a role

workflows_getC

Get workflow details and steps

entities_listB

List all entities

api_keys_createA

Create an API key. The raw key is shown once and never retrievable.

search_rehydrateB

Rehydrate the search index. Omit ENTITY to rehydrate everything (admin only).

pay_methodsB

List saved payment methods

users_listC

List all users

loginA

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.

config_showA

Show the local CLI configuration: all saved project profiles and platform logins, and which of each is active. For every profile it returns the name, org id, auth method (api-key or token), alias, and platform; for every platform it returns the URLs, billing account, and login status. Use this to discover profile names for 'config_use', 'config_remove', or 'logout', and to check which project the 'cli' tool currently targets. Reads local config only — makes no network calls.

search_similarB

Find documents similar to a given record (vector search)

entities_updateC

Update entity settings

signupA

Register a brand-new Anythink platform account with email and password. Use this only when the user has no account yet; if they already have one, use 'login' instead. This creates the top-level user identity — it does not create a billing account or project (do that with 'accounts_create' and 'projects_create' after logging in). On success the user may need to click an email confirmation link before 'login' works; tell them to confirm, then call 'login'.

integrations_connections_listC

List your integration connections

users_deleteC

Delete a user by ID

users_getB

Get a user by ID

fetchC

Make an authenticated API request to the active project

config_useA

Switch the active project profile that the 'cli' tool's commands operate against. Use this to move between already-connected projects without re-authenticating. The profile must already exist (created by 'projects_use' or 'login_direct'); run 'config_show' to see available profile names. Returns confirmation, or an error if the profile does not exist.

search_purgeA

Purge the search index. Omit ENTITY to purge everything (admin only).

data_rlsC

View or set RLS (row-level security) user access on a record

fields_addC

Add a field to an entity

search_auditB

Compare configured public-searchable fields vs what public search actually returns. Flags any data leaks.

search_queryC

Run a search query

workflows_step_getB

View step details including parameters

fields_getB

Get the full definition of one field (including relationship config)

workflows_integration_addB

Add an Integration step (Claude, OpenAI, Slack…) with named flags (no hand-written params JSON)

cliA

Run any Anythink CLI command and return its output. Prefer the dedicated tools; use this for anything they don't cover. Pass the command exactly as you would after 'anythink', e.g. 'entities list' or 'data list posts'. For destructive commands add '--yes' to skip confirmation prompts. Add '--json' where supported for machine-readable output.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

C2.8/5.0

Scored across 102 tools

Disambiguation3/5

Many tools are clearly scoped by resource and action, but the 102-tool surface creates overlap: `cli`, `fetch`, and `api` can all be used for API access, while `integrations_connect` vs `integrations_oauth_connect` and several workflow helper tools require careful selection. Descriptions help, but the sheer number increases misselection risk.

Naming Consistency4/5

Names predominantly follow a consistent snake_case resource_action pattern (e.g., `entities_create`, `fields_update`, `workflows_step_add`). A few bare commands like `fetch`, `docs`, `api`, `cli`, `login`, `logout`, and `signup` are minor deviations from that pattern.

Tool Count1/5

With 102 tools, this far exceeds the normal 3-15 range and the 50+ extreme-mismatch threshold. A generic `cli` and `fetch` already cover broad functionality, so many individual tools are over-provisioned rather than essential.

Completeness4/5

The surface covers most domain lifecycle areas: auth, billing, projects, entities, fields, data, files, search, workflows, integrations, secrets, roles, users, API keys, and payments. Some resource-specific gaps remain (e.g., user update, menu item management), but the generic `cli`/`fetch` tools provide workarounds.

Maintenance

ActivityMaintained
ResponsivenessUnresponsive