English Français العربية

io.github.theshajha/wovo

Official registry Cloud and DevOps

Deploy HTML from any AI tool to a versioned, shareable library on wovo.dev; manage pages.

Source code Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

NPM package @gowovo/wovo
Claude Code 
claude mcp add wovo -e 'WOVO_TOKEN=<your wovo_token>' -e 'WOVO_WORKSPACE=<WOVO_WORKSPACE>' -- npx -y @gowovo/wovo@0.2.2 -y -p @gowovo/wovo wovo-mcp
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "wovo": {
            "command": "npx",
            "args": [
                "-y",
                "@gowovo/wovo@0.2.2",
                "-y",
                "-p",
                "@gowovo/wovo",
                "wovo-mcp"
            ],
            "env": {
                "WOVO_TOKEN": "<your wovo_token>",
                "WOVO_WORKSPACE": "<WOVO_WORKSPACE>"
            }
        }
    }
}

Environment variables

  • WOVO_TOKEN required secret Workspace deploy token (wv_…) from wovo.dev settings.
  • WOVO_WORKSPACE Target workspace slug (optional; the token resolves a default).

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. wovo
  2. Install
  3. Connect (recommended)
  4. CLI
  5. MCP server
  6. Requirements
  7. License

wovo

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.

Install

Run it one-off with npx:

npx @gowovo/wovo deploy ./report.html

Or install globally and use the wovo command:

npm i -g @gowovo/wovo
wovo deploy ./report.html

One command — it opens your browser to sign in, then wires up your AI tool. No token to copy.

npx @gowovo/wovo setup

From then on, just tell your agent "deploy this to Wovo" and the page lands in your library.

Manual auth (CI / headless)

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:

export WOVO_TOKEN="wv_…"
export WOVO_WORKSPACE="my-workspace"

CLI

wovo setup               # connect your AI tool: browser sign-in + skill + MCP + test deploy
                         #   --scope project|user        this project, or every project on this machine
                         #   --behavior auto|ask|manual  publish automatically, offer first, or only on request
wovo deploy <file|dir>   # deploy one .html, or every .html under a folder
wovo list                # list pages in the workspace
wovo pages archive <slug>          # hide a page from the library (link still works)
wovo pages unarchive <slug>        # restore an archived page
wovo pages move <slug> --space S   # change a page's space
wovo pages rename <slug> <new>     # change a page's path; old links redirect
wovo domains list                  # custom domains
wovo domains add <d> --page <slug> # link a domain (prints DNS records)
wovo domains status <d>            # re-check DNS / verification
wovo domains remove <d>            # unlink a domain
FlagDefaultWhat it does
--workspace Wenv WOVO_WORKSPACE, else resolved from the tokenTarget workspace
--space Stop folder nameGroup pages under a space
--tool TcliSource-tool tag
--slug Sderived from pathExplicit slug (single-file deploys)
--url Uenv WOVO_URL or https://wovo.devWovo base URL
--token Tenv WOVO_TOKENDeploy token

Config resolution: CLI flags → ./wovo.json → env (WOVO_URL, WOVO_TOKEN, WOVO_WORKSPACE).

// wovo.json
{ "workspace": "my-workspace", "token": "wv_…", "space": "reports" }
Examples
WOVO_TOKEN=… wovo deploy ./report.html --workspace acme
wovo deploy ./site --workspace acme --tool claude-code
wovo list --workspace acme

MCP server

wovo also ships an MCP server (wovo-mcp) so AI agents can deploy and list pages as tools. Register it with Claude Code:

claude mcp add wovo \
  --env WOVO_TOKEN=wv_… \
  --env WOVO_WORKSPACE=my-workspace \
  -- npx -y -p @gowovo/wovo wovo-mcp

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.

Requirements

Node.js >= 18 (uses the global fetch). Zero dependencies for the CLI; the MCP server uses @modelcontextprotocol/sdk and zod.

License

MIT © Shashank Jha

Frequently asked questions

What is io.github.theshajha/wovo?

Deploy HTML from any AI tool to a versioned, shareable library on wovo.dev; manage pages.

How do I install io.github.theshajha/wovo?

It runs on your machine. In Claude Code: claude mcp add wovo -e 'WOVO_TOKEN=<your wovo_token>' -e 'WOVO_WORKSPACE=<WOVO_WORKSPACE>' -- npx -y @gowovo/wovo@0.2.2 -y -p @gowovo/wovo wovo-mcp. For other clients, paste the JSON configuration from this page into their MCP settings.

Does io.github.theshajha/wovo need an API key?

Yes. It expects WOVO_TOKEN, which you set in its configuration.

Is io.github.theshajha/wovo open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains io.github.theshajha/wovo?

It is published by theshajha. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.