Let ChatGPT and Claude work in WordPress, on a leash you hold.

Yes, as long as the connection is scoped, and scoping is what Agent Abilities for MCP is built around. The agent connects as a real WordPress user and takes that account’s capabilities, so approve the connection while logged in as the account you want the agent to be. Point it at a least-privilege user and it can do no more than that user can do. Every ability stays off until you enable it. Every call to the tools this plugin serves is written to the audit log, denials included. Tools that another plugin publishes straight to the default server of the MCP Adapter are outside these controls, and a Settings switch controls that server.

The agent can only do what the WordPress user it connected as can do. Agent Abilities for MCP re-checks that capability before every call. Deletes go to Trash where WordPress supports it, so they can be restored. The last administrator can never be removed, no matter what the agent asks. Anything the agent is not allowed to do is refused. The refusal is written to the audit log too.

Yes. Turn on Force draft on create in Settings. Anything the agent creates, and any request to publish, is saved as a draft instead. Edits to a post that is already published still go live, so if you want every change reviewed, connect the agent as a Contributor, who cannot edit published posts at all. The Needs review card on the Dashboard lists those drafts so you can preview, publish or discard them.

Only if you connect it as an administrator. The agent takes the capabilities of the account it connects as. Over OAuth that is whichever account approves the connection in the browser, so log in as the dedicated low-privilege user the plugin creates before you approve, and the agent can only do what that user can do. An Application Password works the same way: generate it on that user rather than on your own admin account. Each ability re-checks the capability before it runs.

Only if you deliberately allow it twice. Nine WooCommerce abilities in Agent Abilities for MCP move money or grant authority. They cover refunds, order status, order updates, customer updates, payment gateway settings, coupon creation and updates, and tax rate creation and updates. Turning one of those on is not enough by itself. It stays locked until you also switch on a separate high-risk control in Settings. That switch is written to the audit log like any other change. Everything else in the catalog needs only its own toggle.

No. The plugin connects to no AI provider and sends no telemetry. Your own AI client connects in and calls the abilities you enabled. If you turn on alert emails, they go through WordPress’s own mail to the address you choose and never include call content, a user name or an IP address.

Yes. Agent Abilities for MCP works with ChatGPT through Developer Mode. Turn Developer Mode on in ChatGPT settings, then add your site as a custom connector. Approve it once over OAuth. ChatGPT then calls the abilities you enabled as the scoped user you pick. Custom connectors are a beta feature on ChatGPT’s paid plans. Claude.ai, Claude Desktop, and Manus connect the same way, through a custom connector, and Claude Desktop shares the one Claude.ai uses rather than running a bridge on your machine. Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI connect as well.

Install Agent Abilities for MCP, then open the first-run Quick Connect wizard on the plugin page. The wizard puts the whole first connection on one screen. For a hosted client like ChatGPT or Claude, turn on OAuth and copy the site endpoint. For a client that runs on your own machine, create a dedicated agent user and generate an application password. Either way, finish by switching on content reads. Nothing this plugin serves is exposed until you enable it. The wizard never turns on a delete.

Yes. Install the plugin on each site and add each site’s endpoint to your AI client as its own connector. The agent can then work across your sites from one place, and each site keeps its own user, its own allowed tools and its own audit log.

It is a WordPress site that speaks the Model Context Protocol, so an AI client can discover and call the site’s abilities as tools. Agent Abilities for MCP turns any WordPress site into one, built on the WordPress 6.9 Abilities API and the official MCP Adapter, and wraps every ability in a governance layer: off by default, capped at the capabilities of the WordPress account the agent connects as, and audited on every call.