Title: Rectus Content Access for MCP
Author: Rectus Inc.
Published: <strong>24 julho, 2026</strong>
Last modified: 3 setembro, 2026

---

Pesquisar plugins

![](https://ps.w.org/rectus-content-access-for-mcp/assets/banner-772x250.png?rev
=3621986)

![](https://ps.w.org/rectus-content-access-for-mcp/assets/icon-256x256.png?rev=3621986)

# Rectus Content Access for MCP

 Por [Rectus Inc.](https://profiles.wordpress.org/rectuswp/)

[Baixar](https://downloads.wordpress.org/plugin/rectus-content-access-for-mcp.1.4.1.zip)

 * [Detalhes](https://br.wordpress.org/plugins/rectus-content-access-for-mcp/#description)
 * [Avaliações](https://br.wordpress.org/plugins/rectus-content-access-for-mcp/#reviews)
 *  [Instalação](https://br.wordpress.org/plugins/rectus-content-access-for-mcp/#installation)
 * [Desenvolvimento](https://br.wordpress.org/plugins/rectus-content-access-for-mcp/#developers)

 [Suporte](https://wordpress.org/support/plugin/rectus-content-access-for-mcp/)

## Descrição

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](https://www.rectus.co.jp/tool/rectuscontentaccessformcp.html).

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.
 * 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.
 * Media library listing, physical filename changes, and confirmation-protected 
   permanent attachment deletion.
 * A settings screen where administrators choose which post types MCP clients may
   access.
 * 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.
 * 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.

## Capturas de tela

[⌊Configure connection readiness, allowed post types, and MCP client setup commands.⌉⌊
Configure connection readiness, allowed post types, and MCP client setup commands
.⌉[

Configure connection readiness, allowed post types, and MCP client setup commands.

## Instalação

 1. Install and activate Rectus Content Access for MCP.
 2. Open Settings, Rectus Content Access for MCP.
 3. Select the post types that MCP clients may list, create, or update.
 4. Copy and run the setup command for your client.
 5. Follow the client-specific authentication instructions shown on the settings screen.

HTTPS is required for OAuth connections. The connection has the same effective permissions
as the WordPress user who approved it.

## Perguntas frequentes

### Does Rectus Content Access for MCP require an external service?

No service operated by the plugin author is required. MCP requests are handled by
WordPress through the bundled official MCP Adapter library. When an OAuth client
uses an HTTPS URL as its client ID, Rectus Content Access for MCP retrieves public
client metadata from that client-provided URL as described below.

### What data is sent when URL-based OAuth client metadata is retrieved?

During OAuth authorization, a connecting client may provide an HTTPS metadata URL
as its client ID. Rectus Content Access for MCP then sends a server-side GET request
to that exact URL with an `Accept: application/json` header. The response is limited
to 64 KB and valid metadata is cached for one hour. No WordPress content, passwords,
OAuth codes, or tokens are sent. The destination is selected and operated by the
connecting MCP client, not by the plugin author, so the destination operator’s terms
and privacy policy apply.

### Does the WordPress server need Node.js?

No. The server-side plugin runs in PHP. An MCP client may have its own local runtime
requirements, depending on the client.

### Does Rectus Content Access for MCP send my WordPress password to the MCP client?

No. The user signs in on the WordPress site and approves the connection in the browser.
The MCP client receives short-lived OAuth tokens instead of the WordPress password.

### How do I revoke a connection?

Open Settings, Rectus Content Access for MCP and revoke the connection in the OAuth
connections table. MCP clients may also clear or revoke their saved authorization.

### Can I connect an account that reads content but never changes it?

Yes. Authorize the connection as a user without editing rights, a subscriber by 
default. That account can list posts, read a post with its content and public custom
fields, read the terms assigned to it, and list the enabled post types. Every create,
update, edit, delete, media, menu, and template operation is refused, as is reading
a draft or a private post, because WordPress itself limits those to the users allowed
to see them. The media library cannot be listed either, since that needs the upload
capability.

On WordPress 7.1 or later the connection is offered only those four read abilities.
The rest are hidden from ability discovery rather than listed and refused on use.

### How are local images uploaded without Base64?

Codex and Claude Code should call the media upload ticket tool with the local image
filename, byte size, MIME type, and attachment metadata. The tool returns a plugin
REST endpoint and a short-lived, one-time token. The client then sends the image
bytes directly as multipart form data. The image does not enter the model context,
and no Application Password or second WordPress login is required.

The ticket is valid for five minutes, is bound to the authorized WordPress user 
and expected file metadata, and is stored only as a SHA-256 hash. Repeating a completed
request with the same ticket returns the existing attachment instead of creating
a duplicate.

MCP clients that cannot perform the direct HTTP upload may continue to use the Base64
media upload tool. Files already present in the WordPress uploads/mcp-inbox directory
may use the media import tool without transferring image bytes through MCP.

### How do I rename or delete media?

Use the media list tool to search the WordPress media library and obtain the exact
attachment ID, filename, and file-state SHA-256. To change the physical filename,
call media rename with those values, a new filename, and `confirm` set to true. 
The extension and upload directory stay unchanged. Local original files, generated
sizes, edit backups, and attachment metadata are renamed together.

To delete media, call the media delete tool with the selected ID, matching filename,
and `confirm` set to true. WordPress checks the authorized user’s delete permission
for the selected attachment.

Renaming changes the public media URL. Deletion is permanent and removes the attachment
and its generated files. Existing links to that media in post content are not rewritten,
so clients should show the selected ID and filename to the user before confirming
either operation.

### Can MCP manage Appearance > Menus?

Yes. Navigation menu abilities list and read classic menus, create and update menu
metadata, add and edit ordered hierarchical items, delete childless items or whole
menus with confirmation, and assign or clear registered theme locations. Mutations
require the SHA-256 returned by the latest menu read, and all operations require
the authorized user’s edit_theme_options capability.

### How are posts deleted?

Post delete moves an enabled post, page, or custom post type entry to the WordPress
trash. It requires the exact ID, post type, modified time from a prior read, and`
confirm` set to true. It never permanently deletes content and refuses the operation
on sites where the trash is disabled.

### How are post slugs found and changed?

Pass `slug` to post-list for an exact slug lookup. The separate `search` field uses
WordPress content search. Post-create accepts an optional slug and returns the actual
stored value.

To change a slug, first call post-get, then pass its current `slug` as `expected_slug`
and the new value as `slug` to post-update. A stale current value is rejected. A
value that WordPress would silently suffix, such as adding `-2` because another 
post already uses it, is also rejected with the suggested value in the error data.

WordPress does not keep a published post without a slug. Passing an empty slug to
post-update resets the manual value: published content regenerates the slug from
its current title, while a draft may remain empty until publication. To delete the
post itself and release its active slug, use post-delete. Its response reports the
slug before trashing and the stored trashed slug.

### Can MCP manage categories, tags, and custom taxonomy terms?

Yes. The term list tool searches existing terms and returns their IDs, names, slugs,
descriptions, parents, usage counts, and an editable-state SHA-256. Term create 
can add a category, tag, or custom taxonomy term, including an optional slug, description,
and parent for hierarchical taxonomies. Term update can change those fields after
matching the latest state checksum.

Term delete permanently removes the selected term and may remove or reassign existing
post relationships according to WordPress rules. It therefore requires the exact
ID, taxonomy, latest state checksum, and `confirm` set to true. WordPress-protected
default terms cannot be deleted. Every operation remains limited to taxonomies attached
to an enabled post type and to the authorized user’s native taxonomy capabilities.

### How is the MCP server name chosen?

Rectus Content Access for MCP derives the client configuration name from the site’s
domain and subdirectory path. For example, `rectus.co.jp` becomes `wordpress-rectus-
co-jp`, while `example.com/site-a` becomes `wordpress-example-com-site-a`. This 
prevents different WordPress sites from overwriting each other’s MCP client configuration.

### Why should I run the Codex login command only when needed?

Codex App and Codex CLI share MCP configuration. After the add command saves the
server, Codex App may open the authorization screen automatically. Approve that 
screen once. Run `codex mcp login` only when authorization does not start; running
both flows at the same time can create a duplicate OAuth connection.

### How do I authenticate Claude Code?

Run the displayed `claude mcp add` command, then run `claude mcp login`. The login
command opens the browser authorization screen directly, so there is no need to 
start Claude Code and run `/mcp` manually.

### Why do new MCP clients fail to connect while existing clients keep working?

The OAuth discovery URLs under `/.well-known/` are served through WordPress. Server
rules that handle `/.well-known/` before WordPress break new authorizations while
issued tokens keep refreshing. Rectus Content Access for MCP reports this state 
in Site Health and in the Discovery metadata row on the settings screen.

### Does OAuth support random localhost callback ports?

Yes. Native MCP clients may select an available loopback port when authorization
starts. Rectus Content Access for MCP follows RFC 8252 by allowing the port to differ
for `localhost`, `127.0.0.1`, and `::1` redirect URIs while still requiring the 
scheme, host, path, and query to match. All other redirect URIs require an exact
match.

### Is post content sanitized before it is saved?

Yes, by the same rule WordPress applies to the block and classic editors. Content
from a user who holds the unfiltered_html capability, which on a single site means
an administrator, is stored as written and left to the content_save_pre filters 
that wp_insert_post() applies, so nothing is removed that the editors would have
kept. Content from every other user is filtered with wp_kses_post(), which strips
script elements, event handler attributes, and anything else outside the allowed
list. Rectus Content Access for MCP additionally allows schema.org microdata attributes
there, because WordPress core omits them and structured data lives in the post content.

An MCP connection therefore never grants more reach than the approving WordPress
user already had in the editor.

### Which custom post types are available?

Rectus Content Access for MCP lists non-built-in post types that have a WordPress
editing screen and support a title, editor, or excerpt. Administrators must explicitly
enable each post type.

### Are ACF and other custom fields supported?

Yes. The post-get, post-create, and post-update tools expose public custom fields
through the custom_fields object. Values may be strings, numbers, booleans, arrays,
or objects; pass null during create or update to delete a field.

When post-get returns a stored custom field, custom_field_definitions returns its
label, type, description, required setting, available choices, and whether the definition
came from registered WordPress meta, ACF, or unregistered post meta. Fields without
a stored value are omitted.

For safety, WordPress-protected meta keys, including keys beginning with an underscore,
are not exposed or writable. Existing public ACF value rows are therefore available,
but hidden ACF field-reference metadata is not created or changed. Plugin-specific
validation, new field-reference setup, or side effects that only run through a plugin’s
own form or API are not emulated.

### Can MCP manage fixed-page templates?

Yes. The page-template-list, page-template-get, page-template-create, page-template-
update, and page-template-delete tools manage only root-level `page-*.php` files
with a `Template Name` header in the active theme. They cannot read or modify arbitrary
theme PHP files such as functions.php.

Only users with WordPress theme-editing permission can use these tools. Updates 
and deletions require the SHA-256 returned by a prior read or list, so a changed
template is never overwritten or deleted silently. Deletion also requires `confirm:
true` and is refused while the template remains assigned to a non-trashed page.

The post-get result includes `page_template`. Pass a managed template filename to
the page_template field of post-create or post-update to assign it to a page, or
pass `default` to clear the assignment.

### Which languages are supported?

English source strings are included. After publication on WordPress.org, community
translations are provided through translate.wordpress.org and delivered as WordPress
language packs.

## Avaliações

Não há avaliações para este plugin.

## Colaboradores e desenvolvedores

“Rectus Content Access for MCP” é um programa de código aberto. As seguintes pessoas
contribuíram para este plugin.

Colaboradores

 *   [ Rectus Inc. ](https://profiles.wordpress.org/rectuswp/)

Rectus Content Access for MCP” foi traduzido para 1 localidade. Agradecemos aos 
[tradutores](https://translate.wordpress.org/projects/wp-plugins/rectus-content-access-for-mcp/contributors)
por suas contribuições.

[Traduzir o “Rectus Content Access for MCP” para seu idioma.](https://translate.wordpress.org/projects/wp-plugins/rectus-content-access-for-mcp)

### Interessado no desenvolvimento?

[Navegue pelo código](https://plugins.trac.wordpress.org/browser/rectus-content-access-for-mcp/),
consulte o [repositório SVN](https://plugins.svn.wordpress.org/rectus-content-access-for-mcp/)
ou assine o [registro de desenvolvimento](https://plugins.trac.wordpress.org/log/rectus-content-access-for-mcp/)
por [RSS](https://plugins.trac.wordpress.org/log/rectus-content-access-for-mcp/?limit=100&mode=stop_on_copy&format=rss).

## Registro de alterações

#### 1.4.1

 * Fixed Claude OAuth connections being rejected when its client metadata also advertises
   the JWT bearer grant. Only authorization_code and refresh_token are enabled by
   the plugin.
 * Accepted additional response types in client metadata while enabling only code
   responses. Malformed metadata and clients without authorization_code or code 
   support remain rejected.

#### 1.4.0

 * Checked the read abilities against the WordPress read capability instead of the
   edit capability, so an account that may read but not edit can list and read content
   through MCP.
 * Returned public custom fields to any user allowed to read the post, matching 
   what WordPress exposes through the REST API and the_meta().
 * Required only the read capability to list taxonomy terms, which previously asked
   for the capability to assign them.
 * Listed a post status only when the authorized user may see posts in it, so post-
   list no longer reports a total it will not return and no longer leaves short 
   pages.
 * Reported that a status cannot be listed instead of returning an empty list for
   it.
 * Hid the abilities the authorized user could not use whatever the input from ability
   discovery, so an MCP client is offered what it may call instead of learning the
   difference one refusal at a time. WordPress 7.1 or later is needed for this; 
   on 6.9 and 7.0 every ability stays listed and each call is refused as before.
 * Described post-list and post-get as reading what the user may read rather than
   what the user may edit.

#### 1.3.0

 * Added searchable category, tag, and custom taxonomy term creation, update, and
   permanent deletion abilities.
 * Added editable-state SHA-256 values to term-list and required a matching value
   for term updates and deletions.
 * Required explicit confirmation for permanent term deletion and verified that 
   WordPress removed the selected term before reporting success.
 * Added parent-term validation for hierarchical taxonomies, including missing-parent
   and ancestry-cycle protection.

#### 1.2.0

 * Added exact post slug lookup to post-list.
 * Added conflict-checked post slug updates to post-update. The current slug returned
   by post-get must be supplied, so a changed slug is never overwritten silently.
 * Made post-create and post-update return the stored slug, and reject a requested
   slug that WordPress would otherwise silently suffix for a conflict.
 * Defined an empty slug update as resetting a manual slug: published content regenerates
   it from the current title, while drafts may remain empty until publication.
 * Added the slug before and after post-delete moves an entry to the WordPress trash.

#### 1.1.1

 * Hardened refresh-token retry handling so incomplete or out-of-bounds replay data
   cannot create a parallel token family.
 * Made normal refresh-token rotation atomic and kept replay responses bounded for
   compatible retrying clients.
 * Replayed the rotation that already happened when a client presents a refresh 
   token another of its processes rotated away, instead of revoking the connection
   or issuing a parallel credential.
 * Measured how far behind such a token is in rotations rather than in elapsed time,
   so that the allowance follows the client’s own refresh interval instead of a 
   fixed clock.
 * Encrypted rotation replay material with a key derived from the presented refresh
   token so that it cannot be recovered from the database alone.
 * Fixed a revoked connection being resurrected by a refresh token presented within
   a minute of the revocation.
 * Restored the presented refresh token when the pair it was exchanged for could
   not be issued, instead of leaving the connection unusable.

#### 1.1.0

 * Added confirmation-protected post trashing with post type and modified-time conflict
   checks.
 * Added classic navigation menu, item hierarchy and order, and theme-location management
   with SHA-256 conflict protection.
 * Added physical media filename changes for local uploads, including generated 
   image sizes and edit backups, with rollback and verification.
 * Added file-state SHA-256 values to media listing and stricter schemas for media
   rename and deletion.

#### 1.0.1

 * Added an optional date to post-create and post-update, read in the site time 
   zone, so an entry can carry a past date instead of the time of the request.
 * Scheduled the post when that date is in the future, reporting the resulting future
   status instead of the requested publish.
 * Verified the stored date after saving, like the other post fields.

#### 1.0.0

 * Reported the plugin and site identity to MCP clients instead of the bundled adapter’s
   default server name, version, and instructions.
 * Added the server title, description, website URL, and icons defined by MCP 2025-
   11-25, sent only to clients that negotiated a protocol version which defines 
   them.
 * Added openWorldHint to every ability annotation, stating that operations stay
   within this WordPress site.
 * Fixed the OAuth discovery metadata check reporting a failure with the message“
   1” on sites without a persistent object cache, which made the settings screen
   and Site Health report broken discovery while authorization worked normally.
 * Brought the plugin source to a clean WordPress Coding Standards run.
 * Removed unused parameters from the internal taxonomy helpers.

#### 0.6.0

 * Added post-edit, which replaces exact strings inside a stored post title, excerpt,
   or content instead of resending the whole field.
 * Added field_sha256 checksums to post-get and required the selected checksum as
   expected_field_sha256 when calling post-edit.
 * Required each edit to match exactly once unless replace_all is set, and rejected
   the whole request without saving when an edit does not match or is ambiguous.
 * Re-read the database immediately before saving, rejected stale field checksums,
   refreshed the post cache, and verified the stored value before reporting success.
 * Kept WordPress save filters active and returned an explicit re-read error when
   a filter stored a different value.

#### 0.5.5

 * Added permission-checked fixed-page template listing, reading, creation, update,
   and deletion for active-theme root-level page-*.php files with Template Name 
   headers.
 * Added SHA-256 concurrency checks, explicit deletion confirmation, and an assigned-
   page safeguard for template deletion.
 * Added fixed-page template reporting and assignment through post-get, post-create,
   and post-update.

#### 0.5.4

 * Made post updates determine the post type from the post ID; an optional post_type
   input now acts only as a checked assertion.
 * Verified submitted post fields directly against the database and refreshed the
   post cache before reporting success.
 * Added permission-checked reading, writing, and deletion of public custom fields
   for posts, pages, and enabled custom post types.
 * Added per-field definitions to post reads for stored custom fields, including
   registered WordPress meta and ACF metadata when available.
 * Rejected protected custom field keys and returned explicit errors for mismatched
   post types, empty updates, or values that were not preserved.

#### 0.5.3

 * Fixed MCP sessions being rejected as invalid on sites with a persistent object
   cache, which stopped Claude Code and other clients from loading the tool list
   right after connecting.

#### 0.5.2

 * Verified post content after create and update operations so silently changed 
   content is no longer reported as a successful save.
 * Preserved backslashes and escaped JSON values when creating posts, pages, and
   custom post type entries.
 * Allowed a short refresh-token rotation overlap for concurrent processes using
   the same MCP client credentials without revoking the active connection family.
 * Stored MCP HTTP sessions independently so Codex, Claude Code, and other clients
   can connect concurrently as the same WordPress user without overwriting one another.
 * Added media listing and permission-checked permanent deletion with exact ID, 
   filename, and confirmation safeguards.

#### 0.5.1

 * Stopped running post content through wp_kses_post() for users who hold unfiltered_html,
   so an edit made through MCP keeps the markup that the block and classic editors
   would have stored.
 * Fixed JSON-LD structured data being dropped, and its raw JSON left behind as 
   visible body text, when those users saved content through the create and update
   tools.

#### 0.5.0

 * Added a preferred direct multipart image upload flow for Codex and Claude Code.
 * Added short-lived, one-time media upload tickets exposed through an MCP ability.
 * Added a plugin REST endpoint that validates the ticket, WordPress user permissions,
   filename, byte size, MIME type, and image contents.
 * Added idempotent retry behavior that returns an existing attachment instead of
   creating a duplicate.
 * Kept Base64 media upload and server-side inbox import as compatible fallbacks.
 * Renamed PHP symbols, internal hooks, settings, OAuth storage, and credential 
   prefixes to match Rectus Content Access for MCP.

#### 0.4.1

 * Preserved schema.org microdata attributes in post content saved through the create
   and update tools.

#### 0.4.0

 * Renamed the plugin to Rectus Content Access for MCP and updated its pre-approval
   slug.
 * Internationalized MCP ability names, descriptions, and error messages.
 * Standardized English source strings for WordPress.org translation workflows.
 * Removed bundled translation files in favor of WordPress.org language packs.
 * Generated site-specific MCP client server names from the WordPress domain and
   path.
 * Documented URL-based OAuth client metadata retrieval and the data it sends.
 * Separated Codex server setup from the fallback login command to prevent duplicate
   OAuth authorization flows.
 * Updated Claude Code setup to open browser authorization directly via `claude 
   mcp login`.
 * Added a Site Health test and a settings screen check for OAuth discovery metadata
   reachability.
 * Added a post read tool that returns the stored content and terms for AI editing
   workflows.
 * Added a taxonomy term listing tool so clients assign existing terms instead of
   creating variants.
 * Added featured image support to the post create, update, and read tools.
 * Added taxonomy term filtering to the post list tool.
 * Allowed RFC 8252 ephemeral ports for native client loopback OAuth redirects.

#### 0.3.0

 * Added read-only paginated listing for posts, pages, and enabled custom post types.
 * Added read-only discovery of enabled post types, supported fields, and taxonomies.

#### 0.2.0

 * Added MCP OAuth 2.1 authorization with PKCE, resource indicators, and discovery
   metadata.
 * Added automatic access token refresh, refresh token rotation, and connection 
   revocation.
 * Replaced Application Password setup with one-copy Codex and Claude Code commands.
 * Added an OAuth connection management table to the settings screen.

#### 0.1.0

 * Initial release.
 * Added configurable post, page, and custom post type access.
 * Added standard content, taxonomy, and media abilities.
 * Bundled the official WordPress MCP Adapter with conflict-safe autoloading.
 * Added initial Application Password and MCP client setup tools.

## Meta

 *  Versão **1.4.1**
 *  Última atualização **1 dia atrás**
 *  Instalações ativas **Menos de 10**
 *  Versão do WordPress ** 6.9 ou superior **
 *  Testado até **7.1**
 *  Versão do PHP ** 7.4 ou superior **
 *  Idiomas
 * [English (US)](https://wordpress.org/plugins/rectus-content-access-for-mcp/) 
   e [Japanese](https://ja.wordpress.org/plugins/rectus-content-access-for-mcp/).
 *  [Traduzir para seu idioma](https://translate.wordpress.org/projects/wp-plugins/rectus-content-access-for-mcp)
 * Tags
 * [AI](https://br.wordpress.org/plugins/tags/ai/)[content](https://br.wordpress.org/plugins/tags/content/)
   [custom post types](https://br.wordpress.org/plugins/tags/custom-post-types/)
   [mcp](https://br.wordpress.org/plugins/tags/mcp/)[media](https://br.wordpress.org/plugins/tags/media/)
 *  [Visualização avançada](https://br.wordpress.org/plugins/rectus-content-access-for-mcp/advanced/)

## Classificações

Ainda não foi enviada nenhuma avaliação.

[Sua avaliação](https://wordpress.org/support/plugin/rectus-content-access-for-mcp/reviews/#new-post)

[Ver todas avaliações](https://wordpress.org/support/plugin/rectus-content-access-for-mcp/reviews/)

## Colaboradores

 *   [ Rectus Inc. ](https://profiles.wordpress.org/rectuswp/)

## Suporte

Tem algo a dizer? Precisa de ajuda?

 [Ver fórum de suporte](https://wordpress.org/support/plugin/rectus-content-access-for-mcp/)