
DIVIOPS AGENT
DiviOps Agent compatibility with REEID Translate
DiviOps Agent compatibility with REEID Translate is being reviewed using official plugin documentation. Provides a WordPress-side REST bridge for the DiviOps MCP server, exposing authenticated REST endpoints under `/diviops/v1/*` for MCP clients. No specific text shown to visitors is currently confirmed for translation.
AWAITING VERIFICATION
What DiviOps Agent does
Official plugin information supports the compatibility context documented for this category.
MANUAL REVIEW
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
DiviOps Agent is documented in the Other category with 7 documented features.
DOCUMENTATION REVIEW
We use official plugin documentation to describe what the plugin does. Translation support is listed only for text that can be identified and tested.
COMPATIBILITY REVIEW
How DiviOps Agent compatibility is evaluated
01 · Review official plugin documentation
Confirm documented plugin behaviour before making multilingual compatibility claims.
02 · Identify text shown to visitors
Check whether the documented features display text that visitors can read.
03 · Separate content from functionality
Structure, settings, logic, integrations and runtime behaviour are not treated as translatable content unless they include specific visible text.
04 · Confirm what can be translated
List supported content only after specific text shown to visitors has been identified and can be validated.
PLUGIN INFORMATION
What the plugin does
Plugin capabilities
- Provides a WordPress-side REST bridge for the DiviOps MCP server, exposing authenticated REST endpoints under `/diviops/v1/*` for MCP clients.
- Requires WordPress Application Password authentication for all REST endpoints.
- Targets Divi 5; when Divi is not active, authenticated requests return a `divi_unavailable` error.
- Implements permission gating by capability: read endpoints generally require `edit_posts`, write endpoints generally require `edit_pages`, and administrative surfaces (e.g., preset/variable management) require `manage_options`.
- Supports Divi-related authoring/inspection workflows via the MCP server, including schema inspection, block validation, design-token management, preset audits, and safe read-only diagnostics (as described in the plugin README).
- Does not function without the MCP server: the plugin is the REST bridge while the separately distributed `@diviops/mcp-server` package is the client-facing MCP layer.
- Does not add analytics or tracking; it exposes authenticated REST endpoints and the data read/written depends on the selected MCP tools, the WordPress user permissions, and installed DiviOps plugin capabilities.
TRANSLATION BOUNDARY
DiviOps Agent capabilities and translatable content are documented separately.
Official documentation describes the plugin functionality, but does not currently identify specific text shown to visitors that can be translated.
A feature is not considered translatable unless it includes text that users can read.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
FREQUENTLY ASKED QUESTIONS
DiviOps Agent and REEID Translate FAQ.
What does DiviOps Agent do?
DiviOps Agent has 7 documented features listed in its official documentation. See the Plugin Information section for details.
Does DiviOps Agent have any content currently confirmed for translation?
No specific content is currently confirmed for translation in this integration.
What needs to be confirmed before translating content from DiviOps Agent?
Official documentation must identify specific text, such as labels, titles, descriptions or messages, that can be tested in the integration.
RELATED GUIDES
Explore more compatibility guides.
COMPATIBILITY INFORMATION
Evaluate DiviOps Agent in a multilingual WordPress workflow.
REEID documents DiviOps Agent functionality separately from confirmed translation support so the distinction is clear.
Supported content will be listed when specific translatable text is identified in the official documentation.