MCPDO — AI Operations
MCPDO finds bounded WooCommerce operational issues, preserves the evidence behind each finding, and lets supported AI clients prepare exact product fixes without bypassing WordPress permissions or human approval. Free V1 focuses on one complete outcome loop: find it → prove it → preview a fix → appr
MCPDO finds bounded WooCommerce operational issues, preserves the evidence behind each finding, and lets supported AI clients prepare exact product fixes without bypassing WordPress permissions or human approval.
Free V1 focuses on one complete outcome loop: find it → prove it → preview a fix → approve → apply → verify → recover when safe.
- Run a read-only Store Health Audit.
- Review deterministic findings with evidence, method, limitations, and evidence quality.
- Preview exact reversible product changes before anything is written.
- Update supported product name, short/full description, publication status, categories, tags, existing-media featured image, and inventory fields.
- Require explicit approval before every supported write.
- Verify the observed result independently after the write.
- Recover only the captured MCPDO fields when recovery is still safe and no newer merchant edit would be overwritten.
- Restrict every connection with granular scopes and per-tool switches.
- Review an immutable operational activity timeline.
MCPDO does not claim conversion or revenue causality from the V1 audit signals. Product content, inventory, pending/failed order status, coupons, and supported WooCommerce configuration values are reported as observations only.
WooCommerce is not required to activate MCPDO. When WooCommerce is unavailable or below the supported commerce boundary, MCPDO remains active and reports commerce features as unavailable.
Safety by default
- Global writes are off by default.
- Free V1 writes are limited to the explicit reversible WooCommerce product-field allowlist; arbitrary WordPress, PHP, SQL, shell, filesystem, order, customer, or financial mutation is not exposed.
- Preview, permission checks, approval, verification, and recovery rules remain server-authoritative.
