mcpField
W
wovo

wovo

Local
github.com/theshajhaCloud & Infra0Updated 17w ago

About wovo

wovo is a CLI and MCP server for publishing HTML to a versioned, shareable library on wovo.dev. It supports deployments from AI tools or a terminal, with page management and rollback through saved versions.

Key features

  1. 01Deploy HTML from files or inline content
  2. 02Save each deployment as a version
  3. 03List and manage workspace pages
  4. 04Archive, move, and rename pages
  5. 05Manage workspace domains

Use cases

  1. 01Publish an AI-generated HTML report
  2. 02Deploy multiple HTML files from a folder
  3. 03Restore an earlier page version
  4. 04Manage pages and domains for a workspace

MCP support

The MCP server exposes tools to deploy and list pages, manage page status and names, and handle workspace domains.

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"theshajha-wovo": {
"command": "npx",
"args": [
"-y",
"@gowovo/wovo"
],
"env": {
"WOVO_TOKEN": "<WOVO_TOKEN>",
"WOVO_WORKSPACE": "<WOVO_WORKSPACE>"
}
}
}
}
Run commandnpx -y @gowovo/wovo
Environment variables to set
WOVO_TOKENSecretWorkspace deploy token (wv_…) from wovo.dev settings.
WOVO_WORKSPACETarget workspace slug (optional; the token resolves a default).

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@gowovo/wovo0.2.2

Tools

10

Saved tool list · updated 2w ago

ParameterTypeRequiredDescription
htmlstringNoInline HTML content to deploy.
pathstringNoPath to an .html file to read and deploy.
slugstringNoStable slug for the page (else derived from title).
toolstringNoSource-tool tag (default 'claude-code').
spacestringNoGroup/space to file the page under, e.g. 'reports'.
titlestringNoHuman title (else taken from <title>).
accessenumNoPage visibility. Defaults to 'private' for agent deploys — only the workspace owner can view it. Use 'public' only when the user explicitly wants a shareable link.private | team | public | password
workspacestringNoWorkspace (defaults to WOVO_WORKSPACE).

Details

From the project README

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

Connect (recommended)

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

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.