Governance comes first
The interesting problem is not how many things an agent can do, it is which ones it should be allowed to. Off by default, least privilege, every call audited. That is the whole design.
Home / About
Why we built it
Bringing AI to WordPress, safely.
AI agents are getting good at real work. The open question is not whether to let them near WordPress, it is how to do it without handing over the keys. This plugin is our answer: give the agent real access, on a leash you hold.
What we are building.
One plugin that turns a WordPress site into a governed MCP server, so an agent can act on your site through a layer you set the rules for.
Turn WordPress into a governed MCP server for AI agents, off by default, least privilege, every call audited.
Most tools in this space race to expose the most endpoints. We think the harder and more useful problem is the governance around them: connecting as a scoped user, re-checking capability on every call, and logging what happened. The abilities matter, but the layer that decides whether a call is allowed to run is the reason to trust it.
- 153 governed abilities83 across WordPress core, 70 from optional integrations, and growing.
- 9 clients connect todayChatGPT through its Developer Mode custom connectors, Claude.ai, Claude Desktop and Manus each through a custom connector over OAuth, plus Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI, directly or through the open-source bridge.
- Runs on standardsBuilt on the WordPress 6.9 Abilities API and the official MCP Adapter (no custom transport). Requires WordPress 6.9+ and PHP 7.4+. See how the Abilities API works.
What we believe.
Four positions that shape every decision in the plugin. They are also the promises we hold ourselves to.
Free, and it stays that way
Free on WordPress.org, no paid tier, no API key to buy, no usage limits. There is no paywalled tier waiting behind the free one, and no plan to add one.
Built on open standards
It runs on the WordPress 6.9 Abilities API and the official MCP Adapter (no custom transport). No proprietary transport, no lock-in. If the standards move, we move with them.
Honest about limits
We say plainly what does not work yet. Some clients need a connector the adapter does not serve natively, so they are marked as not supported, not glossed over.
Who is behind it.
A small, independent project, built in the open. The best way to reach us is on GitHub, where the code and the issue tracker live.
Maintainer
Unaib Amir
Enterprise AI and software consultant. Builds and maintains Agent Abilities for MCP.
He has been building software for companies around the world for more than 14 years, mostly custom applications and enterprise platforms, WordPress among them. His work now is largely AI and automation: agents, MCP, RAG, and workflow automation. A lot of WordPress work is repetitive and takes longer than it should, and that is the work agents are good at. But letting an agent do it means giving it real access to a WordPress site, so he built a governance layer instead of a plain connector: the owner decides how far that access goes.
Open source on GitHub
The full source is public. Read it, open an issue, or send a pull request.
View the repositoryShipped on WordPress.org
Install it the usual way, from the WordPress.org plugin directory. Reviews and support requests there reach us too.
See it on WordPress.orgGive an AI agent WordPress access, on your terms.
Install it, keep everything off, and switch on one ability at a time as you build trust. Free, open source, and built to stay that way.
No paid tier behind the free one. No telemetry, nothing phoning home.