
From API to Agent: How WordPress 7.0 and Claude Code Are Rewriting Website Management
Think about the last time you logged into WordPress. You tweaked a meta description, resized a featured image, or fixed a broken internal link. Now imagine telling an AI to handle all of that while you stay in your terminal. That shift — from manual clicking to conversational command — is exactly what WordPress 7.0 and tools like Claude Code are bringing to the table.
This isn’t about “AI as a writing assistant” anymore. It’s about AI as an operator. WordPress 7.0 (codenamed “Armstrong”) built the plumbing. The ecosystem is now filling in the rest.
Here’s what changed, why it matters, and where to go if you want to start building your own AI‑driven WordPress workflow.
1. The New Foundation: WordPress 7.0’s AI Infrastructure
The Connectors API: One Key to Rule Them All
Before WordPress 7.0, adding AI capabilities meant juggling API keys across a dozen plugins. Each had its own settings page, each stored credentials differently. WordPress 7.0 introduced the Connectors API, a centralized credential management system for AI services. You can find it at Settings → Connectors in your wp‑admin.
The core change is simple: enter your OpenAI, Anthropic, or Google Gemini API key once. Every plugin that supports the new WP AI Client can use it — no reconfiguration needed. It’s standardized across the ecosystem.
📖 Official Field Guide
WordPress 7.0 Field Guide — the complete developer reference for what’s changed.
🔌 Connectors API Deep Dive
Introducing the Connectors API — auto‑discovery, authentication flows, and plugin developer notes.
🛠️ Hands‑On Guide
What the AI Connectors Actually Do — a practical walkthrough of the new settings page.
The Abilities API: When AI Can Actually “Do” Things
Plugging in API keys is one thing. Letting AI operate your website is another. WordPress 7.0’s Abilities API gives AI agents structured access to core functionality: publishing posts, adjusting settings, navigating admin screens. The shift is subtle but profound — AI moves from “suggest” to “execute.”
2. The Bridge: Connecting Claude Code to WordPress
The most practical way to start using AI agents with WordPress right now is through Application Passwords — WordPress’s native API authentication system. Generate one at Users → Profile → Application Passwords. Copy the token, and any AI agent (Claude Code, Cursor, custom scripts) can securely interact with your site via the REST API.
🔐 Step‑by‑Step Setup
Publishing Content to WordPress with Claude Code Skills & the REST API — a 15‑minute guide: generating Application Passwords, creating a .env file, and building reusable Claude Code Skills.
🛡️ Security Best Practices
Give Claude access to your WP website – but keep track of what they do — why Application Passwords are safer than sharing your main credentials, plus logging and auditing strategies.
3. The Advanced Frontier: Agent Skills and Custom Workflows
This is where things get genuinely interesting. WordPress officially released agent‑skills — portable bundles of instructions, checklists, and scripts that help AI assistants understand WordPress development best practices. The repository currently includes 13 core skills covering block development, theme.json, REST API usage, security patterns, and more.
If you work in VS Code with Claude Code, you’re in the most powerful configuration. You can define custom Skills in your project’s .claude/ directory, execute WP‑CLI commands directly, and build specialized agents for SEO auditing, image generation, internal linking, or content governance — all without leaving your terminal.
📦 Official GitHub Repository
WordPress agent‑skills on GitHub — the definitive source, updated with 1,200+ stars and active community contributions.
🧠 Case Study — 6 Agents, 16,000 Posts
I Built a WordPress Plugin with a Team of 6 AI Agents — processing 16,000 posts in 90 seconds using Claude Code’s Agent Teams.
📈 SEO Automation Case Study
Automating WordPress SEO Optimisation with MCP and Claude Code — fixing 11 broken URLs, adding meta descriptions to 52 pages, and implementing strategic internal linking across 40 posts, all without opening the WordPress admin interface.
What This Means for You
This shift — from “AI suggests, you click” to “you command, AI executes” — represents a fundamentally different way of managing websites. The plugins you rely on will increasingly need to support the new WP AI Client and Connectors API to remain competitive. But more importantly, you now have the tools to build your own agents: custom workflows that scan, optimize, link, and publish without manual intervention.
Whether you start with Application Passwords and a simple Claude Code Skill, or dive into the full agent‑skills repository, the path is open. The question is no longer if AI can run parts of your site — it’s what parts you’re ready to hand over.
1. Start small — Set up an Application Password and try the REST API publishing workflow from the Anicca guide.
2. Explore the official resources — Read the Connectors API documentation and watch the WordPress.tv Claude Code talk.
3. Go deep — Clone the agent‑skills repository, study the case studies, and build your first custom SEO audit Skill.
flowchart LR
subgraph User["👤 User"]
CLI["Terminal / Claude Code"]
Skills["Custom Skills"]
end
subgraph WP["🏠 WordPress 7.0"]
REST["REST API"]
Auth["App Passwords"]
Connectors["Connectors API\n(AI keys)"]
Abilities["Abilities API\n(Execute)"]
end
subgraph AI["🤖 AI Agents & Services"]
Claude["Claude Code"]
OpenAI["OpenAI"]
Anthropic["Anthropic"]
Gemini["Google Gemini"]
end
subgraph Tasks["📋 Workflows"]
SEO["SEO Fixes"]
Content["Publish/Edit"]
Linking["Linking"]
Meta["Meta Desc"]
end
CLI -->|App Password| Auth
Auth --> REST
REST --> Connectors & Abilities
Connectors --> OpenAI & Anthropic & Gemini
Abilities --> Tasks
CLI --> Skills --> Claude
Claude -->|agent-skills & REST| Tasks
style WP fill:#5b21b6,color:#fff
style User fill:#f97316,color:#000
style AI fill:#c084fc,color:#000
style Tasks fill:#10b981,color:#000