WordPress MCP

WordPress MCP registers WordPress abilities and exposes them through the MCP adapter endpoint at:

/wp-json/mcp/wp-forge

WordPress 6.9+ provides the core Abilities API. The MCP transport is provided by the wordpress/mcp-adapter Composer dependency.

See docs/architecture.md for the ability registry, registration trait, domain trait, schema, validation, and permission helper layout.

Requirements

• WordPress 6.9 or later.
• PHP 8.2 or later.
• Composer dependencies installed, including wordpress/mcp-adapter.

Available Tools

Content Management

Content

wp-forge-post-type-list returns each post type's slug, label, hierarchical status, public status, supported features, registered taxonomies, and REST base. The content tools use the same runtime metadata to validate conditional fields: parent_id is accepted only for hierarchical post types, and taxonomies may only include taxonomies registered to the selected post_type.

Taxonomies

Media

Site Management

Users

Settings

Site Info

Plugins

Options

Comments

Site Health

Error Logs

WP-CLI

WP-CLI execution is disabled by default. To enable it, define WP_FORGE_MCP_ENABLE_WP_CLI as true in wp-config.php, or return true from the wp_forge_mcp_enable_wp_cli filter. If wp is not on the web server user's PATH, define WP_FORGE_MCP_WP_CLI_PATH with the full path to the WP-CLI executable.

Global Styles

Themes

Advanced REST API CRUD

REST method schemas are derived from the registered WordPress REST routes at discovery time, so methods such as PUT appear when the underlying API supports them.

Copy-Paste MCP Configuration

Replace https://example.com with your site URL. Create a WordPress Application Password from your user profile, then replace the username and password placeholders below.

{
  "mcpServers": {
    "wordpress": {
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote"
      ],
      "env": {
        "WP_API_URL": "https://example.com/wp-json/mcp/wp-forge",
        "WP_API_USERNAME": "YOUR_WORDPRESS_USERNAME",
        "WP_API_PASSWORD": "YOUR_APPLICATION_PASSWORD",
        "OAUTH_ENABLED": "false"
      }
    }
  }
}

The same configuration is available in WordPress under Settings > WordPress MCP after activating the plugin.

Activity Log

An optional MCP activity log is available under Settings > WordPress MCP. When enabled, it records each tool call's tool name, user, status, duration, IP address, user agent, and session ID. Tool arguments and responses are not logged.

Development

Install Composer dependencies to generate the PSR-4 autoloader:

composer install

Run the test suite:

composer test

Playground Testing

Start a local WordPress Playground site with this plugin mounted and activated:

npm install
npm run playground:start

Test the MCP endpoint:

npm run test:playground

By default, the endpoint test uses http://127.0.0.1:9400/wp-json/mcp/wp-forge and authenticates with Playground's local auto-login flow. For remote sites, set WP_API_URL, WP_API_USERNAME, and WP_API_PASSWORD to use a WordPress Application Password.