> Publish a website from OpenClaw, protect it with a password, and keep updating the same live URL with Revdoku static hosting. # OpenClaw website hosting with Revdoku Build a static website in OpenClaw, publish it as a live link, control who can open it, and keep updating the same URL. Revdoku requires browser sign-in before storing files or creating a preview. Just ask to “publish to Revdoku” to publish your HTML pages presentation dashboard app prototype game prototype as a fast and secure website from your Codex , Claude or another AI app publish files or folders Connect Skill MCP Paste this into your AI app. Copy Install the Revdoku skill in your AI app. Copy npx skills add revdoku/revdoku --skill revdoku -g Choose your AI app to connect through MCP. Codex CLI Claude Code Other Copy codex mcp add revdoku --url https://app.revdoku.com/mcp codex mcp login revdoku Copy claude mcp add --transport http revdoku https://app.revdoku.com/mcp claude mcp login revdoku Transport Streamable HTTP Auth Browser OAuth Copy https://app.revdoku.com/mcp Open the MCP setup guide → Free · Public or protected · Visitor analytics · Forms and email alerts Building websites for clients? Explore Revdoku for agencies → ## Build → publish → protect → update the same URL Here is the complete workflow: 1. **Build.** Ask OpenClaw to create the site in a dedicated folder with an `index.html` file. 2. **Preview.** Ask it to run `revdoku preview `. Complete browser sign-in, creating a Free account if needed, then review the 15-minute preview. 3. **Publish.** Ask it to run `revdoku p ` when you want the main website live. 4. **Protect when needed.** In Revdoku, change Access to **Password** and save. Revdoku generates the website password; send it separately from the website link. 5. **Update.** Ask OpenClaw to edit the original folder and publish it again. The existing Revdoku binding updates the same URL. The preview is `noindex`, lasts 15 minutes, and does not change the main website or consume a live-site slot. A complete OpenClaw prompt: > Build a responsive static project-status website in a new folder. Save it to Revdoku as a private draft, create a temporary preview, and give me the preview URL. After I approve it, publish the main website. Keep the Revdoku binding in that folder so later revisions update the same URL. ## Recommended local OpenClaw workflow Use the local Revdoku client when OpenClaw can access the project folder. This route uploads HTML, CSS, JavaScript, images, fonts, PDFs, and other site assets together. After the first publish, keep using the same folder: ```sh cd path/to/site revdoku p ``` Do not remove the local Revdoku binding or ask OpenClaw to start a new website for every edit. The binding is what connects the folder to its existing Revdoku URL. ## Connect OpenClaw through hosted MCP OpenClaw can connect to Revdoku as a remote Streamable HTTP MCP server with OAuth: ```sh openclaw mcp set revdoku '{"url":"https://app.revdoku.com/mcp","transport":"streamable-http","auth":"oauth"}' openclaw mcp login revdoku openclaw mcp doctor revdoku --probe ``` After sign-in, ask OpenClaw to list the Revdoku tools and publish a one-page test site. Hosted MCP is useful for text-based site files and for updating an existing Revdoku website. A remote MCP connection cannot read arbitrary files from your computer. If the website includes local images, archives, fonts, or other binary files, use the local client. See [MCP website publishing with Revdoku](/mcp/) for more setup options. ## Verify password access After setting Access to Password: 1. Open the website in a private browser window. 2. Confirm the password screen appears. 3. Enter the password and verify the site loads. 4. Ask OpenClaw for a small revision and republish the original project. 5. Reload the same URL and confirm both the revision and password screen remain. Never put the password in the published files or in a public prompt. ## Static hosting boundaries Revdoku publishes static output. It hosts HTML, CSS, JavaScript, media, and documents, but it does not run a server-side application process. For a framework project, ask OpenClaw to create a production build and publish the generated static output directory. ## Common fixes ### OpenClaw returned a new URL Make sure it is editing and publishing the original bound folder, or selecting the original website through MCP. Publishing a different folder as a new website creates a different URL. ### The preview expired Authenticated previews expire after 15 minutes. Run the preview command again to refresh the same preview URL, or publish the main site when it is approved. ### Images are missing through MCP Use the local Revdoku client for a site with local binary assets. Remote MCP is best for text content and website management. ## Next steps - Follow [the same-URL OpenClaw update guide](/blog/how-to-update-an-openclaw-website-without-changing-its-url/). - Read the [MCP client setup guide](/mcp/). - Publish from [Codex](/codex/), [Claude](/claude/), or [ChatGPT](/chatgpt/). --- [View the canonical page](https://revdoku.com/openclaw/) · [Browse llms.txt](https://revdoku.com/llms.txt)