# A WordPress AI agent for the admin work nobody wants to do Most WordPress AI plugins will write you a lovely paragraph and then leave you to paste it in, fix the formatting, and still go find the 14 images with no alt text yourself. A WordPress AI agent takes the other half. You describe the job ("raise every price on the services page by 10%"), and it works out the steps and does them on your site while you watch. You decide what it's allowed to touch, and which changes wait for you. There are two kinds of WordPress AI tool, and they're good at different things. ## Writing tools vs agents AI writing plugins live inside wp-admin and help you write. AI Engine has 90,000+ active installs on WordPress.org as of October 2026. It gives you chatbots for visitors, a Content Studio for drafting posts, and a Copilot in the editor that corrects, rewrites and translates. You bring your own API key from whichever AI provider you choose. And it's moved toward agents too. AI Engine now ships a free MCP server that its plugin page says Claude and ChatGPT can use with no account, no cap and no API key. Its Pro version adds MCP tools for plugins, themes, the database and WooCommerce. **If you want a visitor chatbot and in-editor writing help in one plugin, AI Engine is the one to pick.** Agents work the other way round. You talk to Claude or ChatGPT, and it calls tools on your site: edit this page, update that plugin, change this setting, check the result. The model doesn't run on your server at all. WordPress.com built both kinds for its own customers. Its built-in AI assistant (February 2026) edits layout, styles and text inside the editor, with layout changes on block themes only, per TechCrunch. In March 2026 it opened MCP write tools on paid WordPress.com plans, with every change needing approval. If your site is hosted on WordPress.com, start there. But most freelancer and agency sites are self-hosted, on whatever host the client picked in 2019. ## Three jobs an agent does well A dog-grooming salon's site makes a good example: a services page with prices, a booking page, and a blog nobody has touched since spring. ```prompt Our prices go up 10% on November 1. Update every price on the Services page, rounded to the nearest dollar, and show me the before and after. ``` The agent reads the page, rewrites the prices and lists them for you. Content edits like this run directly, and Kitepod snapshots the page first, so going back is one request. ```prompt The booking page has been throwing errors since last night. Find out why and tell me before you change anything. ``` Kitepod reads Site Health, the last fatal error, paused plugins and the tail of the debug log, secrets hidden. The agent tells you what it found. If the fix means touching code or the database, that part waits for a person. ```prompt Find the blog posts with no featured image and suggest a free stock photo for each, with its license. ``` Kitepod searches free stock photos (Openverse, plus Unsplash and Pexels when they're configured) and returns each with its license and attribution. You pick; it uploads and sets them. That middle one is what agents are for. It's diagnosis and action in one place, on a problem you'd otherwise spend your lunch break googling. ## Running one on your own site Kitepod is a free MCP server plus a WordPress plugin. It turns Claude, ChatGPT, Cursor or any MCP client into an agent for your site, with 51 tools, unlimited sites and no call meter. It's free because Kitepod doesn't run a model; your own AI plan does. - Upload the plugin (it needs WordPress 6.4+ and PHP 7.4+), then press Connect in wp-admin. - Choose the WordPress account the agent works as. It can never do more than that account. - Point your assistant at `https://kitepod.com/mcp` and sign in. There are short guides for [Claude](/claude-wordpress) and [ChatGPT](/chatgpt-wordpress). Allow about two minutes, start to finish. ## Why the agent can't approve itself An agent with access to everything is only useful if it can't sign off its own risky work. So in Kitepod **the AI can't approve its own changes.** Each site has an approval policy: auto, balanced (the default) or strict. Under balanced, the agent edits content, menus, SEO fields and media on its own, with a snapshot behind every write. Plugin installs and updates, theme switches, users and roles, database writes and code wait for a person. Strict holds more back. ## Who should use an agent People whose WordPress time goes on admin rather than writing: freelancers with a few client sites, agencies running [care plans](/wordpress-care-plan), owners with a list of small fixes that never gets shorter. But if your real need is a chatbot for visitors or drafting help inside the editor, a writing plugin will serve you better. And if you're weighing agent setups against each other, the [WordPress MCP](/wordpress-mcp) overview lines the setups up side by side. ## Finer points ### What's the difference between a WordPress AI assistant and an AI agent? An assistant usually helps you write or answers questions inside the editor. An agent takes actions across the site: it edits pages, changes settings, updates plugins and checks the result. Kitepod turns the assistant you already use into an agent for your site. ### Does the agent get my admin password? It doesn't. Your assistant signs in to Kitepod with OAuth, and you choose which WordPress account it works as. Connect it as an Editor and it can't touch plugins or theme code; connect it as an Administrator and it can, with approvals on the risky parts. ### Will an AI agent slow my site down? The agent only works when you ask it to. The model runs on Claude or ChatGPT, not your server, and a short per-site rate limit stops a runaway agent from hammering it. ### Can one agent handle all my client sites? Yes. All your connected sites share one conversation, so a single request can cover every one. You can invite each client as an approver on just their own site. ### Do I need to pay for an AI model? You use the Claude or ChatGPT plan you already have. Kitepod itself is free. The writing was never the slow part of running a WordPress site. The clicking was.