quick_deployLABSCO SUMMARY
Rollback is why this belongs in the chat rather than the terminal.
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.
What it is
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.
What you get
- Six ways to deploy, matched to what you have —
quick_deployfor files with minimal configuration,deploy_websitefor a full directory,deploy_artifactfor a React component,deploy_markdownfor a styled page from Markdown,deploy_themed, andupdate_deploymentfor an existing one - Project management —
list_projects,create_project,project_delete,project_archiveandproject_cleanupfor finding stale or duplicated projects - Deployment history you can act on —
list_deploymentsandget_deploymentto inspect,redeployto push the latest again,rollback_deploymentto go back,get_build_logswhen a build fails,delete_deploymentto remove one set_custom_domainto attach a domain, andget_templatefor template details- Four tools that need local filesystem access:
deploy_local_dir,init_projectto scaffold from a template,open_project, andwhoami - Platform helpers —
help,ask_agentandget_system_status
Requirements
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.
Setup effort
One command plus a key — npm install -g opzero, then supply credentials
USE CASES
01
Shipping a page without opening a terminal
Point the assistant at the directory or file and let it deploy, then hand back the live URL.
02
Publishing a component or a Markdown doc as a page
Deploy a React artifact or a Markdown file directly, with the styling applied for you.
03
Recovering from a bad release
Read the build logs, then roll back to the previous deployment in the same conversation.
04
Tidying an account that accumulated projects
Find the stale and duplicate projects, then archive or delete them.
26 tools
Listed in project docs. Your client may show a different list.
deploy_websitedeploy_artifactdeploy_themeddeploy_markdownupdate_deploymentlist_projectscreate_projectproject_deleteproject_archiveproject_cleanupget_deploymentlist_deploymentsredeployrollback_deploymentget_build_logsdelete_deploymentget_templateset_custom_domainhelpask_agentget_system_statusdeploy_local_dirinit_projectopen_projectwhoamiBEFORE YOU INSTALL
What to know first
Tools you get
26 tools named in the project's documentation.
Requires
- opzero on PATH (or npx for @opzero/mcp)
- An OpZero API key: run opzero login once, or set OPZERO_API_KEY in the server's env
Where it runs
All 4 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
npm install -g opzeroMCP Clients
Claude Code, Cursor
JSON
{
"mcpServers": {
"opzero": {
"command": "opzero",
"args": [
"mcp"
]
}
}
}Authenticate before your client starts the server: run opzero login once (API key or browser sign-in, the same credentials the CLI uses), or add an env entry setting OPZERO_API_KEY to your key from opzero.sh/dashboard/api-keys.
Windsurf
WINDSURF · JSON
{
"mcpServers": {
"opzero": {
"command": "npx",
"args": [
"@opzero/mcp"
]
}
}
}Authenticate before your client starts the server: run opzero login once (API key or browser sign-in, the same credentials the CLI uses), or add an env entry setting OPZERO_API_KEY to your key from opzero.sh/dashboard/api-keys.
GitHub Copilot in VS Code
GITHUB COPILOT IN VS CODE · JSON
{
"servers": {
"opzero": {
"command": "npx",
"args": [
"@opzero/mcp"
]
}
}
}Add this to .vscode/mcp.json in your workspace (or your user-level mcp.json). VS Code does not read a github.copilot.chat.mcpServers setting.
Authenticate before your client starts the server: run opzero login once (API key or browser sign-in, the same credentials the CLI uses), or add an env entry setting OPZERO_API_KEY to your key from opzero.sh/dashboard/api-keys.
