WordPress
Self-hosted WordPress and WooCommerce operations with evidence, exact previews, WordPress-admin approval, verification, and safe recovery.
MCPDO ecosystem
One AI operations layer. Multiple runtimes.
MCPDO gives AI clients bounded access to real work without collapsing every environment into one privileged agent. WordPress handles site operations, Local handles development work, and Cloud is the optional remote bridge.
Local
Files, Git, terminal, project quality, browser development tooling, Docker, and local WordPress development from the machine you control.
Cloud
Optional OAuth-protected remote relay for paired devices. Cloud routes requests; it does not override Local policy, approval, verification, or activity.
The safety loop stays the same.
Runtime-specific tools remain separate, while the protocol vocabulary and safety lifecycle stay compatible.
01
Inspect
Read the real state before proposing a mutation.
02
Approve
Bind human approval to the exact proposed operation where required.
03
Execute
Run only through the capability-owning runtime and its local policy.
04
Verify
Observe the result independently. Execution success is not verification success.
Remote MCP endpoint
Use this when you want ChatGPT or another compatible web client to reach a paired MCPDO Local device through MCPDO Cloud.
https://mcpdo.tophive.dev/mcp
WordPress sites expose their own site-hosted MCP endpoint. Installing the WordPress plugin does not require this Cloud endpoint or MCPDO Local.