Install the AnyCap CLI

Install the AnyCap CLI to run media and web commands from a terminal, let an agent use the CLI, or start the local MCP server. The binary install does not require Node.js. You will need an AnyCap login before running authenticated capabilities.

Choose an installation method

Environment	Installation path
macOS or Linux shell	Use the binary install script below
Windows with Git Bash	Run the same script inside Git Bash
An environment with Node.js and npm	Install @anycap/cli globally
Manual installation	Choose the matching operating system and architecture from GitHub Releases

The script detects 64-bit x86 or ARM. It rejects 32-bit systems; the selected platform must also have a matching release asset. The shell examples on this page use macOS, Linux, or Git Bash syntax.

Recommended binary install

The install script selects the correct binary for macOS, Linux, or Windows through Git Bash:

curl -fsSL https://anycap.ai/install.sh | sh

The default non-root location is ~/.local/bin/anycap. The installer updates your shell profile when needed.

npm install

If your environment already standardizes on Node.js:

npm install -g @anycap/cli

Binary installation is usually faster to start and does not require a Node.js runtime.

GitHub Releases

Download a platform binary from AnyCap Releases, place it on PATH, and make it executable on Unix-like systems.

Verify the installation

anycap --version
anycap status

The version command confirms that the executable runs. anycap status checks account and service state; an unauthenticated result means the binary is installed but login is still required.

Log in and run your first task

anycap login
anycap status

Complete the browser authorization prompted by anycap login, then check status again. See authentication for credential configuration.

Continue with generate and share an image for a first CLI workflow, or MCP setup to connect an agent host.

Update

The CLI checks for updates automatically. To update immediately:

anycap update

Fix anycap: command not found

A newly installed binary may exist before the current shell reloads its profile.

On macOS or Linux:

ls -la ~/.local/bin/anycap
export PATH="$HOME/.local/bin:$PATH"
anycap status

In Git Bash on Windows, check ~/.local/bin/anycap.exe instead. Open a new terminal after the installer changes your profile. If an editor or MCP host still cannot find AnyCap, restart that application or configure the executable’s absolute path; its environment can differ from your terminal.

If that file does not exist, review the installer output for /usr/local/bin or a custom ANYCAP_INSTALL_DIR. If an older npm binary takes precedence, inspect the resolved path:

command -v anycap

Use the intended full path or put its directory earlier on PATH.