Automattic WordPress 远程 MCP

WordPress 远程集成的工程痛点

• 企业级 WordPress 站点与 MCP 客户端集成时，常面临认证机制碎片化（OAuth/JWT/应用密码混用）、远程操作缺乏标准化接口、动态内容同步延迟等问题。
• 传统方案需要手动处理令牌刷新、API 版本适配，导致维护成本高且易出错。

远程 MCP 桥接的工作逻辑

• 核心能力：通过 @automattic/mcp-wordpress-remote 包提供统一接口，支持三种认证方式：

- OAuth 2.0 标准流程（适合第三方应用）
- JWT 签名验证（适配 WordPress REST API 认证体系）
- 应用密码（Application Passwords）快速接入

• 关键步骤：

1. 配置 WP_API_URL、WP_API_USERNAME、WP_API_PASSWORD 环境变量，指向目标站点 REST API 端点
2. 在 MCP 客户端（如 Claude Desktop）的配置文件中添加桥接服务，指定 Node.js 22+ 运行环境
3. 通过标准化接口执行内容 CRUD 操作，例如 POST /wp-json/wp/v2/posts 创建文章，GET /wp-json/wp/v2/sites 获取站点信息

适用场景与技术边界

• 推荐场景：需要通过 MCP 客户端远程管理多 WordPress 站点的内容（文章/页面/媒体）、主题设置、插件状态，且要求实时同步的场景。
• 限制条件：

- 必须运行在 Node.js 22+ 环境（依赖 fetch API 支持）
- 依赖 WordPress 站点启用 REST API 并正确配置认证信息
- 适合维护中的远程 MCP 桥接，不推荐用于本地开发环境或低版本 WordPress 站点

Engineering Pain Points in WordPress Remote Integration

• Enterprise WordPress sites often struggle with fragmented authentication mechanisms (OAuth/JWT/application passwords), lack of standardized remote operation interfaces, and delayed dynamic content synchronization when integrating with MCP clients.
• Traditional solutions require manual token refresh and API version adaptation, leading to high maintenance costs and increased error risks.

Working Logic of Remote MCP Bridging

• Core Capabilities: The @automattic/mcp-wordpress-remote package provides a unified interface supporting three authentication methods:

- OAuth 2.0 standard flow (suitable for third-party applications)
- JWT signature verification (adapted to WordPress REST API authentication)
- Application Passwords for quick access

• Key Steps:

1. Configure environment variables: WP_API_URL, WP_API_USERNAME, WP_API_PASSWORD pointing to the target site's REST API endpoint
2. Add the bridge service in MCP client configuration files (e.g., Claude Desktop's claude_desktop_config.json) with Node.js 22+ environment specified
3. Execute content CRUD operations via standardized interfaces, such as POST /wp-json/wp/v2/posts to create articles, GET /wp-json/wp/v2/sites to retrieve site information

Applicable Scenarios & Technical Boundaries

• Recommended Scenarios: Managing content (posts/pages/media), theme settings, and plugin status across multiple WordPress sites via MCP clients with real-time synchronization requirements.
• Constraints:

- Requires Node.js 22+ environment (dependent on fetch API support)
- Depends on WordPress sites with REST API enabled and properly configured authentication information
- Suitable for maintained remote MCP bridging, not recommended for local development environments or lower-version WordPress sites