內容簡介
Rectus Content Access for MCP 外掛讓經過身份驗證的 MCP 客戶端能夠管理 WordPress 內容、經典導航菜單及媒體檔案，提供高效的內容編輯和管理功能，提升使用者體驗。
【主要功能】
• 列出、創建及更新文章和頁面
• 精確的字串編輯及衝突檢測
• 確認保護的文章移動至垃圾桶
• 預覽未發佈文章的連結
• 支援批量編輯最多 50 篇文章
• 管理經典導航菜單及媒體庫
外掛標籤
開發者團隊
② 後台搜尋「Rectus Content Access for MCP」→ 直接安裝（推薦）
原文外掛簡介
Rectus Content Access for MCP lets authenticated MCP clients manage WordPress content, classic navigation menus, and media files.
For a Japanese overview and setup guide, visit the Rectus Content Access for MCP introduction page.
The plugin provides:
Listing, creation, and updating of posts, pages, and selected custom post types, including exact slug lookup and conflict-checked slug changes.
Targeted string edits with full-field SHA-256 conflict detection, so small corrections do not require resending an entire title, excerpt, or content field.
Confirmation-protected movement of posts to the WordPress trash with post type and modified-time conflict checks.
Listing, reading, and conflict-checked restoring of post revisions, with the text a post had before each change through MCP kept as a revision.
Preview links for unpublished posts in post lists, reads, and write results.
Exact text search across the posts the user can edit, and batch edits and updates of up to 50 posts in one call, so an old URL or a category can be changed across many posts after the list has been checked.
Page order on creation and update, and duplication of a post into a new draft.
An optional publication date on creation and update, so back-dated entries such as a release history can be filed under the day they happened.
Reading of a single post’s stored title, content, excerpt, and assigned terms, available to any account WordPress allows to read the post.
Listing of enabled post types with labels, supported fields, and taxonomies.
Searching, creation, conflict-checked updating, and confirmation-protected permanent deletion of categories, tags, and custom taxonomy terms.
Paginated content lists with status, search, taxonomy term, and ordering filters.
Featured image assignment from uploaded media when creating or updating posts.
Classic navigation menu, menu item, hierarchy, order, and theme-location management with checksum conflict protection, including batch edits of up to 100 menu items in one call.
Media library listing, physical filename changes, and confirmation-protected permanent attachment deletion.
Conflict-checked updates of the title, alternative text, caption, and description of up to 100 media items in one call.
A settings screen where administrators choose which post types MCP clients may access, and which protected custom fields, such as SEO plugin fields, MCP may read and write.
An activity log of successful changes and partially completed batches under Tools > MCP Activity.
Site information, including the front page, permalink structure, and whether the active theme is a block theme.
Listing of classic widget areas and conflict-checked changes to a widget’s settings.
Comment listing without email or IP addresses, and approving, holding, spamming, or trashing up to 100 comments in one call.
Support for standard content fields, public custom fields, and taxonomies assigned to the selected post type.
Listing, reading, creation, update, and confirmation-protected deletion of managed fixed-page templates in the active theme.
Reading, replacing, partly editing, and clearing Additional CSS with checksum conflict protection, and restoring it from its revisions.
Fixed-page template assignment through post creation and update operations.
Direct multipart image uploads for Codex and Claude Code using short-lived, one-time tickets.
Base64-encoded image uploads as a fallback for MCP clients that cannot perform direct uploads.
Browser-based OAuth 2.1 authorization with PKCE and automatic token refresh.
Copy-ready setup commands for Codex and Claude Code.
Site-specific MCP server names derived from the WordPress domain and path to prevent client configuration collisions.
Support for MCP protocol revisions 2025-11-25, 2025-06-18, and 2024-11-05, negotiated with the connecting client.
Server identity reported on connection, including the site title, description, website URL, and icons, so a client registered against several sites can tell them apart.
Translation-ready administration, OAuth, MCP ability, and error strings.
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.
Reading follows the read capability rather than the edit capability. An account that may read but not edit, a subscriber by default, can therefore list and read published content, its public custom fields, and the terms assigned to it, while every write operation stays refused. Drafts and private posts remain limited to the users WordPress already allows to see them.
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.
For targeted corrections, post-get returns SHA-256 checksums of the exact stored title, content, and excerpt. Post-edit requires the selected field checksum, re-reads the database immediately before saving, and returns a conflict without saving if the field changed. WordPress save filters still run normally, and the stored value is verified before success is reported.
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.
A client that shares one credential between several processes can present a refresh token that another process already rotated away. For supported retry behavior, Rectus Content Access for MCP can replay the already-issued token pair instead of issuing a parallel credential, so the client converges on the single active credential. Replay material is encrypted with a key derived from the presented refresh token itself, so it is never recoverable from the database alone. Replay requests are bounded by the rotation history and a time safety limit; requests outside those bounds are treated as reuse of an invalid credential and revoke the connection family.
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.
Third-Party Libraries
Rectus Content Access for MCP includes the following GPL-compatible Composer packages:
WordPress MCP Adapter, copyright WordPress.org Contributors, GPL-2.0-or-later.
WordPress PHP MCP Schema, copyright WordPress.org Contributors, GPL-2.0-or-later.
Jetpack Autoloader, copyright Automattic, GPL-2.0-or-later.
License files are included with each package under the vendor directory.
