Wovo

io.github.theshajhaPublished by GitHub account theshajhav0.2.2Updated Oct 25, 2026

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

VerifiedSTDIODesktop onlyFiles & Storage Developer Tools

Server details

Identifier: io.github.theshajha/wovo
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account theshajha for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.theshajha%2Fwovo.svg)](https://sourceweft.com/mcp/io.github.theshajha%2Fwovo?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Wovo is a local MCP server that lets an AI assistant deploy HTML pages to a versioned, shareable library on wovo.dev and manage those pages.

What you can do: Deploy inline HTML or a file path as a new versioned page and get a live URL back, with re-deploys appending versions rather than overwriting. List pages in a workspace. Archive, unarchive, move between spaces, or rename pages, with old links redirecting. List custom domains, add a domain to a page, check DNS verification status, and remove domains.
When to use it: Useful when you want an assistant to publish HTML it generates — reports, dashboards, prototypes — to a hosted, shareable link without a separate deploy step, and to keep a versioned library of those pages.
Requirements: Runs locally via npx with Node.js 18 or newer. Needs a wovo.dev workspace and a deploy token supplied through the WOVO_TOKEN environment variable; WOVO_WORKSPACE optionally selects the target workspace. Network access to wovo.dev is required.

Before you install

The deploy token (WOVO_TOKEN) is a workspace credential and should be kept out of shared configs and repositories. Deploying publishes HTML to a live URL, and page operations such as archive, move, rename and domain changes alter the workspace library; domain changes also involve DNS records you must configure yourself.

Installation

In SourceWeft

Open Wovo in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

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:

Or install globally and use the wovo command:

Connect (recommended)

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.

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:

CLI

bash

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 requestwovo deploy <file|dir>   # deploy one .html, or every .html under a folderwovo list                # list pages in the workspacewovo pages archive <slug>          # hide a page from the library (link still works)wovo pages unarchive <slug>        # restore an archived pagewovo pages move <slug> --space S   # change a page's spacewovo pages rename <slug> <new>     # change a page's path; old links redirectwovo domains list                  # custom domainswovo domains add <d> --page <slug> # link a domain (prints DNS records)wovo domains status <d>            # re-check DNS / verificationwovo domains remove <d>            # unlink a domain

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 requestwovo deploy <file|dir>   # deploy one .html, or every .html under a folderwovo list                # list pages in the workspacewovo pages archive <slug>          # hide a page from the library (link still works)wovo pages unarchive <slug>        # restore an archived pagewovo pages move <slug> --space S   # change a page's spacewovo pages rename <slug> <new>     # change a page's path; old links redirectwovo domains list                  # custom domainswovo domains add <d> --page <slug> # link a domain (prints DNS records)wovo domains status <d>            # re-check DNS / verificationwovo domains remove <d>            # unlink a domain

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).

Examples

bash

WOVO_TOKEN=… wovo deploy ./report.html --workspace acmewovo deploy ./site --workspace acme --tool claude-codewovo list --workspace acme

WOVO_TOKEN=… wovo deploy ./report.html --workspace acmewovo deploy ./site --workspace acme --tool claude-codewovo 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:

bash

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

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

Source: README.md at commit d16c9ff

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.2.2LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts