A WordPress AI Agent for Agency Sites

What agencies want from an AI agent

If you run an agency, you ask the same questions again and again. Which plugins are installed on this site? What pages exist? Can someone make a backup before the change? Can someone clear the cache before the call starts? None of these questions is hard. They are repetitive, and they multiply with every site you add.

That is the appeal of a WordPress AI agent. You type a question in plain words in an app you already use, such as ChatGPT or Claude, and the answer comes from the site itself. You stop opening one dashboard after another just to look something up.

It helps to be honest about the limits from the start. An AI agent sitting on top of a website is only as safe as the actions it is allowed to take. A tool that can only read a plugin list is a small risk. A tool that can change anything is a large one. When you judge any agentic setup for WordPress, start with the list of actions, not the demo.

This post covers what the SimpleWP connector allows today, how to connect it, and where it stops for agencies. It stops short of client work, and that matters if your business is built around client sites.

What the connector can do today

SimpleWP offers a connector that links ChatGPT or Claude to your account. Once connected, you can do the following from the AI app:

  • List your sites and see a site's details.
  • List a site's plugins and pages.
  • Ask the site assistant a question.
  • Create a backup.
  • Clear the cache.

That is a deliberately practical set. It covers the lookups and small maintenance jobs that eat time. Checking the plugins on a site becomes a short conversation instead of another login.

Two boundaries are worth knowing before you plan around it.

First, changes the assistant proposes need your approval in the AI app. The agent does not quietly push things through. You see the proposal and decide.

Second, the connector works on your own sites only. It does not write content for you either. If you want an AI app to draft pages through the connector, that is not what this does. It is a way to look, ask, back up and clear the cache.

If you want the single-site version of this story, we wrote it up in connecting ChatGPT or Claude to your own site.

Connect ChatGPT or Claude in a few steps

The setup is short. You add the SimpleWP server address in the AI app, sign in to SimpleWP, and click Allow. The server address is https://mcp.simplewp.com/mcp.

You do not paste a password into the AI app. You sign in to SimpleWP as usual, and the Allow screen is where you grant access. That is the same pattern you already know from "sign in with" buttons elsewhere.

The exact screens differ between ChatGPT and Claude, and they change as those apps change. Rather than describe every click here and risk getting it out of date, follow the step-by-step setup guide.

One caveat sits on the AI app's side, not ours. Adding your own connector may not be available on every plan of the AI app. If you cannot find the option, check your plan in ChatGPT or Claude first.

Claude Code, Cursor and VS Code for developers

If you or your developers work in Claude Code, Cursor or VS Code, the same server address applies. This is the route for anyone searching for how to set up WordPress MCP with Claude Code: point the tool at the address above and connect.

Some developer tools cannot complete the sign-in and Allow flow. For those, you can connect with a personal key instead, sent as a header. The key stands in for the sign-in step.

Treat that key with care. A personal key opens the whole account, not a single site. That makes it more sensitive than it looks, so a few habits are worth building:

  • Keep it out of files that are shared or committed to a repository.
  • Do not paste it into chats, tickets or team channels.
  • Prefer the sign-in and Allow flow whenever the tool supports it.

On a team, this deserves a clear rule. One person pasting a key into a shared notes file is enough to expose every site on that account. Decide where keys may live before the first developer connects.

The same limits apply here as with ChatGPT and Claude. The tools act on your own sites, and the actions are the ones listed above. A developer connection does not unlock anything extra.

Client sites: where this stops today

This is the part agency owners need to read twice. Sites you manage for clients are not available through the connector today. The connector sees the sites you own, and that is where it ends.

If your portfolio is mostly client work, that limits how much of it the connector can cover for now. We would rather say that plainly than let you find out after a pitch to a client.

For client work, the tools that exist today are these:

  • The client dashboard. You invite clients, create WordPress sites on their behalf, open their WP admin and manage subscriptions. It is live now, and the guide to manage clients as a partner walks through it.
  • The Partner API. Org-scoped API keys with rate limits work against the public Partner API. If you want to script parts of your agency's workflow, this is the route. If you are new to this kind of interface, the WordPress REST API is a good primer on what APIs are and are not good for.

In practice, many agencies will end up using both sides. The connector helps with the sites you own, such as your agency's own site, internal tools or demo builds. The dashboard and the Partner API handle the sites you manage for others.

Keeping an agency account safe

An agency account holds more than a personal one, so the safety habits matter more.

Read the consent screen every time. It names the app asking for access. If you are connecting ChatGPT, it should say so. If you see an app name you do not recognize, click away and do not allow it.

Then review what is connected from time to time. In SimpleWP, go to Settings, AI assistants, Connected apps. You will see the apps you have allowed. Disconnect anything you no longer use. A tool someone tried during a trial and forgot about is still a door into the account.

A few habits are worth building around that review:

  • Make a short list of who on the team has connected which app.
  • When someone leaves the agency, check for apps they connected and any personal keys they created.
  • Approve proposed changes by reading them, not by clicking through.

None of this is complicated. It is the same care you would give to any account that can touch several websites.

Start with the partner program

If you build and manage sites for clients, the partner program is the place to start. It is where the client dashboard and the Partner API fit into how your agency works. Connect your own sites to ChatGPT or Claude, try the plain-language lookups, and keep client work on the tools built for it while the connector stays limited to sites you own.

Photo: olia danilevich on Pexels