AI for WordPress can mean a writing button, a dashboard agent, an MCP server, a reusable skill, or a coding agent working in a repository. This guide separates those categories so you can choose the smallest tool that safely solves the job.
11 profiles
Plugins & builders
Compare dashboard agents, SEO copilots, page builders, chatbots, automation plugins, and hosted WordPress builders by what they can actually do.
8 profiles
MCP connectors
Understand the official WordPress MCP stack and compare remote bridges, ability catalogs, WooCommerce support, authentication, and production safeguards.
5 profiles
Agent skills
Compare WordPress Agent Skills, Studio, Playground, Blueprints, and WP-CLI without confusing instructions with executable tools.
8 profiles
Coding agents
Compare general and WordPress-specific coding agents for plugin, theme, block, WP-CLI, test, Git, and deployment work.
Choose by the work, not the AI label
| Need | Start with |
|---|---|
| Write or optimize one page | An editor or SEO copilot |
| Manage content, media, products, and routine admin | An in-dashboard WordPress agent |
| Connect Claude, Codex, Cursor, or another external client | An MCP adapter or server |
| Build or refactor a plugin or theme | A coding agent with WordPress Agent Skills and Playground |
| Repeat a defined procedure | An Agent Skill or deterministic automation |
Safety baseline
- Start on a disposable or staging site for code, files, users, orders, settings, or database writes.
- Give outside agents a dedicated, least-privilege WordPress user.
- Begin read-only and enable publishing, deletion, plugins, users, billing, and customer data separately.
- Review the actual authenticated tool list, not only a marketing feature count.
- Keep backups, revisions, logs, and a tested rollback path.