I built an MCP server that lives inside WordPress - here's the safety model

Description and use

SiteHelm is a secure WordPress plugin that exposes 115 typed MCP operations with two‑phase writes, snapshots, and audit logs, enabling AI agents to manage sites without direct database access.

Problem

Clients need an AI agent to manage WordPress sites without exposing raw database or filesystem access.

Outcome

SiteHelm enables secure, auditable AI-driven WordPress management with two‑phase writes, snapshot verification, and rollback, preventing accidental or malicious changes.

Workflow

• Install SiteHelm plugin on WordPress
• Configure agent to use SiteHelm MCP operations
• When agent requests a write, SiteHelm performs a preview call returning before/after values and a single‑use plan token
• Agent submits apply call with exact arguments and token
• SiteHelm records snapshot before write
• Executes write operation
• Reads back site state and compares with preview promise
• If mismatch, reports failure; otherwise logs change in wp-admin
• Agent can pause writes via a single switch; plugins installed only from WordPress.org and deactivated by default

Evidence

Two-phase writes. Every write is two calls. The first is a preview: it writes nothing and returns each field's before and after value with a single-use plan token.

Source

Snapshot and verify. Before a write, the engine records everything a restore would need. After it, the site is read back and compared with the preview's promise.

Source

Audit and rollback. Every change lands in a log in wp-admin, in plain sentences, and applied changes roll back from there - with a preview first.

Source