Recommended Free Tools
WordPress MCP Adapter is the official plugin that connects the WordPress Abilities API to the Model Context Protocol (MCP). It lets compatible MCP clients discover and use abilities that have been explicitly made public; installing the adapter does not automatically expose every ability or add AI features to a site. The latest release listed on the project’s releases page is v0.7.0, dated October 2, 2026.
What the MCP Adapter does—and what it does not do
The adapter is protocol and server plumbing for WordPress. It makes abilities registered by WordPress core or other plugins available to MCP clients as tools, resources, or prompts, depending on their purpose and configuration. It does not create those abilities, provide an AI assistant, or decide what an AI agent should do. The project describes it as part of WordPress’s AI Building Blocks initiative and licenses it under GPL-2.0-or-later. Official project overview
As an Amazon Associate I earn from qualifying purchases.
In practical terms, an ability is the capability being offered; MCP is the interface a compatible client uses to discover or interact with it. The adapter’s default server includes abilities for discovering available abilities, retrieving information about an ability, and executing one. These map to MCP tools, allowing a client to find a capability, inspect it, and then invoke it where permitted. WordPress Developer Blog overview
Quick wins for a faster PC:
Repair Windows errors before they cause bigger problemsFix Now →Fix the driver behind crashes, sound loss and screen glitchesFind Drivers →Clear out junk files and repair common Windows errorsFree Scan →What installing the plugin enables
After activation, the plugin initializes a default MCP server. Its default HTTP endpoint is /wp-json/mcp/mcp-adapter-default-server. The project also lists STDIO transport and an interface for custom transports, so the endpoint is not the only possible way to connect. Which connection method is appropriate depends on the MCP client and how the WordPress site is hosted and administered. Transport and project details
#1 Best Overall
Installing the adapter alone does not make a site’s abilities available. A capability must be registered, and exposure through the default server is opt-in: abilities need to be explicitly marked public for MCP. Before an ability runs, WordPress still checks permissions for the current WordPress user. That means public exposure and execution authorization are separate parts of the boundary: the first determines whether the MCP server offers the ability, while the second governs whether the current user may carry it out. WordPress.org plugin listing Developer Blog setup explanation
Install the canonical plugin
The project recommends installing the canonical WordPress plugin rather than bundling the adapter as a Composer library in another plugin. Its installation guide provides a WP-CLI command that downloads and activates the latest release:
wp plugin install https://github.com/WordPress/mcp-adapter/releases/latest/download/mcp-adapter.zip --activateAlternatively, download the latest release and install it through WordPress’s plugin interface. After activation, the default server uses the endpoint shown above. The installation documentation notes that the WordPress plugin dependency mechanism requires directory listing and references an open issue related to submission support; verify current plugin-directory and dependency mechanics if they affect your deployment. Official installation guide
What changed in v0.7.0
The project’s releases page lists v0.7.0, released October 2, 2026, as the latest release. It adds support for MCP revision 2026-07-28 and uses schemas for the exact requested revision. Clients requesting 2025-06-18 or 2024-11-05 can still connect through the 2025-11-25 schema. These are compatibility details for client and integration developers, not a change that makes every WordPress ability public. Official release notes Official changelog
Rank #3
The release also contains breaking changes for integrations that rely on extension-facing or internal implementation details. The release notes report removal of generated DTO classes, three validator classes, and a validation filter. Custom transports must delegate to HttpRequestHandler or McpWireOrchestrator. Components malformed for every supported revision are now rejected rather than silently repaired, and use of the adapter as a bundled Composer library is deprecated. v0.7.0 release notes
Upgrade checklist for site and integration developers
- Check how the adapter is installed. If it is bundled as a Composer library inside another plugin, note that this approach is deprecated; the project recommends the canonical plugin.
- Review custom transport code. Update integrations to delegate to
HttpRequestHandlerorMcpWireOrchestratoras required by the release notes. - Search for removed internals. Check whether your code references generated DTO classes, the three removed validator classes, or the removed validation filter.
- Validate components against supported revisions. Inputs malformed for all supported revisions will now be rejected instead of repaired silently, so integrations that depended on permissive handling may need changes.
- Read the migration guide before upgrading. The project says existing ability registration,
create_server(), and WordPress hooks continue working, but integrations using custom handlers, transports, or internal component structures should review the v0.7.0 migration details. Release and migration information
Choose the connection and ability type that fit
There is no buyer-style product comparison to make here; the practical decisions are about how a client connects and what kind of capability it needs. The project lists HTTP and STDIO transports, plus a custom transport interface. Abilities may be surfaced as tools, resources, or prompts according to their purpose and configuration. Use the canonical plugin installation for a standard WordPress deployment rather than building around the deprecated bundled-library approach. Project overview Installation guide
HTTP
Use the default HTTP server when the MCP client can connect to the WordPress endpoint. The default path is /wp-json/mcp/mcp-adapter-default-server.
Windows Errors? Fix Them Before They Spread
Repair common Windows errors and clear accumulated junk for a smoother, more stable PC - no reinstall needed.Free scan · no reinstallCrashes, No Sound, or Screen Glitches?
Random freezes, missing sound and display glitches usually trace back to one bad driver. Find and replace yours safely.Free scan · under a minuteSTDIO or a custom transport
The project lists STDIO and a custom transport interface for other integration patterns. Custom transport implementers should account for the v0.7.0 delegation changes before upgrading.
Tool, resource, or prompt
Tools support discoverable and executable behavior, as illustrated by the default discovery, information, and execution abilities. Resources and prompts are also supported forms of exposure; configure an ability according to its role rather than treating every capability as an executable action.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.Frequently Asked Questions
What is MCP Adapter?
It is the official WordPress plugin that connects the Abilities API to MCP clients, exposing explicitly public abilities as MCP tools, resources, or prompts.
How do AI agents connect to my site?
A compatible MCP client connects through the adapter’s configured transport. The default HTTP endpoint is /wp-json/mcp/mcp-adapter-default-server; the project also lists STDIO and custom transports.
Does every registered ability get exposed automatically?
No. Abilities must be explicitly marked public for MCP to be exposed by the default server, and WordPress checks the current user’s permissions before execution.
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.
