Deploying from an assistant is convenient; being able to read the build log and roll back in the same thread is what makes it safe to do. The split between hosted and local-only tools is worth noting up front — scaffolding a project and deploying a local directory need filesystem access, so they will not work from a client running somewhere else.
The OpZero CLI and the MCP server that ships with it. The server exposes 26 tools that let an assistant deploy sites, manage projects, roll back a bad release and read build logs, using the same credentials as the command-line tool.
- Six ways to deploy, matched to what you have — `quick_deploy` for files with minimal configuration, `deploy_website` for a full directory, `deploy_artifact` for a React component, `deploy_markdown` for a styled page from Markdown, `deploy_themed`, and `update_deployment` for an existing one
- Project management — `list_projects`, `create_project`, `project_delete`, `project_archive` and `project_cleanup` for finding stale or duplicated projects
- Deployment history you can act on — `list_deployments` and `get_deployment` to inspect, `redeploy` to push the latest again, `rollback_deployment` to go back, `get_build_logs` when a build fails, `delete_deployment` to remove one
- `set_custom_domain` to attach a domain, and `get_template` for template details
- Four tools that need local filesystem access: `deploy_local_dir`, `init_project` to scaffold from a template, `open_project`, and `whoami`
- Platform helpers — `help`, `ask_agent` and `get_system_status`
An OpZero account and an API key from the dashboard. Authenticate once with `opzero login`, or pass `OPZERO_API_KEY` in the server's environment. The client runs `opzero mcp` if the CLI is installed globally, or `npx @opzero/mcp` if not; the MCP server is also published on its own as `@opzero/mcp`, runnable as `opzero-mcp`.
One command plus a key — npm install -g opzero, then supply credentials