Orivox AI Website Builder

Most tools are clearly separated by domain (project lifecycle, page editing, domains, backend, database, assets). The only minor overlap is between create_new_site and replace_page, though their descriptions explicitly differentiate index.html (create_new_site) from non-index pages (replace_page). apply_dom_ops is also distinct from the wholesale-rewrite tools.

Most tools follow a consistent verb_noun pattern: create_project, create_page, create_new_site, create_backend, create_database, delete_page, delete_project, delete_asset, delete_backend, list_projects, list_domains, list_backend_files, read_page, read_backend_file, write_asset, write_backend_file, publish_website, unpublish_website, check_domain, search_domains. A few use different patterns like apply_dom_ops, build_site, get_preview_url, get_project_context, validate_project, whoami, but these are still recognizable and not chaotic.

38 tools is on the heavy side for a website builder MCP server, but the scope is broad: website building, page editing, backend/database management, domains, publishing, account info, and image uploads. The count is high but justifiable given the breadth of the domain.

The tool surface covers the full website lifecycle: create project/page/site, read pages, update via apply_dom_ops or create_new_site/replace_page, delete pages/projects/assets/backends, publish/unpublish, domain search/purchase/connect, backend file management, database querying, image upload/list, validation, and account/version info. There are no obvious dead ends or missing lifecycle operations.