WordPress MCP Adapter

Content

WordPress MCP Adapter is the official WordPress package for exposing WordPress Abilities API functionality to MCP clients. It converts selected WordPress abilities into MCP tools, resources, and prompts, with support for HTTP and STDIO transports, multiple MCP servers, custom permissions, validation, observability, and error handling.

The default server exposes reviewed public abilities through adapter tools such as ability discovery, ability metadata lookup, and ability execution. Developers can also create custom MCP servers with explicit tool, resource, prompt, and transport configuration.

Source Review

• https://github.com/WordPress/mcp-adapter
• https://github.com/WordPress/mcp-adapter/blob/trunk/README.md
• https://github.com/WordPress/mcp-adapter/blob/trunk/composer.json
• https://github.com/WordPress/mcp-adapter/blob/trunk/docs/guides/transport-permissions.md
• https://repo.packagist.org/p2/wordpress/mcp-adapter.json

Verified on 2026-06-18. The repository README identifies MCP Adapter as part of the AI Building Blocks for WordPress initiative and documents plugin, Composer, WP-CLI STDIO, and HTTP transport setup. Packagist lists wordpress/mcp-adapter as a GPL-2.0-or-later WordPress plugin package.

Features

• Convert WordPress Abilities API registrations into MCP tools, resources, and prompts.
• Use HTTP transport for REST-style MCP access or WP-CLI STDIO for local development and local MCP clients.
• Create multiple MCP servers with separate IDs, namespaces, routes, transports, exposed abilities, resources, prompts, error handlers, and observability handlers.
• Discover public abilities, inspect ability metadata, and execute reviewed abilities through the default server.
• Add custom transport permission callbacks and per-ability permission checks.
• Install as a WordPress plugin or require as a Composer dependency inside another plugin.

Installation

Install the WordPress plugin release with WP-CLI:

wp plugin install https://github.com/WordPress/mcp-adapter/releases/latest/download/mcp-adapter.zip --activate

For local MCP clients using WP-CLI STDIO:

{
  "mcpServers": {
    "wordpress-default": {
      "command": "wp",
      "args": [
        "--path=/path/to/your/wordpress/site",
        "mcp-adapter",
        "serve",
        "--server=mcp-adapter-default-server",
        "--user=admin"
      ]
    }
  }
}

Plugin developers can also install the library with Composer:

composer require wordpress/mcp-adapter

Use Cases

• Let an agent discover and invoke reviewed WordPress abilities from a local development site.
• Build a plugin that exposes specific content, editorial, ecommerce, or admin actions through a custom MCP server.
• Use WP-CLI STDIO to test MCP tools before opening HTTP access.
• Connect Claude, Cursor, VS Code, or other MCP clients to WordPress ability workflows.
• Create role-specific MCP servers with different exposed abilities and transport permission callbacks.

Safety and Privacy

The adapter is only as safe as the abilities and permissions exposed through it. Treat every public ability as an agent-callable API surface. Keep production sites locked down, use least-privilege users, require per-ability permission callbacks, and avoid exposing write-heavy or destructive operations without a human approval step.

For HTTP transport, protect application passwords and API URLs, prefer HTTPS, and avoid logging secrets or sensitive request bodies. For STDIO transport, confirm the WP-CLI user and site path before running tool calls against a real site.

Duplicate Check

Checked current content/mcp/, content/tools/, content/skills/, open pull requests, and repository-wide content for WordPress/mcp-adapter, wordpress/mcp-adapter, WordPress MCP Adapter, WordPress Abilities API MCP, WP-CLI MCP, and WordPress AI agents. The catalog includes a separate WordPress agent skills entry for agent guidance, but no dedicated MCP Adapter entry, exact source URL duplicate, target file, or open duplicate PR was found.