Agent Abilities for MCP – Connect Claude and ChatGPT with Permission Controls and Audit Log
WordPress MCP server for Claude and ChatGPT with limited access, a pause switch, read-only mode, drafts you approve, playbooks and an audit log.
Safe pick
Yes — Agent Abilities for MCP is a safe, well-maintained plugin to use in 2026. It runs on 1K+ sites, is rated 4.8/5 and was last updated 4 days ago, and scores 85/100 on our health check.
- Actively developed — last update 4 days ago
- Tested with the latest WordPress (7.1)
- Momentum — downloads up 26.6% vs the previous 30 days
How does it stack up?
Side-by-side on installs, updates, ratings & supportDaily downloads
Download spikes usually follow a new release — each site that auto-updates counts as a download.
Rankings
Where Agent Abilities for MCP stands todayWordPress.org search rankings
Live position in the plugin search, top 100| Keyword | Position |
|---|---|
| abilities-api | #3 |
| AI agent | #16 |
| Claude | #17 |
| mcp | #15 |
| mcp-server | #17 |
Version adoption
Share of active sites per release.
Rating breakdown
★★★★★★★★★★ 4.8 from 5 reviews
About Agent Abilities for MCP
From the official readme · v1.12.0Description
WordPress MCP server for Claude and ChatGPT, with limited access and an audit log
Agent Abilities for MCP is a free WordPress MCP server plugin that exposes WordPress abilities to AI agents. You connect Claude, ChatGPT, Cursor or another MCP client to your site, and the AI works as a WordPress user you pick and gets exactly that user’s role. An Editor connection means limited access, not admin: it can write and edit posts, and it can’t install a plugin or change a setting.
It suits site owners, agencies and developers who want an AI agent working on the site without an admin login. Let Claude or ChatGPT draft posts without publishing them, or give either read-only access so it can look around.
Once connected, you can ask things like:
- “List my five newest drafts and tell me which ones have no featured image.”
- “Fix the typo in the second paragraph of the About page.”
- “Which WooCommerce orders are still on hold?”
- “Write a post about the spring sale and save it as a draft.”
There are 216 abilities (the tools an AI client can call), 94 for WordPress itself and 122 for plugins such as WooCommerce, ACF and Yoast SEO. Every one starts switched off.
What is a WordPress MCP server?
MCP, the Model Context Protocol, is an open standard that lets an AI app ask a service what it can do and then call it, and a WordPress MCP server is a site that answers. Give Claude or ChatGPT your site’s MCP endpoint, the URL on the plugin’s Connection tab, and it can look up an order or draft a post directly instead of you copying text between a chat window and wp-admin.
Connect Claude to WordPress
Switch on the abilities you want and copy your endpoint from the Connection tab. In Claude, open Customize, then Connectors, choose + Add, then Add custom connector, and paste the endpoint. Approve the sign-in once in your browser. On Team and Enterprise plans an Owner (or, on Enterprise, a role with the right permission) has to add the connector first, under Organization settings, then Connectors.
Anthropic’s help article lists custom connectors on Free (one custom connector), Pro, Max, Ultra, Team and Enterprise. Claude connects from Anthropic’s cloud, so your site has to be reachable from the public internet.
Connect ChatGPT to WordPress
On ChatGPT web, open Plugins, select the plus button, then Add custom MCP server, name it, paste your endpoint under Connection, choose OAuth for authentication, tick the risk acknowledgment and select Create as a plugin. You don’t need to turn on Developer Mode first.
OpenAI’s help article says custom MCP servers and full MCP, writes included, are available on Business and Enterprise/Edu, and that Pro can connect with read and fetch permissions, but it doesn’t mention Free or Plus. On Business, admins and owners add the server, while on Enterprise/Edu admins can, and so can members they grant access to. It’s a web feature only.
Manage multiple WordPress sites from Claude or ChatGPT
Install the plugin on each site and add each endpoint as its own connector. Every site keeps its own user, switches and audit log, so an agency can open one client’s site to the AI without touching the others.
Let Claude or ChatGPT edit WordPress posts without admin access
The role you connect as sets the limit: an Editor can write and edit any post, an Author only its own, and a Contributor can write without publishing. The catch is that on a new install only Administrators can approve a connection. Tick Editor under Roles that can connect on the Settings tab, approve as an administrator and pick the Content editor preset, or use the Application Password route with an agent user you’ve given the Editor role.
Let Claude or ChatGPT draft posts without publishing
Start with Force draft on create in Settings. What the AI creates or tries to publish as a post, page, custom content item, reusable block or WooCommerce product is saved as a draft instead, and a product variation is saved as disabled (private).
The Needs review card on the Dashboard lists those drafts with Preview, Open in editor, Publish and Discard buttons, and Discard moves the post to the Trash. Edits to a post that is already live still go live, so connect the AI as a Contributor, who can’t edit published posts, if every change needs your approval.
Give an AI agent read-only access to WordPress
Turn on read-only mode in Settings and this plugin unloads every write tool, including write tools bridged from other plugins, so the AI can search and read but can’t change anything through it. Your selections come back when you switch it off. To limit a single connection instead, pick the Read only preset when you approve it.
Update ACF fields and edit one block
With ACF active, the AI can read a post’s fields and write new values, each sanitized for the field’s type. It can also edit a single block: it lists your block types, reads a block’s settings (an ACF block adds its field names) and swaps one block with Replace block, without resending the page.
Limit what an AI agent can do on your site
These controls cover this plugin’s own tools, plus any other plugin’s tool you switch on from the Plugins’ own tools tab. Each call is checked against the capabilities of the WordPress user the AI connects as, over OAuth or an Application Password.
Pause all access on the Connection tab is the emergency stop, the one switch that pauses all agents at once. It refuses every MCP request through your site, OAuth apps and Application Passwords alike. An Application Password can still use the rest of the REST API, so revoke it too for a full cut-off. To pause an AI agent without disconnecting it, use Pause and Resume next to Revoke on an OAuth connection. An OAuth connection can also get an end date, for access that expires, and a lower rate limit of its own; an Application Password has neither.
When you approve an app, or run Quick Connect, you pick an access preset (Read only, Content editor, Shop manager or Custom) that only ever narrows what is already switched on. Per-role and per-connection allowlists narrow it further, since a tool has to be in the global list, the role’s list and the connection’s list before the AI can call it. The rate limit, the IP allowlist, Force draft on create and a maximum title length sit on the Settings tab and do nothing until you set them.
Ten WooCommerce tools that move money or grant authority (refunds, creating and changing orders, customer updates, payment gateways, coupons and tax rates) stay locked until you unlock them in Settings, even if you’ve ticked them. Deletes work differently: the tools named Trash post and Trash page move content to the Trash, but most Delete tools, such as Delete post, Delete page and Delete media, remove it permanently.
What these controls do not cover
The MCP Adapter has a built-in default server that other plugins can publish their own tools to. Tools on that server sit outside this plugin’s controls, so its read-only mode, allowlists, IP allowlist, rate limit and audit log do not apply to them. Pause all access is the exception, since it refuses requests to that server too. A Settings choice, Allow the MCP Adapter’s default server, takes Automatic (the default, which runs it only when another plugin publishes tools there), Always on or Always off. This plugin’s own tools are never on that server.
Audit log: see what the AI did on your site
The audit log is the Activity Log tab. Every call to one of this plugin’s tools lands there, denied calls included, with the reason for a denial. A row shows who made the call, the connection and source IP, the tool, the argument names, how long it ran and a short note on what it touched (ids, slugs and meta key names, never post text or email addresses).
You can filter by user, connection, tool, plugin, date or text, watch the Live view and export what the filters show as CSV. The log is a table in your own database.
Playbooks and Site Brief: standing instructions for AI agents
Write a checklist once on the Playbooks tab, such as how to check a draft before it goes out, and the AI loads it when a task matches. Five starters come built in and arrive switched off. Site Brief on the Settings tab holds a few standing rules, such as your spelling or pages to leave alone, that every agent gets when its session starts.
Two read tools, List playbooks and Get playbook, stay off until you enable them on the Abilities tab. With both on, the AI sees your Active playbooks when a session starts and loads one with Get playbook. It reads the text word for word, so keep passwords and private details out, and agents can’t edit playbooks. A playbook or the Site Brief is guidance the AI may follow, so the controls above still decide what it can do.
AI for WooCommerce, ACF, Yoast SEO and other plugins
When one of these plugins is active, its abilities appear on the Integrations tab. WooCommerce has the most, 52, covering products, variations, orders, customers, coupons, shipping, tax, payment gateways and reports, and because they reach names, emails and addresses an admin notice flags them. ACF adds 7 for field groups and the field values on posts, terms and users, and Rank Math (5), Yoast SEO (3), All in One SEO (3) and Slim SEO (2) let the AI read and edit a post’s SEO data.
The Events Calendar has 13 abilities, Event Tickets 3, Avada 18 and WPBakery Page Builder 12, both for editing pages and builder settings. GeoDirectory’s 4 business listing tools stay off until you enable that integration, even with GeoDirectory active.
Minimum versions: WooCommerce 9.1, All in One SEO 4.9.8, The Events Calendar 6.17.3.1 and Event Tickets 5.29.3.1. Below these, their tools stay hidden and the Integrations tab says why.
Plugins that register their own abilities with the WordPress Abilities API appear on the Plugins’ own tools tab, and this plugin does not filter what another plugin’s ability returns.
Each tool shows which plugin provides it (or its namespace, when the plugin cannot be identified), carries a Read, Write or Destructive label from the plugin’s own annotations (an unlabelled tool is treated as Destructive and says so), and gets a notice when it may return personal data (a hint from the plugin and tool name, not a full check). Tools a plugin update adds wait for your review.
A plugin that doesn’t declare its reads as read-only has them treated as writes, so read-only mode unloads them. A tool whose own permission check needs an item id is listed for anyone who can edit posts, and that plugin’s own check refuses the call if their role can’t run it.
Built on the Abilities API and the MCP Adapter
WordPress 6.9 added the Abilities API, and the official MCP Adapter turns those abilities into MCP tools. The Adapter comes bundled, so there is nothing else to install, and if you also run the standalone Adapter plugin, this plugin uses whichever copy loads first.
Page builders: Avada and WPBakery editable, the rest refused
A page builder owns its page’s layout, so an edit to the post text can report success and change nothing. For Elementor, Divi, Beaver Builder, Avada, Visual Composer, Oxygen, Breakdance, Brizy, Bricks and WPBakery the plugin’s general content tools refuse the write, though an excerpt-only edit goes through unless the plugin can’t tell which builder owns the post. Avada and WPBakery pages get their own editing tools, which refuse any save that changes anything else; Restore revision also works there.
Is this the right WordPress MCP plugin for you?
It fits if you want to decide tool by tool what an AI agent can do. Your AI client talks straight to your site: the plugin calls no AI provider, sends no telemetry and has no relay, account or API key of ours in the path.
It’s a poor fit if you want every tool on from day one, or an undo for every kind of change. The Changes tab can revert changes from 25 of this plugin’s tools for 30 days. Changes from its other tools can’t be undone, including permanent deletes, orders, refunds, user accounts and file uploads.
Compatible clients
Any MCP client that can reach your endpoint can connect. Claude (web and Desktop), ChatGPT and Manus are hosted apps and use OAuth, while Claude Code, Cursor, VS Code, Windsurf and Gemini CLI can use OAuth or an Application Password. The Gemini app has no known way to add a custom MCP server. A client that can’t connect directly can go through a bridge such as mcp-remote, which runs on your own machine.
Disclaimer
The Model Context Protocol is an open specification that Anthropic originally developed. Claude, ChatGPT, Cursor, VS Code, Gemini and other product names belong to their owners, and Agent Abilities for MCP is a third-party plugin that isn’t affiliated with, endorsed by or sponsored by any of them.
External Services
This plugin calls no AI provider and sends no telemetry.
It makes two kinds of outbound request on its own. The first is the Connection tab’s checks: requests from your site to its own address that test the MCP endpoint, header and body delivery and, with OAuth on, the discovery documents. The second only happens if you enable the upload-media-from-url ability, which is off by default: it fetches the exact HTTPS URL your AI client supplies so the file can be added to your media library, refuses private and reserved addresses and follows no redirects. The server at that URL sees the URL, your site’s IP address and the time of the request, and the request carries none of your content, credentials or site data. When an agent calls Avada Studio tools, Avada downloads content from avada.studio under your Avada registration; this plugin sends nothing. Avada’s terms and privacy policy apply.
Connecting a client happens in the client. Some clients reach your endpoint directly, and others use a bridge that runs on your own machine and is not bundled with the plugin:
- mcp-remote: https://www.npmjs.com/package/mcp-remote
- @automattic/mcp-wordpress-remote: https://www.npmjs.com/package/@automattic/mcp-wordpress-remote
Installation
- Upload the plugin to
/wp-content/plugins/agent-abilities-for-mcp, or install it from Plugins, Add New in your admin, then activate it. - Open Agent Abilities for MCP in the admin menu and, on the Abilities tab, switch on the tools you want the AI to have.
- On the Connection tab, copy your MCP endpoint and paste it into your AI client. Most clients ask you to approve the connection once in the browser, as your own account.
- If a client can’t use OAuth, create the low-privilege agent user the Connection tab offers, add an Application Password for it and connect with that, using the config the tab builds for you.
- Click Check my connection to confirm your server answers.
Each client has its own steps in the getting started guide and in connecting a client.
Changelog
Adds element editing for WPBakery Page Builder and Avada pages, their templates and Library, admin-only builder settings and block-theme navigation tools. Every new tool starts off. Divi pages are no longer overwritten by update-page, update-post and replace-in-post.
1.12.0
- Feature: Agents can edit WPBakery Page Builder and Avada pages element by element with tools such as avada-update-element and wpbakery-insert-template. Restore revision works there too. See every tool.
- Feature: Users who can manage options can change WPBakery settings, Avada Global Options, layouts and Slider settings, and import Avada Studio items. Page CSS and page options can be set per page.
- Feature: list-navigations and update-navigation read and replace block-theme menus, pages take a parent and a template, update-site-settings sets the static homepage, and wc-update-product can remove an attribute.
- Feature: Connection adds Add to Cursor and Add to VS Code links and can end tokens issued for an old site address. Other plugins is now Plugins’ own tools, and the accent follows your Admin Color Scheme.
- Fix: update-page, update-post and replace-in-post overwrote Divi page layouts and now refuse them, and avada-replace-text refuses a save that would strip other content.
- Fix: Expired or revoked OAuth tokens now get error=”invalid_token”, and alert emails go through WP-Cron on hosts that can’t finish the page before sending.
1.11.2
- Feature: A new Changes tab keeps 30 days of what agents changed with 25 tools and reverts a change if the item hasn’t been edited since, and a site-wide find and replace reverts as one group. Every write tool now reports whether its change can be undone, with a reason when it can’t (permanent deletes, orders, refunds).
- Feature: Two new tools, list-changes and undo-change, let an agent see and undo its own changes from the last 24 hours, up to 30 undo calls an hour per connection. Both start off, and undo-change is destructive, so the Read only, Content editor and Shop manager presets leave it out.
- Fix: wc-update-payment-gateway’s order is now a zero-based position, as wc-get-payment-gateway reports it, and the write renumbers the stored gateway order, so a script that passed a stored sort value now gets a position. wc-get-order returns payment_method and payment_method_title, a variation’s sale price can be cleared with an empty string, and WordPress’s export and erase personal data tools now cover the activity log and the new change history.
- Fix: A refund above the remaining amount, a user deleting their own account, deleting or demoting the last administrator, a missing reassign user, trashing an item already in the Trash and a tool aimed at a content type that isn’t exposed now each return a named error instead of a generic one.
- Chore: Change history is stored in its own table, which is dropped on every uninstall and emptied by Reset, and several tool descriptions and messages were reworded.
1.11.1
- Fix: The high-risk lock now holds wc-create-order, WooCommerce’s own order status and order update tools, and the Secure Custom Fields tools that can store a callback name, and its filter accepts other plugins’ slugs. Shop manager connections no longer reach wc-create-order, and post tools no longer reach a type whose own tool is off.
- Fix: Agent writes to WPBakery, Bricks, Oxygen, Breakdance and Brizy pages are refused, but a page builder’s post or page now accepts an edit that only sets the excerpt and keeps its stored content as it was, unless the plugin can’t tell which builder owns it. A role with only read_private_posts no longer lists other people’s drafts, the user meta tools can’t reach the MCP session store, Test connection no longer sends your login cookies to another host, and a bridged tool’s crash text no longer reaches the agent under WP_DEBUG.
- Fix: Bridged WooCommerce product create and update tools no longer leave ChatGPT stuck on an old tool list. Rank Math’s get-head shows a post’s own title and description, the Activity Log records which object each built-in write tool changed (a count for the site-wide replace), and invalid URLs, an event end before its start, a sale price above the regular price and similar bad input are refused with an error instead of being saved or ignored.
- Fix: A batch of smaller fixes across Quick Connect and Reset, subsite deletion, Force draft on product variations, meta tools that now say why a key was refused, the product types wc-create-product offers, protected excerpts, term backslashes, empty meta, SEO head and search answers, OAuth discovery on subfolder installs, and LiteSpeed and WP Fastest Cache purging after agent meta writes.
- Chore: Five old admin save actions are gone (a script calling them directly should use aafm_save_abilities_page), readme wording is corrected, and integration minimum versions are listed.
1.11.0
- Feature: The Other plugins tab says which plugin provides each group of tools (or its namespace, when the plugin cannot be identified), labels each tool Read, Write or Destructive from the plugin’s own annotations (an unlabelled tool is treated as destructive and says so), and marks tools that may return personal data such as form entries, orders, learner or member records. That mark is a hint from the plugin and tool name, not a full check.
- Feature: When a plugin update or a newly activated plugin adds tools, a “New tools since your last review” card lists them. They stay off until you switch them on, and Settings can send a notification for them.
- Feature: Each plugin on the Other plugins tab has an “Allow only read tools” button, and the Activity Log can filter to one plugin’s tools.
- Fix: A bridged tool’s error names the plugin, using the name from its header once cleaned up, for example “WPForms Lite” instead of “wpforms”, or names the tool namespace and says so when the plugin cannot be identified. The Quick Connect note no longer promises deletes go to Trash, the upload tools name the upload-files capability, and Content editor and Shop manager say they can read playbooks.
- Chore: The TEC events list says whose draft events it returns, the Avada descriptions lost a dash, and leftover internal notes came out of the plugin’s PHP comments.
1.10.2
- Fix: A request from another site’s web page now gets a 403 even when it carries wrong credentials, and responses requested with ?_envelope=1 send Cache-Control: no-store like every other response.
- Fix: Content editor and Shop manager connections can read playbooks. The Playbooks editor refuses to save over a playbook someone else changed after you opened it, and keeps your text in the form.
- Fix: The unknown ACF field refusal names fields only for callers who can list them. A paused connection no longer leaves a “paused” note in the server instructions after you resume it. An app the site no longer recognizes now gets the steps and MCP URL to add it again.
- Fix: Seven integration tool descriptions now match what the tools do, and every description that lists page builders names all five.
- Chore: The ability picker on the Playbooks tab has space between its search box and the count line.
1.10.1
- Feature: The new Playbooks tab holds step-by-step instructions for agents. Tick the abilities each one uses or add one of five starters. Two read tools, off until you enable them, let agents list and load Active playbooks.
- Fix: A paused connection now signs in and lists tools, and each tool call returns a message that the connection is paused. Claude used to show a firewall or sign-in error instead.
- Fix: The MCP endpoint refuses requests from web pages on other sites, as the MCP specification requires, and sends Cache-Control: no-store on every response. Clients that open with server discovery now get the playbook list too.
- Fix: A blocked address, the rate limit and an unknown ACF field name now say why in the refusal. An unreadable playbook list is reported rather than overwritten, and a connection row shows Saved after you save it.
- Chore: New FAQ answers cover refreshing a client’s tools, ChatGPT plans, playbooks and refused browser clients. The delete-tool and ChatGPT menu wording is corrected.
Screenshots
For developers
Is this your plugin? Show off the numbers.
Add a live badge to your site, docs or GitHub README. It updates on its own — no account needed.
Best Agent Abilities for MCP alternatives
All abilities-api plugins →FAQ
Agent Abilities for MCP: quick answers
Straight answers, pulled from live WordPress.org data.
Source: WordPress.org
Is Agent Abilities for MCP free?
Yes. Agent Abilities for MCP is free to download and use from the official WordPress.org plugin directory.
Is Agent Abilities for MCP safe to use in 2026?
Yes — Agent Abilities for MCP is a safe, well-maintained plugin to use in 2026. It runs on 1K+ sites, is rated 4.8/5 and was last updated 4 days ago, and scores 85/100 on our health check.
How many websites use Agent Abilities for MCP?
Agent Abilities for MCP is active on 1K+ WordPress websites and has been downloaded 16,510 times since it launched in July 2026. It was downloaded 6,970 times in the last 30 days.
Does Agent Abilities for MCP work with WordPress 7.1?
Yes. The developer has tested Agent Abilities for MCP up to WordPress 7.1.5, the latest release. It requires WordPress 6.9 or newer.
What PHP version does Agent Abilities for MCP need?
Agent Abilities for MCP requires PHP 7.4 or higher. Most hosts run PHP 8.x today, so it works on any modern WordPress hosting.
When was Agent Abilities for MCP last updated?
The latest version, 1.12.0, was released on November 15, 2026 (4 days ago).
Who makes Agent Abilities for MCP?
Agent Abilities for MCP is developed and maintained by Unaib Amir.
What are the best alternatives to Agent Abilities for MCP?
The most popular alternatives to Agent Abilities for MCP are MCP Adapter (70K+ installs), AgizoAI Agentic Browsing Op… (100+ installs) and HLB Ability Registry for MCP (10+ installs).
Powered by PageForge
One template and a spreadsheet. A real page for every search.
PageForge turns each row of a CSV into a WordPress page with its own title, URL, SEO fields and schema, built on the layout you already designed. Free on WordPress.org.
- CSV and XLSX, plus Google Sheets on Professional and Enterprise
- Its own title, URL, SEO fields and schema for every page
- Works with the block editor, Elementor, Divi and Avada
- Free on WordPress.org, no credit card
