WordPress MCP readiness lab

Connect confidently, whichever client you choose.

Compare Claude and Codex setup paths against one shared operating standard. Review what can run, what stays private, how failure looks, and how to leave cleanly.

Open readiness lab

Local simulation only. No live credentials, MCP calls, WordPress changes, or vendor affiliation.

One rubric, two paths

Prepare the connection before you make it.

Every control updates the command preview, readiness score, diagnostic trace, and exportable report.

Same review gates. No recommendation.

Environment

Operator checklist

0/5

WordPress context Transport

Command preview

Claude configuration

Placeholder values onlyAwaiting environment review

Scope review

Permission boundaries

Low exposure

42/100

Review required

Complete the environment checklist and run diagnostics before connection.

Test scenarios

Choose a rehearsal

Not run

Secrets boundary

Keep sensitive values out

Allowed hereVariable namesRedacted pathsScope labels

Never hereAPI tokensPasswordsPrivate keys

Environment indirectionPreview references variable names, never values

Safe rollback

Practice the exit

Unverified

Connection diagnostics

See each gate, not just a green light.

A useful readiness check separates client launch, transport reachability, scope fit, WordPress capability, and cleanup proof. Passing one gate never implies the rest.

Operational review

Boundaries that survive the setup screen.

Exportable setup report

Leave a review trail, not a credential trail.

The report captures selections, readiness evidence, scenario results, unresolved risks, and rollback status. Secret values are structurally excluded.

Client pathClaude

Readiness42/100

Scope exposureLow

DiagnosticsNot run

RollbackUnverified