What this does
Since WordPress 6.9, a site can describe what it's able to do in a form AI assistants understand, and a connector can hand those abilities to Claude. The usual advice online is "install the connector". This skill does the careful version instead.
When it's finished you'll have:
- A separate WordPress user for the assistant, with the lowest role that does the job. It never gets an administrator account.
- Reading only, to begin with. Nothing can be changed until you decide it can, one ability at a time.
- One test read that proves it works. For example, the titles of your five latest posts, checked against what you see in your dashboard.
- A record of every call, if the connector you choose keeps one.
- A one-click off switch, and you'll know where it is.
Last tested on 23 September 2026, with WordPress 7.1.2 and Agent Abilities for MCP 1.7.5. The assistant read the published posts, was refused the drafts, couldn't write, and every call appeared in the log.
How to undo it
Revoke the assistant's access, which is one click: disconnect it, or delete its application password. Then deactivate the connector plugin and delete the assistant's user. Your content isn't touched at any point unless you've switched on writing.
When this stops being a small job
Stop and get help if any of these are true:
- Your site takes orders or payments. WooCommerce has its own abilities for orders and products, and the risk is real money.
- It's a multisite network.
- The assistant would see personal data: customer records, member details, form submissions.
- Your host or a security plugin blocks application passwords, and the connector has no other way to sign in.
- The site hasn't been updated in a long time, so getting to 6.9 is a job in itself.
Instructions for the assistant
You're helping someone connect you to their own WordPress site. They may be new to this. Be plain and brief, go one step at a time, and change nothing without a yes. Never ask for a password, application password or key to be pasted into the chat. Tell them where it goes instead.
1. Look first
Ask for the site's address. Check that https://<site>/wp-json/ responds. Ask them to confirm their WordPress version, which they'll find on the dashboard's Updates screen. It must be 6.9 or later. Ask whether the site is hosted on WordPress.com or somewhere else.
If anything in "When this stops being a small job" applies, say so plainly and stop there.
2. Ask what it's for
Ask these, as one numbered list, and wait for the answers:
- What do you want me to be able to do on the site? For example, read posts, draft new ones, or tidy categories.
- Who else edits the site?
- Which Claude are you using: the Claude app, Claude Desktop, or Claude Code?
3. Make sure there's a way back
Ask them to take a backup today, through their host or a backup plugin, and to tell you when it's done. Wait for that.
4. Choose the route
First, ask what's already on the Plugins screen. If anything mentions MCP or abilities, assess that before adding anything: two MCP servers on one site will confuse both of you.
-
Hosted on WordPress.com: it has its own connector for AI agents, which you approve in the browser. Follow its current guide at developer.wordpress.com/docs/mcp.
-
Hosted anywhere else: WordPress's official MCP Adapter on its own exposes three read-only abilities: site information, user information and environment information. That's useful for a first test, but not for real work. For reading and drafting posts, the site needs a plugin that registers those abilities.
Look for one that meets all of these criteria:
- everything is off by default, with a switch per ability
- the assistant acts as a real WordPress user, never as an admin-equivalent key
- there's a read-only mode
- it keeps an audit log of every call
- it has been updated in the last three months and is tested with the current WordPress
- it has been around long enough, and on enough sites, to have a track record. A young plugin with a single maintainer isn't ruled out, but tell the person plainly
At the time of writing (September 2026), Agent Abilities for MCP on wordpress.org meets the design criteria. It's young, though: first published in July 2026, with one maintainer. So tell the person that, and let them decide.
Before recommending any plugin, check its page for the maintainer, when it was last updated, how many sites use it, and what it's tested with. Tell the person what you found. If anything worries you, say so and don't recommend it.
Some of these plugins include the MCP Adapter inside themselves (Agent Abilities for MCP does). If the one you choose does, don't install the adapter separately.
Follow the chosen connector's own current setup guide for the exact steps. The steps below are the safety layer around that guide.
5. Give the assistant its own user
Walk them through creating a new user in the dashboard, named something like claude-assistant. Use the lowest role that does the job:
- Contributor if the assistant should only draft. Contributors can write and edit their own drafts but can't publish, so a person always presses Publish.
- Author only if it genuinely needs to publish.
- Never Administrator.
They create the user themselves. You explain the steps.
6. Connect it
Prefer a connection they approve in the browser (OAuth) if the connector offers one, because no secret is stored anywhere.
Otherwise, they sign in as the new user, go to Users, then Profile, then Application Passwords, and create one named after the assistant. They put it into Claude's connector settings or config file themselves. It never goes into the chat.
7. Reading only
In the connector's settings, switch on only the abilities that list and read posts. Leave everything else off. If there's a read-only mode, turn it on.
8. Prove it works
Make one harmless read: list the titles of the five most recent posts. Ask them to compare the list with their dashboard. With a Contributor account you'll only see published posts. If a request for drafts is refused, that's the account working as it should, so say so. If the connector keeps an audit log, ask them to find that call in it.
9. Show the off switch
Tell them exactly how to cut you off: disconnect the connection, or delete the application password. Point to where that button is. Make sure they can find it before you move on.
10. Writing, only if they want it
If they want you to do more than read, switch on one ability at a time. For each one, say what it lets you do, and what the worst mistake with it would be. Prefer drafts: with the Contributor role, a person publishes. Turn on any force-to-draft or rate-limit setting the connector offers. Leave anything that deletes switched off.
11. Summarise
Finish with a short summary:
- what's connected, and as which user
- which abilities are on
- where the log is
- how to switch it all off
Add one line of advice: look at the log once a week for the first month.