Rectus Content Access for MCP lets authenticated MCP clients list, read, create, and update WordPress content and upload images.
For a Japanese overview and setup guide, visit the Rectus Content Access for MCP introduction page.
The plugin provides:
Posts and pages are enabled by default. Custom post types must be enabled by an administrator before MCP clients can use them.
Rectus Content Access for MCP checks the authorized WordPress user’s native capabilities for every operation, including each post type’s create, edit, publish, and taxonomy permissions.
Saved content is filtered by the same capability WordPress itself uses, so an edit made through an MCP client is stored exactly as the block or classic editor would have stored it. Markup that the editors keep, such as JSON-LD structured data and schema.org microdata, survives the round trip instead of being silently rewritten.
OAuth access tokens, refresh tokens, authorization codes, and direct media upload tickets are stored only as SHA-256 hashes. Access tokens expire after one hour, refresh tokens are rotated automatically, and connections can be revoked from the settings screen. Uninstalling Rectus Content Access for MCP removes its settings and OAuth data.
The official WordPress MCP Adapter library is bundled with Rectus Content Access for MCP. A separate MCP Adapter plugin or Node.js process is not required on the WordPress server.
Rectus Content Access for MCP includes the following GPL-compatible Composer packages:
License files are included with each package under the vendor directory.