Revdoku MCP server
{
"mcpServers": {
"revdoku": {
"type": "http",
"url": "https://app.revdoku.com/mcp"
}
}
}{
"mcpServers": {
"revdoku": {
"type": "http",
"url": "https://app.revdoku.com/mcp"
}
}
}{
"mcpServers": {
"revdoku": {
"type": "http",
"url": "https://app.revdoku.com/mcp"
}
}
}{
"servers": {
"revdoku": {
"type": "http",
"url": "https://app.revdoku.com/mcp"
}
}
}{
"mcpServers": {
"revdoku": {
"type": "http",
"url": "https://app.revdoku.com/mcp"
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsonversion 1.0.1
What it does
Revdoku is a website publishing platform that allows AI agents to create, update, and manage live websites without requiring user accounts. It provides hosting, analytics, built-in forms, and file versioning, accessible through an MCP server for direct integration with AI assistants.
- Ask an AI agent to publish a landing page, waitlist, or portfolio and get a live URL within seconds.
- Build client deliverables like password-protected presentations or project portals that AI agents can update while keeping the same public link.
- Collect form submissions and analytics on published sites directly through an AI agent without setting up a separate backend.
Tools this server exposes
| Tool | Does |
|---|---|
| publish_website | Publish or update a website from files or a local folder and receive a live public URL. |
| get_analytics | Retrieve visitor statistics, page engagement, and download metrics for a published website. |
| manage_forms | Create and manage built-in contact, signup, or feedback forms on a website and retrieve submissions. |
| list_projects | List all published websites and projects associated with the account. |
| get_project_details | Retrieve metadata and settings for a specific published website or project. |
| download_files | Download all files associated with a published website for backup or export. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.