zxcv

The command-line interface for working on a ZXCV project from any editor or coding agent. It links a local directory to a project, runs a local preview, pushes schema and env, and ships versioned deploys to the edge.

Install

npm i -g zxcv

zxcv login

Authenticate the CLI with your ZXCV account. Run this once per machine.

zxcv login

zxcv link <project>

Link the current directory to a project. This pulls the project’s typed schema so your SDK queries autocomplete and return typed rows.

zxcv link acme-store

zxcv dev

Run a local preview against the dev instance. Use it to work on your app with live data before you ship a version.

zxcv dev

zxcv deploy

Build a new version and get a preview URL. Add flags to promote or canary it.

zxcv deploy              # new version + preview URL
zxcv deploy --prod       # promote to your production domain
zxcv deploy --canary 10  # route 10% of traffic, auto-promote on clean metrics

zxcv db push / zxcv db pull

Sync your database schema. pull brings the current schema down and regenerates SDK types; push applies your local changes as an expand/contract migration.

zxcv db pull   # sync schema + regenerate SDK types
zxcv db push   # apply local schema changes as a migration

zxcv env pull / zxcv env push

Sync environment variables between your project and your local .env.

zxcv env pull   # download project env vars locally
zxcv env push   # upload local env vars to the project

zxcv logs

Stream logs from your project.

zxcv logs

zxcv domains add <domain>

Add a custom domain to your project, or register one through the in-console registrar. DNS and TLS are wired for you.

zxcv domains add app.acme.com

zxcv mcp

Share full project context — schema, policies, and deployments — with Claude Code, Codex, or any MCP-aware editor, so a coding agent can work against your real project.

zxcv mcp

Next steps

• Deploy — versions, previews, canaries, and rollback
• SDK reference — the typed client zxcv link generates
• Database — author schema migrations for db push