Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@wovo-mcp deploy ./report.html with space 'weekly'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
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:
npx @gowovo/wovo deploy ./report.htmlOr install globally and use the wovo command:
npm i -g @gowovo/wovo
wovo deploy ./report.htmlRelated MCP server: webserver-mcp
One command — it opens your browser to sign in, then wires up your AI tool. No token to copy.
npx @gowovo/wovo setupFrom 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:
export WOVO_TOKEN="wv_…"
export WOVO_WORKSPACE="my-workspace"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 domainFlag | Default | What it does |
| env | Target workspace |
| top folder name | Group pages under a space |
|
| Source-tool tag |
| derived from path | Explicit slug (single-file deploys) |
| env | Wovo base URL |
| env | Deploy token |
Config resolution: CLI flags → ./wovo.json → env (WOVO_URL, WOVO_TOKEN, WOVO_WORKSPACE).
// wovo.json
{ "workspace": "my-workspace", "token": "wv_…", "space": "reports" }WOVO_TOKEN=… wovo deploy ./report.html --workspace acme
wovo deploy ./site --workspace acme --tool claude-code
wovo list --workspace acmewovo 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-mcpTools: 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
This server cannot be installed
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
Publish HTML, files, or a URL to a permanent public URL, then update it — from any MCP agent.
Screenshot, diff, audit and sitemap-capture any web page — 5 MCP tools for AI agents.
Publish AI-generated HTML & Markdown to a hosted, shareable URL via MCP.
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/theshajha/wovo-cli'
If you have feedback or need assistance with the MCP directory API, please join our Discord server