MCP Abilities - Database gives AI a clear basis for deciding what to change

An AI assistant can start from the current WordPress database state that matters to the question, so a proposed maintenance change has a concrete site fact behind it.

Art Deco industrial MCP Abilities - Database machine with protected database cylinders, five health gauges, a logical table route, a network lock, and a three-state verification chamber.

From question to evidence

Turn a database question into a decision you can check

Keep the current condition, intended target, proposed operation, and returned result distinct.

01

Read the current database condition

Use the overall health snapshot for table engines, storage, index findings, option health, and observability coverage. Use narrower checks for engines, indexes, or options when the question is specific.

02

Inspect post content before editing

First list posts whose raw content contains a search string. For a known phrase, use exact search and replace; for a pattern, use regex replacement. Treat both as dry runs until you explicitly confirm a live write.

03

Choose a narrow maintenance operation

Expired-transient cleanup can plan or delete at most 500 expired transient pairs per call and returns no names or values. Option-autoload maintenance can plan or change at most 25 explicit non-transient option names without reading or changing their values.

Core-table conversion is restricted to explicitly selected allowlisted core tables. These operations begin as dry runs, and live deletion, option changes, conversion, or content writes require explicit confirmation.

04

Verify the resulting state

After a conversion, inspect the resulting state before relying on it. Use the response to distinguish the database statement outcome, the verified postcondition, and whether the mutation is known or unknown.

Control boundaries

Let WordPress keep identity and authority in view

An AI assistant can request a result through MCP, while WordPress applies its own table identity, permissions, and mutation reporting.

AI assistant through MCP

An AI assistant sends a request through MCP, and WordPress evaluates it within the site’s own identity and permissions.

Accepted table target

Table operations accept a logical WordPress table key. Arbitrary table names and free-form SQL are not accepted.

Physical name resolution

WordPress resolves the physical table name after selection, so custom prefixes and multisite base tables remain supported.

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 separates the database statement outcome, the verified postcondition, and whether the mutation is known or unknown.

Dependencies

What MCP database abilities require

Keep the WordPress runtime, PHP runtime, and MCP connection available as separate requirements.

Stable package

Evaluate the database evidence in your own environment

Download the stable self-hosted ZIP to test whether its WordPress database evidence answers the maintenance question in front of you.