The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Wovo listing page.
Deploy any HTML — from any AI tool or your terminal — to a versioned, shareable library. wovo is the CLI and MCP server for wovo.dev.
Every deploy snapshots a new version, returns a live URL, and files the page in your workspace library. Re-deploying the same slug never overwrites — it appends a version you can roll back to.
Run it one-off with npx:
Or install globally and use the wovo command:
One command — it opens your browser to sign in, then wires up your AI tool. No token to copy.
From then on, just tell your agent "deploy this to Wovo" and the page lands in your library.
When there's no browser (CI, a server), provide a deploy token from your workspace settings on wovo.dev via env, a config file, or --token:
| Flag | Default | What it does |
|---|---|---|
--workspace W | env WOVO_WORKSPACE, else resolved from the token | Target workspace |
--space S | top folder name | Group pages under a space |
--tool T | cli | Source-tool tag |
--slug S | derived from path | Explicit slug (single-file deploys) |
--url U | env WOVO_URL or https://wovo.dev | Wovo base URL |
--token T | env WOVO_TOKEN | Deploy token |
Config resolution: CLI flags → ./wovo.json → env (WOVO_URL, WOVO_TOKEN, WOVO_WORKSPACE).
wovo also ships an MCP server (wovo-mcp) so AI agents can deploy and list pages as tools. Register it with Claude Code:
Tools: wovo_deploy (inline html or a file path), wovo_list, wovo_pages_archive,
wovo_pages_unarchive, wovo_pages_move, wovo_pages_rename, wovo_domains_list,
wovo_domains_add, wovo_domains_remove, wovo_domains_status.
Node.js >= 18 (uses the global fetch). Zero dependencies for the CLI; the MCP server uses @modelcontextprotocol/sdk and zod.
MIT © Shashank Jha