DIVIOPS AGENT
DiviOps Agent compatibility with REEID Translate
DiviOps Agent compatibility with REEID Translate is being evaluated from available plugin evidence. Provides a WordPress-side REST bridge for the DiviOps MCP server, exposing authenticated REST endpoints under `/diviops/v1/*` for MCP clients. No specific visitor-facing translation surface is currently confirmed.
AWAITING VERIFICATION
What the available evidence establishes for DiviOps Agent.
Official plugin information supports the compatibility context documented for this category.
AWAITING VERIFICATION
This integration has not yet been manually verified by REEID.
PLUGIN PROFILE
DiviOps Agent is documented in the Other category with 7 concrete capabilities identified in the current evidence.
EVIDENCE COVERAGE
Plugin capabilities are documented from available official evidence. Translation support is listed only when concrete visitor-facing content is explicitly established.
COMPATIBILITY REVIEW
How DiviOps Agent compatibility is evaluated
01 · Review official plugin evidence
Establish documented plugin behaviour before making any multilingual compatibility claim.
02 · Identify visitor-facing content
Determine whether the documented behaviour exposes human-readable values that visitors can see.
03 · Separate content from functionality
Keep structure, configuration, logic, integrations and runtime behaviour outside translation scope unless concrete content values are identified.
04 · Confirm translation scope
Publish supported content only when concrete visitor-facing values are explicitly established and can be validated.
PLUGIN INTELLIGENCE
What the official plugin evidence shows
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.
CONTENT BOUNDARY
DiviOps Agent capabilities and translation scope are documented separately.
The available evidence documents plugin functionality, but does not currently establish a specific visitor-facing translation surface.
Functional capability alone is not treated as evidence that a value should be translated.
LIMITATIONS & QA
Verification notes
- This integration is documented for compatibility context. Visitor-facing translation scope is not listed for this category.
COMMON QUESTIONS
DiviOps Agent and REEID Translate FAQ.
What does DiviOps Agent do according to the available plugin evidence?
DiviOps Agent has 7 concrete capabilities documented from the currently available official plugin evidence. See the Plugin Intelligence section for the individual capabilities.
Is a REEID translation surface currently confirmed for DiviOps Agent?
No specific visitor-facing content values are currently confirmed as an evidence-backed translation surface for this integration.
What would establish translation scope for DiviOps Agent?
The evidence must identify concrete visitor-facing values such as labels, titles, descriptions, messages or other human-readable content that can be validated through the integration workflow.
RELATED GUIDES
Continue through the compatibility library.
INTEGRATION EVIDENCE
Evaluate DiviOps Agent in a multilingual WordPress workflow.
REEID documents DiviOps Agent functionality separately from evidence-backed translation support so compatibility claims remain specific and testable.
Translation scope will be published when concrete visitor-facing content is established by evidence.