Skip to main content
Glama
Sign In
Anythink-MCP

Anythink-MCP

Official
by anythink-cloud
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Remote

Run an Anythink CLI command

cli
Destructive

Execute any Anythink command and return its output. Use when dedicated tools do not cover a platform operation.

Instructions

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'. Destructive pay commands (delete, expire, relink, pause and similar) must be run by a person in a terminal; never add '--yes' on their behalf. 'data import' creates records (not destructive): run it with --dry-run first and only add '--yes' after the user approves the dry run. 'import directus' changes the project: run it with '--dry-run' first and only add '--yes' once the user has approved the plan. Add '--json' where supported for machine-readable output.

Input Schema

NameRequiredDescriptionDefault
commandYesCLI arguments after 'anythink', e.g. 'entities list', 'users me', 'data list blog_posts --json', 'migrate --from a --to b --dry-run', 'fetch /some/path'. Do NOT include 'anythink' itself or '--profile' (profile is injected automatically).

Schema Changelog

Changes observed during successful MCP inspections.

  1. Changed2 schema fields changedv0.2.27
    • removedInput schema / description
      Removed value: -"Run any Anythink CLI command and return its output. Use this for commands not covered by dedicated tools (entities, fields, data, workflows, roles, menus, secrets, users, files, pay, oauth, migrate, fetch, api, docs, etc.). Pass the command exactly as you would after 'anythink', e.g. 'entities list' or 'data list posts'. Menu commands: 'menus list' shows dashboard menus with tree structure; 'menus add-item <menu_id> <entity> --icon <Icon> --parent <parent_id>' adds an entity to a dashboard menu. For destructive commands add '--yes' to skip confirmation prompts. Add '--json' where supported for machine-readable output."
    • removedInput schema / title
      Removed value: -"cli"
  2. First observedv0.2.6

TDQS

A4.6/5.0
Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations only flag openWorldHint and destructiveHint; the description goes far beyond that by naming the destructive command families (delete, expire, relink, pause), forbidding '--yes' on the user's behalf, mandating human execution of destructive pay commands, and prescribing dry-run-first workflows for import commands. No contradiction with the destructiveHint annotation—it explains it.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Front-loads purpose and the fallback routing before the command syntax and safety rules. Dense but every sentence carries a distinct constraint for a broad escape-hatch tool; minor redundancy with the schema's example list.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For an open-ended catch-all tool with no output schema, this covers what an agent must know: what it is, when to prefer siblings, exact argument format, and the safety/dry-run obligations for destructive and project-mutating subcommands.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the schema already documents the single command parameter, including the 'do not include anythink or --profile' rule. The description largely restates that with different examples, adding only the --json hint, so the baseline 3 applies.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

States a specific verb+resource ('Run any Anythink CLI command and return its output') and immediately positions itself against the many dedicated siblings by declaring itself the fallback ('Prefer the dedicated tools; use this for anything they don't cover'). Concrete examples ('entities list', 'data list posts') make the intent unambiguous.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly says when to use it (anything the dedicated tools don't cover) and when not to (prefer dedicated tools). Adds further conditional guidance: which destructive commands a human must run, and the --dry-run-then-approve protocol for 'data import' and 'import directus'.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Deploy Server

Other Tools