From signal to a checkable result
Inspect the condition before choosing a database operation
A practical operator sequence is to establish the current signal, identify a narrow target, choose the operation, and read the result.
01
See current database health
Request a bounded current-site snapshot covering table engines, storage, index findings, options health, and observability coverage.
Use that result to identify what needs attention before maintenance.
02
Find the exact content or table target
List posts whose raw content contains a search string before changing them. For a known string, search and replace that exact string; when matches follow a pattern, use regex replacement.
For table work, select a logical WordPress table key. WordPress resolves the physical name, including custom prefixes and multisite base tables, without accepting an arbitrary table name or SQL.
03
Choose a controlled maintenance operation
Clean up expired transients or set an option’s autoload behavior when those tasks need attention. Core-table conversion to InnoDB is available for explicitly selected allowlisted core tables.
Exact and regex content replacements are dry-run by default, and live content writes require explicit confirmation. Table conversion is dry-run-first and also requires explicit confirmation.
04
Read the reported and verified outcome
For table-engine conversion, read the database statement outcome, the verified postcondition, and whether the mutation is known or unknown as separate results.
The statement alone is not proof that the resulting table state is verified.
Control boundaries
Keep every table operation inside WordPress-owned identity
The target, authority, and result remain independently checkable when table maintenance is needed.
AI assistant through MCP
MCP Abilities – Database exposes its registered WordPress abilities for an AI assistant to use through MCP.
Accepted table target
Use a logical WordPress table key. A physical table name or free-form SQL is not accepted.
Physical name resolution
WordPress resolves the physical table name so custom prefixes and multisite base tables stay within the same controlled boundary.
Network-global authority
On multisite, a network-global table key requires both super-admin and network-options authority, including for audit and dry-run requests.
Mutation reporting
A conversion response reports the database statement outcome, checks the resulting postcondition, and states whether the mutation is known or unknown. Read all three separately.
Dependencies
Dependencies for MCP database abilities
These named components provide ability registration, plugin execution, and MCP client access.
WordPress 6.9 or later
WordPress Abilities API in WordPress 6.9 or laterProvides the native ability registration and execution interfaces.
PHP 8.0 or later
PHP 8.0 or laterRuns the plugin code.
MCP client access
WordPress MCP AdapterExposes registered WordPress abilities to MCP clients.
Stable package
Download the WordPress database abilities
Download the stable self-hosted ZIP when you want an AI assistant to inspect WordPress database health and use controlled maintenance abilities through MCP.