Title: Agent Abilities for MCP – MCP Server for AI Agents Author: Unaib Amir Published: July 2, 2026 Last modified: July 2, 2026 --- Search plugins ![](https://ps.w.org/agent-abilities-for-mcp/assets/banner-772x250.png?rev=3594360) ![](https://ps.w.org/agent-abilities-for-mcp/assets/icon-256x256.png?rev=3594360) # Agent Abilities for MCP – MCP Server for AI Agents By [Unaib Amir](https://profiles.wordpress.org/unaibamir/) [Download](https://downloads.wordpress.org/plugin/agent-abilities-for-mcp.1.0.0.zip) * [Details](https://wordpress.org/plugins/agent-abilities-for-mcp/#description) * [Reviews](https://wordpress.org/plugins/agent-abilities-for-mcp/#reviews) * [Installation](https://wordpress.org/plugins/agent-abilities-for-mcp/#installation) * [Development](https://wordpress.org/plugins/agent-abilities-for-mcp/#developers) [Support](https://wordpress.org/support/plugin/agent-abilities-for-mcp/) ## Description Agent Abilities for MCP is a WordPress plugin that turns your site into a governed Model Context Protocol (MCP) server. It exposes 153 curated WordPress “abilities”( tools) to AI agents like Claude, Cursor, and VS Code over MCP, so your AI client can read and, when you allow it, write to your site as a real, least-privilege WordPress user you choose. It is built on the WordPress 6.9 Abilities API and the official MCP Adapter, so there is no custom server or transport to trust. Nothing is exposed until you turn it on. The agent only ever acts as the WordPress user you bind it to, never an admin-equivalent key, and every call is re-checked against that user’s capabilities and logged before it runs, denials included. You add reach as you build trust, not all at once. Your own AI client connects in to your site; the plugin makes zero outbound calls and has no telemetry. Model Context Protocol (MCP) is an open specification originally developed by Anthropic. Claude, ChatGPT, Cursor, VS Code, Gemini, and other product names are trademarks of their respective owners. Agent Abilities for MCP is a third-party plugin and is not affiliated with, endorsed by, or sponsored by any of them. #### 🛡️ Least-privilege access by design * **Least privilege by design.** The AI agent connects as a real, scoped WordPress user through OAuth or an Application Password, never an admin-equivalent key. * **Off by default.** Nothing is exposed until you enable it, and updates never silently widen access. * **Two-layer capability gating.** A connection only sees the tools its user can call, and every call re-checks that capability before it runs. * **Honest audit log.** Every call is recorded, denied attempts included, with the principal and the argument keys (never the values). It lives in your own database and clears from the admin. * **Bounded by construction.** No arbitrary option or meta access, no remote URL fetch, no code execution. Uploads are decoded from inline data and checked by their real bytes against an image allow-list, never fetched from a URL. A created user gets the site default role, never admin, and the last administrator can never be removed. Anything destructive is off by default and capability-gated, and deletes go to Trash where the ability supports it. * **Optional safety controls.** Switch on a per-minute rate limit, an IP allowlist, a force-to-draft mode, or a title-length cap. All four stay off until you set them. * **No data leaves your site.** The plugin contacts no AI provider and no external service. Your AI client connects in; the plugin never reaches out. * **Two ways to connect.** Approve an agent in the browser over OAuth, with no secret to store, or point a dedicated low-privilege user at an Application Password. A guided screen builds the client config and checks the endpoint for you. #### 🤖 Built on the WordPress Abilities API and MCP Adapter WordPress 6.9 ships the Abilities API and the official MCP Adapter. Agent Abilities for MCP registers a curated, governed set of abilities on top of them rather than inventing its own protocol or transport. It builds on the official MCP Adapter library( wordpress/mcp-adapter) rather than a custom server, so there is no bespoke server to trust and the plugin inherits the standard’s behavior. What it adds is the governance layer: the off-by-default catalog, the capability gating, the safety controls, and the audit log for running the Model Context Protocol on WordPress. #### 📦 153 governed abilities Version 1.0.0 ships **153 governed abilities: 83 across WordPress core and 70 from auto-detected integrations.** Every one is off until you enable it, scoped to the bound user, capability-gated, and logged. **WordPress core (83 abilities).** Reads plus guarded writes across your whole site: * **📝 Posts & Pages:** list, read, create, update, and delete posts and pages, with destructive actions off by default and deletes routed to Trash. * **🏷️ Terms & Taxonomies:** manage categories, tags, and custom taxonomy terms. * **💬 Comments:** read and moderate the comment queue. * **🖼️ Media:** list and read the media library, and add images decoded from inline data and validated by their real bytes against an image allow-list (never fetched from a URL). * **🗂️ Post Meta:** read and write only the meta keys an administrator has explicitly allowlisted. Protected, underscore-prefixed, and authentication keys can never be allowlisted. * **👥 Users:** read and manage users within capability limits. A new user gets the site default role, never admin, and the last administrator can never be removed. * **🧭 Site structure:** work with menus and the structural pieces that hold the site together. * **🕓 Revision history:** read the revision trail for content. * **🧱 Blocks & Templates:** work with reusable blocks, themes, and templates. * **⚙️ Limited settings & site health:** a tightly scoped set of settings, plus read-only site health and plugin status. * **🔍 Site-wide search:** one search that spans every post type at once. **Integrations (70 abilities).** Detected automatically per active plugin, off until you turn them on, capability-gated, and logged. Each appears only while its host plugin is active: * **🛒 WooCommerce MCP (52 abilities):** read and write products, orders, and customers so an AI agent can help run your store. These touch real customer and order data, including personal data such as names, emails, and addresses, so they sit behind a clear admin notice and stay off until you switch them on. * **🧩 Advanced Custom Fields (7 abilities):** read and write ACF field data. Like WooCommerce, these can reach real personal data and sit behind the same clear notice. * **📈 Rank Math SEO (5 abilities):** read and manage Rank Math SEO data. * **📈 Yoast SEO (3 abilities):** read and manage Yoast SEO data. * **📈 All in One SEO (3 abilities):** read and manage AIOSEO data. More integrations are planned. #### 🔌 Connect Claude, Cursor and other MCP clients Connect any MCP client that can reach your endpoint: Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI, some directly and some through the open- source `mcp-remote` bridge that runs on your own machine. With OAuth you paste the endpoint URL and approve once in the browser; with an Application Password you point a low-privilege user at the endpoint. Hosted ChatGPT and Gemini apps want a streamable HTTP/SSE remote connector that the underlying adapter does not serve natively yet. ### External Services This plugin does not contact any external service. It registers abilities on your own site and answers the requests your AI client sends to it. It makes no outbound requests of its own and includes no analytics or telemetry. Connecting an AI client to your site is done by the client, not by this plugin. Some MCP clients reach your endpoint directly; others use a small bridge program that runs on your own computer, such as the open-source `mcp-remote` tool or `@automattic/ mcp-wordpress-remote`. Neither bridge is bundled with this plugin or run by it. You install and run it yourself, and it talks only to your site and your local AI client. Their terms are on their own pages: * mcp-remote: https://www.npmjs.com/package/mcp-remote * @automattic/mcp-wordpress-remote: https://www.npmjs.com/package/@automattic/mcp- wordpress-remote ## Screenshots [⌊The dashboard walks you through setup with a three-step checklist and shows enabled abilities, agent activity, audit size, and your MCP endpoint at a glance.⌉⌊The dashboard walks you through setup with a three-step checklist and shows enabled abilities, agent activity, audit size, and your MCP endpoint at a glance.⌉[ The dashboard walks you through setup with a three-step checklist and shows enabled abilities, agent activity, audit size, and your MCP endpoint at a glance. [⌊Connect over OAuth by pasting your site URL and approving once in the browser. An Application Password is there as a fallback.⌉⌊Connect over OAuth by pasting your site URL and approving once in the browser. An Application Password is there as a fallback.⌉[ Connect over OAuth by pasting your site URL and approving once in the browser. An Application Password is there as a fallback. [⌊Nothing is exposed until you switch it on. Abilities are grouped by area, each with its own toggle and an enable-all per section.⌉⌊Nothing is exposed until you switch it on. Abilities are grouped by area, each with its own toggle and an enable- all per section.⌉[ Nothing is exposed until you switch it on. Abilities are grouped by area, each with its own toggle and an enable-all per section. [⌊Integrations for WooCommerce, ACF, and SEO show up only while the host plugin is active, and each one stays off until you turn it on.⌉⌊Integrations for WooCommerce, ACF, and SEO show up only while the host plugin is active, and each one stays off until you turn it on.⌉[ Integrations for WooCommerce, ACF, and SEO show up only while the host plugin is active, and each one stays off until you turn it on. [⌊The activity log records every call: who made it, which ability, and whether it succeeded or was denied.⌉⌊The activity log records every call: who made it, which ability, and whether it succeeded or was denied.⌉[ The activity log records every call: who made it, which ability, and whether it succeeded or was denied. ## Installation 1. Upload the plugin to the `/wp-content/plugins/agent-abilities-for-mcp` directory, or install it from the WordPress plugins screen. 2. Activate it from the Plugins screen. 3. Open the Agent Abilities for MCP menu in your admin sidebar. On the Abilities tab, turn on only the abilities you want the agent to have. Everything starts off. 4. On the Connection tab, copy your site’s MCP endpoint. The simplest path is OAuth: paste the endpoint into your MCP client and approve the connection once in the browser, where the agent acts as your own account. 5. Prefer not to use OAuth, or on a client that can’t? Create the dedicated low-privilege agent user the Connection tab offers, generate an Application Password for it, and connect with that instead. 6. Use the connection check on the Connection tab to confirm the endpoint is reachable from your server. ## FAQ ### Does the agent get admin access? No. The agent authenticates as whatever WordPress user you bind it to. Point it at the dedicated low-privilege user the plugin can create for you, and it can only do what that user can do. Each ability also re-checks the user’s capability before it runs, so a connection can never call a tool its user is not allowed to use. ### Is it safe to connect an AI agent to my WordPress site? Yes, when the connection is scoped, which is what this plugin is built around. The agent connects as a real, least-privilege WordPress user you choose, never an admin- equivalent key. Every ability is off until you enable it, each call re-checks the user’s capability before it runs, and every call is logged, denied attempts included. The plugin itself never holds an admin-equivalent key. ### What can an agent actually do? Only the abilities you have enabled, and only within the bound user’s capabilities. The catalog is reads and guarded writes over posts, pages, terms, comments, media, post meta, and site structure, plus revision history and a search that spans every post type at once. There is no ability to change options arbitrarily, change roles, fetch a remote URL, or run code. An agent can only write post meta for keys an administrator has explicitly allowlisted, and protected, underscore-prefixed, and authentication keys can never be allowlisted. Deletes move content to Trash where the ability supports it, and the permanent ones are off by default and capability-gated. ### How does the plugin handle tools and access? Agent Abilities for MCP ships everything off, binds the agent to one WordPress user you pick, re-checks that user’s capability on every call, and logs every call including denials. You add reach as you build trust, not all at once. It trades raw tool count for control you can audit. ### Is it free? Yes. Agent Abilities for MCP is free on WordPress.org, with no paid tier, no API key to buy, and no usage limits added by the plugin. ### Does it work with my other plugins? Yes, for a set of supported plugins. When one is active, Agent Abilities for MCP adds abilities for it under the same rules as the core: detected automatically, off until you turn them on, capability-gated, and logged. Version 1.0.0 covers WooCommerce, Advanced Custom Fields, and SEO (Yoast, Rank Math, and All in One SEO). The WooCommerce and ACF abilities can read and write real customer and order data, including personal data such as names, emails, and addresses, so they sit behind a clear notice in the admin and stay off until you switch them on. More integrations are planned. ### Is this the same as the WordPress Abilities API, or the official MCP adapter? It is built on both. WordPress 6.9 ships the Abilities API and the official MCP Adapter; Agent Abilities for MCP registers a curated, governed set of abilities on top of them rather than inventing its own protocol or transport. So there is no bespoke server to trust, and the plugin inherits the standard’s behavior. What it adds is the governance layer: the off-by-default catalog, the capability gating, the safety controls, and the audit log. ### What’s the difference between this and the WordPress REST API? The REST API exposes raw endpoints. MCP describes your site’s abilities as discoverable tools an AI agent can reason about and call, and this plugin wraps each one in a governance layer: off by default, capability-gated on every call, and logged. It is the same underlying WordPress, governed so an agent can drive it within the limits you set. ### Which WordPress version do I need? WordPress 6.9 or newer, which is where the Abilities API and the official MCP Adapter the plugin builds on are available. PHP 8.0 or newer is required. ### Which AI clients work? Any MCP client that can reach your site’s endpoint. With OAuth you paste the endpoint URL into the client and approve the connection once in the browser; clients like Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI connect this way, some directly and some through the mcp-remote bridge that runs on your own machine. You can also connect with an Application Password instead of OAuth. The hosted ChatGPT and Gemini apps want a streamable HTTP/SSE remote connector, which the underlying adapter does not serve natively yet. ### Does it work with ChatGPT? Not the hosted ChatGPT app yet. It needs a streamable HTTP/SSE remote connector that the underlying MCP Adapter does not serve natively yet. Claude Desktop, Claude Code, Cursor, VS Code, Windsurf, and Gemini CLI all work today, some directly and some through the mcp-remote bridge that runs on your own machine. ### I’m on Windows and the config won’t start. Windows MCP clients can’t launch the npx shim by name. Wrap it in cmd: set “command” to “cmd” and put “/c”, “npx” at the front of “args”. The Connection tab has a Windows tab that generates this for you. ### My agent can’t connect to a local or staging site. Local stacks like DDEV, Local, and Valet serve a self-signed certificate that Node rejects, so the proxy never reaches WordPress. For local testing only, add “NODE_TLS_REJECT_UNAUTHORIZED”:“ 0” to the “env” block (the Connection tab adds it automatically when it detects a local site). Don’t ship that setting to production. A public site has a trusted certificate and doesn’t need it. ### OAuth discovery returns 403 or 404 on my server. When OAuth is enabled, clients find your site by fetching two documents under /. well-known/: /.well-known/oauth-protected-resource and /.well-known/oauth-authorization- server. WordPress serves both, but the request has to actually reach WordPress. Some servers deny anything that starts with a dot before PHP runs, and that blocks discovery. On nginx the usual cause is a dotfile deny rule (location ~ /. { deny all; }). Add a more specific block ahead of it so /.well-known/ falls through to WordPress: location ^~ /.well-known/ { try_files $uri $uri/ /index.php?$args; } The ^~ prefix tells nginx to prefer this block over the dotfile deny. Other hidden files stay denied. Apache usually works as-is, because the WordPress .htaccess sends anything that isn’t a real file to index.php, /.well-known/ included. If a host or security plugin is blocking dotfiles, look for that rule (often in the vhost or a hardening snippet, not WordPress itself) and let /.well-known/ through. To check, request https://your-site/.well-known/oauth-protected-resource. A working setup returns a JSON document instead of a 403 or 404. ### Is there rate limiting? Yes. Set a per-minute cap on the Settings tab under “Rate limit (per minute)”. Each connection can make that many agent calls a minute, counted per agent user; 0 turns the limit off. Calls over the cap are denied and logged on the Activity Log tab, so you can spot a connection that keeps hitting it. ### Does it send my content to OpenAI, Anthropic, or Google? No. The plugin connects to no AI provider and makes no outbound requests of its own. Your own AI client connects in to your site and calls the abilities you have enabled. Whatever your AI client does with the results afterward is between you and whoever makes that client. ### Does it send data anywhere? No. The plugin contacts no external service and has no telemetry. Your agent talks directly to your site. ### What gets logged? Every ability call, whether it started, succeeded, errored, or was denied, with the acting user, the ability name, and the argument keys. Argument values are never stored. The activity log lives in your own database and can be cleared from the admin screen. ### How do I report a security issue? Please report security issues privately rather than in the support forum, so a fix can ship before details are public. Use the security contact listed on the plugin’s GitHub repository. ## Reviews There are no reviews for this plugin. ## Contributors & Developers “Agent Abilities for MCP – MCP Server for AI Agents” is open source software. The following people have contributed to this plugin. Contributors * [ Unaib Amir ](https://profiles.wordpress.org/unaibamir/) [Translate “Agent Abilities for MCP – MCP Server for AI Agents” into your language.](https://translate.wordpress.org/projects/wp-plugins/agent-abilities-for-mcp) ### Interested in development? [Browse the code](https://plugins.trac.wordpress.org/browser/agent-abilities-for-mcp/), check out the [SVN repository](https://plugins.svn.wordpress.org/agent-abilities-for-mcp/), or subscribe to the [development log](https://plugins.trac.wordpress.org/log/agent-abilities-for-mcp/) by [RSS](https://plugins.trac.wordpress.org/log/agent-abilities-for-mcp/?limit=100&mode=stop_on_copy&format=rss). ## Changelog #### 1.0.0 * Initial release. 153 governed abilities: 83 across WordPress core (reads and guarded writes for posts, pages, terms, comments, media, users, post meta, revisions, blocks, templates, and site structure, plus a search that spans every post type), and 70 from auto-detected integrations for WooCommerce, Advanced Custom Fields, Yoast, Rank Math, and All in One SEO. Built on the WordPress Abilities API and the official MCP Adapter, with no custom transport. Connect over OAuth in the browser or with a least-privilege Application Password user. Everything off by default, two-layer capability gating, per-connection tool filtering, optional safety controls (rate limit, IP allowlist, force-draft, title-length cap), an audit log that records denials, and a guided connection screen with diagnostics. ## Meta * Version **1.0.0** * Last updated **13 hours ago** * Active installations **Fewer than 10** * WordPress version ** 6.9 or higher ** * Tested up to **7.0** * PHP version ** 8.0 or higher ** * Tags * [AI agent](https://wordpress.org/plugins/tags/ai-agent/)[ChatGPT](https://wordpress.org/plugins/tags/chatgpt/) [content management](https://wordpress.org/plugins/tags/content-management/)[mcp](https://wordpress.org/plugins/tags/mcp/) [woocommerce](https://wordpress.org/plugins/tags/woocommerce/) * [Advanced View](https://wordpress.org/plugins/agent-abilities-for-mcp/advanced/) ## Ratings No reviews have been submitted yet. [Your review](https://wordpress.org/support/plugin/agent-abilities-for-mcp/reviews/#new-post) [See all reviews](https://wordpress.org/support/plugin/agent-abilities-for-mcp/reviews/) ## Contributors * [ Unaib Amir ](https://profiles.wordpress.org/unaibamir/) ## Support Got something to say? Need help? [View support forum](https://wordpress.org/support/plugin/agent-abilities-for-mcp/)