Terminal
Terminal/Skill
Installs the zilliz-cli, logs you in to Zilliz Cloud, and sets which cluster your commands target.
By Zilliz (Milvus)
Works with
npx skills add zilliztech/zilliz-plugin --skill setupBefore running any zilliz-cli command, verify the following in order:
curl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash to ensure the latest version is installed.zilliz auth status. If not logged in, guide through login (see below).zilliz context current. If no context, guide through context setup.curl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash
Verify installation:
zilliz --version
IMPORTANT: Login commands (zilliz login, zilliz configure) require an interactive terminal and CANNOT run inside Claude Code. Always instruct the user to run these in their own terminal.
Check if already logged in:
zilliz auth status
If not logged in, tell the user to open their own terminal and run one of the following:
Option 1: Browser-based login (OAuth) — full feature access
zilliz login
--no-browser in headless environments (displays a URL to visit manually)Option 2a: API Key via login command
zilliz login --api-key
Option 2b: API Key via configure (legacy)
zilliz configure
Option 3: Environment variable
User can add to their shell profile (.zshrc / .bashrc):
export ZILLIZ_API_KEY=<your-api-key>
After the user completes authentication, verify by running:
zilliz auth status
zilliz configure # Interactive API key setup
zilliz configure list # Show all config values
zilliz configure set <key> <value> # Set a config value
zilliz configure get <key> # Get a config value
zilliz configure clear # Clear all credentials
These commands require an interactive terminal. Instruct the user to run in their own terminal:
# Interactive selection
zilliz auth switch
# Direct switch by org ID
zilliz auth switch <org-id>
zilliz logout
Data-plane commands (collection, vector, index, etc.) require an active cluster context.
# Set by cluster ID (endpoint auto-resolved)
zilliz context set --cluster-id <cluster-id>
# Set with explicit endpoint
zilliz context set --cluster-id <cluster-id> --endpoint <url>
# Change database (default: "default")
zilliz context set --database <db-name>
zilliz context current
All zilliz-cli commands support --output json for structured, machine-readable output. Use this when you need to parse results programmatically:
zilliz cluster list --output json
zilliz collection describe --name <name> --output json
Available formats: json, table, text. Default is text.
Different cluster types have different feature support:
| Feature | Free | Serverless | Dedicated |
|---|---|---|---|
| Collection CRUD | Yes | Yes | Yes |
| Vector search/query | Yes | Yes | Yes |
| Database create/drop | No | No | Yes |
| User/role management | No | Limited | Yes |
| Backup management | No | Yes | Yes |
| Cluster modify | No | No | Yes |
When a command fails with a permissions error, check the cluster type first — the feature may not be available on that cluster type.
~/.local/bin) is in your PATH. Try re-running the install script: curl -fsSL https://raw.githubusercontent.com/zilliztech/zilliz-cli/master/install.sh | bash.zilliz auth status to check login state. Tokens may have expired — re-run login in your own terminal.zilliz context current to verify. If the cluster was deleted or suspended, set a new context with zilliz context set --cluster-id <id>.zilliz cluster describe --cluster-id <id>. Suspended clusters reject data-plane requests.zilliz login, zilliz configure, or zilliz auth switch (without arguments) inside Claude Code — they require interactive input. Always instruct the user to run these in their own terminal.zilliz auth status.zilliz context current.