WordPress 7.1 “Mary Lou” shipped on August 19. The headlines said core finally brought AI to WordPress. If you manage a site and expected to talk to it, you got a cropper, Notes with @mentions, and a Field Guide.
What actually landed is plumbing. The Abilities API grew up. The AI Client showed up. Developers got hooks. Site owners did not get an assistant.
That gap is the story. Not a complaint about 7.1. Core was never going to ship an opinionated admin agent. Matt already blocked a knowledge/guidelines primitive in core until some plugin shows week-to-week growth. WordPress will define the socket. Someone else has to plug a brain into it.
Read the Field Guide, not the blog post
The public 7.1 notes lead with user-facing stuff: Notes, media crop, responsive controls. The architecture is buried: validation hooks, execution filters, a flag for whether an ability is public to outside clients.
There is no AI writer in core. No admin chatbot. No “run my site from chat.” Waiting for that in a major release is how you wait years. If you want it this year, it is a plugin problem: tool choice, confirmations, and who pays for tokens.
Abilities are a registry, not an agent
An ability is a named action a model can call. Create a post. Update meta. 7.1 added three useful bits around that:
- Validation hooks, so you can refuse a call based on caps or post type before it runs.
- Public exposure flags, so a site can say which actions an external client is even allowed to see.
- Execution filters, so something can sit in front of the write: log it, ask first, or stop it.
That is how WordPress announces what a site can do. It is not how anything decides which tool to run, how to chain three of them, or what to do when the context window is full. The reasoning still lives outside core. That is the correct split.
MCP will choke on a fat catalog
Talking to WordPress from Claude or Cursor goes through MCP. PressBot’s MCP adapter turns site abilities into tool calls. The boring problem is size. Dump 105 tools into every prompt and you burn context and latency for no reason.
The 2026 MCP roadmap has progressive discovery: load tools when the conversation needs them. WordPress 7.1 does not have that. So an agent with a real catalog, like PressBot and its 105 tools, has to filter, budget, and rank on its own. Core gives you the endpoint. The plugin has to keep the conversation cheap.
What a write actually looks like
A create-post call in this world is not “the model publishes.” It looks more like this:
- The plugin registers
create_postwith a permission check. Authors only. - An external agent finds it over MCP because the ability is marked public.
- It sends a title, draft body, maybe tags.
- An execution filter fires. A human still has to say yes before the database moves.
- Then core runs it and hands back a draft ID.
7.1 is the fence: caps, flags, filters. Topic, draft, retries, “are you sure” in chat: that is the agent. The intelligence does not live in Mary Lou, and it should not.
BYOK is the part core will not do
This cautious core is why bring-your-own-key still wins on WordPress. You point the site at Claude, GPT, or Gemini. You pay that vendor. Nobody in the middle takes a per-message cut. You do not wait for 7.2 to get Telegram, images, or a tool that did not make the core debate.
That is the architecture PressBot Pro is on. Zip from pressbot.io (Freemius, not wordpress.org). 105 tools, site memory, multi-step runs, still your keys.
What to do with 7.1
Update. You want the security work and the stabilized Abilities hooks. Then do not sit around for an official admin agent.
The free plugin is the visitor chatbot on your own key. Pro is $29/year for one site when you want the admin side, bulk tools, and the other channels (14-day money-back; Business $59 for 5 sites, Agency $99 for 50). Same product. You are picking how many sites, not which features.
