Craft Anything CLI command notes
Documented syntax: v0.3.0

Check the CLI version
craft-anything-cli --version
Confirm which executable your terminal is using before following a command example.
Check: A version identifier. Compare it with the release whose instructions you are following.

Read the command overview
craft-anything-cli --help
See the flags and subcommands supported by your own installed version.
Check: Usage, global options and available subcommands. Read this before copying flags from a different version.

List the available tools
craft-anything-cli commands
Find tool names grouped by toolset before choosing one to inspect.
Check: Tool names and descriptions. Choose a specific tool name, then inspect its help before calling it.

Inspect this install’s capabilities
craft-anything-cli capabilities
See toolsets, tool availability and engine information for this installation.
Check: A capability report for this installation. Use it to identify missing engines or unavailable toolsets.

Read the installation health report
craft-anything-cli --format text doctor
Check registrations, engines, AI backends and the MCP server in a readable format.
Check: Checks marked ok, warn, FAIL or info, with remediation where supplied. A missing AI backend matters for building, while other inspection tasks can still be available.

Read one tool’s arguments
craft-anything-cli core-session-show --help
Learn the required inputs before sending a tool request.
Check: Usage and accepted arguments for the session-status tool. This command opens help; it does not show an actual session report.

Inspect the MCP server options
craft-anything-cli mcp --help
See how the CLI exposes tools to an external MCP client.
Check: Options for the installed MCP server. The server uses standard input/output; starting mcp normally waits for client requests rather than a chat prompt.

Preview client setup changes
craft-anything-cli setup --dry-run
Inspect the proposed registration changes before applying them.
Check: A setup plan showing what would change, without writing those changes. Review the named clients and paths.

Source: https://github.com/storytold/craft-anything/tree/v0.3.0
Guide: https://craft-anything.com/tools/