Do these 3 things before closing this tab:
1Fix the driver behind crashes, sound loss and screen glitches2Repair Windows errors before they cause bigger problems3Scan for outdated or missing drivers - takes under a minuteFor most site owners, the right choice depends on what you want an AI client to do: use WordPress MCP Adapter as the official bridge to abilities, add Agent Abilities for MCP for a broad, governed catalog, or add Agent Toolbelt for site diagnostics and maintenance actions. The adapter does not provide a large content-management tool catalog on its own; it exposes abilities registered by WordPress and plugins. This comparison reflects project documentation checked on October 3, 2026, not hands-on compatibility or security testing.
How the WordPress MCP options differ
MCP, the Model Context Protocol, connects an AI client to tools and other capabilities exposed by a server. In WordPress, the key distinction is between the adapter that provides the connection and plugins that register abilities for it to expose. WordPress calls these registered capabilities abilities; an MCP client sees exposed abilities as tools.
| Option | What it adds | Capabilities and exposure | Authentication and stated compatibility |
|---|---|---|---|
| WordPress MCP Adapter | The official server and transport bridge between WordPress abilities and MCP. | Its three default meta-tools discover abilities, retrieve ability details, and execute an ability. WordPress core supplies a small baseline for site, authenticated-user, and environment information; additional functionality comes from plugins or custom code. Abilities are private by default on the default server. | Supports HTTP and STDIO. The official guidance describes WP-CLI user authentication for local STDIO and application passwords or custom OAuth through a remote proxy for HTTP. WordPress 6.9 is identified as the release shipping the Abilities API; confirm the adapter release and client combination you plan to use. |
| Agent Abilities for MCP | A governed catalog layered on the Abilities API and official adapter, with integrations and the ability to bridge abilities registered by other plugins. | Its WordPress.org listing advertises 179 abilities: 85 core and 94 from auto-detected integrations. Listed areas include WordPress content and site tasks, WooCommerce, ACF, SEO, events, and tickets. The listing says abilities are disabled until enabled, capability-checked, and logged. | The listing states WordPress 6.9+ and PHP 7.4+. It describes OAuth or an Application Password for a low-privilege user, and names Claude clients, ChatGPT custom connectors, Cursor, VS Code, Windsurf, Gemini CLI, and Manus. It says hosted Gemini is not supported. These are publisher claims and client support can change. |
| Agent Toolbelt | Diagnostics and site-operations abilities for use through the official adapter. | Its listing describes read-only status, health, logs, updates, cron, and checksum checks, alongside higher-risk operations such as updates, rollback, toggling components, and database cleanup. The listing says destructive actions are disabled by default and risky execution uses dry runs and a confirmation token. | The listing gives an Application Password setup for MCP endpoint use. It says WooCommerce 10.9+ includes the same adapter when its MCP feature is enabled; this is not a general compatibility guarantee for all WordPress sites or clients. |
| Automattic wordpress-mcp | Archived historical implementation. | Not a current choice for a new connection. | The repository says it is deprecated and archived, and directs users to WordPress/mcp-adapter for ongoing development. |
The 179-ability figure and its breakdown are Agent Abilities for MCP listing claims, not independent measurements. No independent performance, adoption, or security-audit statistics are established here.
Which option fits your use case?
- Choose the MCP Adapter if you are building an integration around existing or custom WordPress abilities and need the official transport bridge. Plan to configure which abilities are exposed; installing the adapter alone does not give an AI client broad editing or administration powers.
- Consider Agent Abilities for MCP if you want a prebuilt catalog spanning WordPress and supported integrations, with documented enablement and capability checks. Review the specific abilities you enable, particularly those involving customer or order information.
- Consider Agent Toolbelt if your goal is operational visibility or maintenance, and you understand the impact of actions that can change plugins, themes, or database records. Read-only checks and write operations should not be treated as equivalent risk.
- Do not start a new setup on Automattic’s archived wordpress-mcp repository. Its maintainers point to the official adapter instead.
How abilities become available to an MCP client
The adapter exposes registered WordPress abilities, but exposure is controlled. WordPress documentation states that abilities are private by default. An ability must be marked public for access through the default server, or explicitly included on a custom server. That means a plugin can register abilities without making every one of them automatically available to every client.
When comparing extensions, check whether enablement is per ability, whether calls enforce the connected user’s capabilities, and whether activity is logged. These controls are described by the projects, but they do not replace reviewing the permissions and effects of each operation on your own site.
Authentication and transport: local versus remote
Local connections with STDIO
For local development, the official WordPress guidance shows invoking the adapter with wp mcp-adapter serve and selecting a WordPress user. This approach requires WP-CLI to be available in the local environment. The abilities available to calls are governed by the selected user’s WordPress permissions.
Rank #2
- Book - 1, 000 books to read before you die: a life-changing list (1000 before you die)
- Language: english
- Binding: hardcover
HTTP connections to a site
For HTTP, the official guide shows the @automattic/mcp-wordpress-remote proxy with Application Password credentials; it also notes that custom OAuth implementations are possible. Agent Abilities for MCP separately advertises OAuth and Application Password support for its endpoint. Agent Toolbelt documents an Application Password setup; its interoperability claims alone do not establish OAuth support.
Credentials are not interchangeable in scope. The Agent Abilities for MCP listing says its OAuth tokens are endpoint-specific, while an Application Password is a WordPress credential whose effective access follows the account’s role. It also says requests act as the WordPress user who authorized them. Treat these as the plugin publisher’s descriptions, and verify the actual permissions and behavior in your deployment.
Free tools Windows power users keep installed
One-click scans. No signup required.
WordPress, PHP, WooCommerce, and client compatibility
The clearest minimum-version statements in the available project documentation are specific to individual components. Agent Abilities for MCP lists WordPress 6.9+ and PHP 7.4+. The adapter’s documentation identifies WordPress 6.9 as the release that ships the Abilities API. Agent Toolbelt says WooCommerce 10.9+ includes the same adapter when its MCP integration feature is enabled; do not read that as a universal WordPress or PHP requirement.
Agent Abilities for MCP names Claude clients, ChatGPT custom connectors, Cursor, VS Code, Windsurf, Gemini CLI, and Manus, while stating hosted Gemini is not supported. Its listing says ChatGPT setup depends on Developer Mode/custom connector availability and an eligible plan. These are changing product claims, not a guarantee that every named client works with every transport, plugin release, or account tier.
The project documentation does not establish a tested, release-by-release matrix spanning plugin, WordPress, PHP, transport, and MCP client versions. Before deployment, confirm the current release notes and client instructions for the exact combination you will use, then test it on a staging site.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Security and operational risks to review
WordPress developer guidance recommends a dedicated user with only the capabilities required for the intended tasks. For public HTTP servers, it recommends preferring read-only abilities, using careful permission callbacks rather than unrestricted access for destructive operations, and monitoring and logging usage.
- Limit the account. Calls run with the connected WordPress user’s authority; avoid using a full administrator account when a narrower role will do.
- Review each enabled ability. Identify whether it reads site content, exposes customer or order data, changes content or configuration, or deletes records.
- Use safeguards for writes. Agent Toolbelt’s listing describes dry-run previews and confirmation tokens for risky operations, but also includes actions that can change plugins or themes and delete database records. A confirmation flow does not make an operation harmless.
- Check logs and access boundaries. Agent Abilities for MCP and Agent Toolbelt describe logging or audit records in their listings. Confirm what your installed version records and who can access those records.
Agent Abilities for MCP’s listing specifically warns that WooCommerce and ACF abilities may access real customer, order, or personal information. Enable only the integrations and actions needed for the workflow, and account for the data they can reach.
Do not confuse the site adapter with WordPress.org’s MCP server
WordPress.org also documents an MCP server for its Plugin Directory workflow, including plugin guidelines, README validation, submission status, and submission actions. That is a different service from installing an MCP server on your own WordPress site to expose that site’s abilities.
Sources and scope
Capability, authentication, compatibility, and safety descriptions above are attributed to the projects’ own documentation and plugin listings checked on October 3, 2026. They are useful for choosing an architecture and shortlist, but do not constitute hands-on testing or independent security validation.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
