Quick answer
DiviOps combines a WordPress plugin, an MCP server and an authoring skill to help a compatible AI client edit native Divi 5 content. Install and verify all required components on an approved development or staging site first. A successful connection or page listing alone does not prove that the current session can author valid, editable Divi modules.
Applies to
Interactive Online customers using Divi 5 who have permission to install the required software and configure a separate AI client. DiviOps is a third-party project, independent of Elegant Themes' built-in Divi AI Agent. Follow the supported versions and capabilities of the published packages you actually install. Divi licensing, AI usage and optional paid DiviOps components are separate requirements.
Understand the three components and current names
The DiviOps Agent plugin runs in WordPress. The DiviOps MCP server runs in the AI client's environment and communicates with WordPress. The authoring skill teaches the client the supported Divi data format and workflow. Updating the WordPress plugin does not update a manually installed skill.
The current public authoring skill is named diviops-divi-5. Older installations may show divi-5-builder; the Claude marketplace package still uses divi-5-builder@diviops. Check the actual discovered skill and published migration instructions before replacing anything. Preserve local edits outside discovery folders and avoid two active builder copies.
1. Review requirements and install the components
- Read the publisher's setup guide, WordPress.org plugin page and release notes. Use a published compatible release rather than treating unreleased source notes as an available download. Keep a recovery checkpoint for the approved test site.
- Install the Free DiviOps Agent from its WordPress.org listing or the publisher's documented download through Plugins > Add New Plugin. Activate it only on the agreed site. Optional Pro features require their separate licensed components.
- Check the MCP server's runtime requirements. The current successor server documentation requires Node.js 22 or newer on the client host. Follow the publisher's current supported setup rather than installing a server on cPanel by default.
- Have the owner approve the WordPress user, required operations and credential handling. Create a dedicated Application Password through Users > Profile > Application Passwords when that supported method is chosen. Enter it in the client's private configuration, keep it out of chat and public files, and record how to revoke it. Application Password access follows its user's effective permissions; a credential name does not restrict access to one page.
- Register the MCP server using the publisher's client-specific instructions, your own HTTPS site URL and private credentials. Review exposed tools and optional command permissions before allowing writes.
2. Load the authoring skill
For Claude Code, the publisher documents these terminal commands:
claude plugin marketplace add oaris-dev/diviops
claude plugin install divi-5-builder@diviopsFor Codex or a manual installation, use the publisher's current skill distribution and the client's supported skill location. Include its required primer and referenced files. Confirm diviops-divi-5 is visible in a fresh or reloaded session; having the new folder on disk does not prove an already-running conversation has read it.
3. Inspect, then try a bounded native edit
Use the installed DiviOps authoring skill.
Inspect the approved staging site and one existing draft page.
Report the site identity, component versions, available capabilities,
page ID and target Text module without changing anything.
Propose a shorter Services introduction using my supplied facts.
Preserve native modules, presets, globals, links and other pages.
Do not publish or substitute a large HTML/Code module.After reviewing that inspection, approve one draft-only change. Use a preview or dry run when the operation supports it. Check the changed native module in the Divi Visual Builder, inspect phone/tablet layouts, and prove the supported rollback before approving publication. Preserve the site's files and database separately; a layout snapshot does not replace a full backup.
Troubleshooting and access removal
For missing capabilities, compare the installed plugin/server/skill versions and the site's advertised support. For authorization errors, inspect the user's permissions and HTTPS/authentication setup. Avoid turning on broad command allowances to bypass a refusal. If content stops being natively editable, stop and recover the scoped revision. To end access, revoke the dedicated Application Password, remove or disable the client's connection, and verify that a fresh authenticated request is rejected.
When to contact support
Contact Interactive Online when the hosting account, WordPress installation, document root or available access method is unclear. Provide the affected page URL, tool and plugin versions, time and time zone, and the exact redacted error. Exclude passwords, Application Passwords, keys, tokens, cookies and customer records. Skill publishers handle their own installation defects and feature requirements; AI subscriptions, paid builders and connector licenses are separate from hosting.
Related help
- AI skill installation and discovery
- Elegant Themes built-in Divi AI Agent
- Review connector permissions before writes
- Recover a WordPress page revision
Documentation and downloads
- DiviOps public repository, skill names and releases
- DiviOps setup, authentication and client instructions
- DiviOps Agent download and published requirements
- Elegant Themes documentation for its separate Divi AI Agent
Documentation and source review by Interactive Online: November 2, 2026. Installation sources and instructions were reviewed. A new installation or connected editing test was not performed for this article; confirm the versions, tools and permissions available in your own environment.
