Packagist · #1923 most downloaded on Packagist

wordpress/mcp-adapter

v0.7.0568K downloads/moWordPress/mcp-adapter ↗New releases in your daily digest, changelog included.

Adapter for Abilities API, letting WordPress abilities to be used as MCP tools, resources or prompts

Last release 6 days ago
02 Oct 2026
Ships fairly regularly
a new release about every 3 months
Nearly every release is documented
notes for 8 of 8 stable releases
Nothing withdrawn
no release was ever pulled
1 years old
8 releases · first in 2025

Release timeline

8 releases since 2025

20252026

Releases

v0.7.02 Oct 2026Breaking
This release has breaking changes for code that extends the adapter:
MCP Adapter 0.7.0 adds support for MCP 2026-07-28 and moves protocol output to exact-revision schemas. It is also the first release published to the WordPress.org plugin directory.

Before you upgrade

This release has breaking changes for code that extends the adapter:

The generated DTO classes, the McpToolValidator, McpResourceValidator, and McpPromptValidator classes, and the mcp_adapter_validation_enabled filter have been removed.

Custom transports must delegate to HttpRequestHandler or McpWireOrchestrator.

Components that are invalid in every supported revision are now rejected instead of silently repaired.

Using MCP Adapter as a bundled Composer library is deprecated. Install the plugin instead.

Read the v0.7.0 migration guide before you upgrade.

Highlights

MCP 2026-07-28: sessionless server/discover, per-request protocol metadata, and the Mcp-Method, Mcp-Name, and Mcp-Param-* headers over HTTP.

Clients that request 2025-06-18 or 2024-11-05 still connect, and are served through the 2025-11-25 schema.

Direct callable tools can request elicitation input under 2026-07-28 with McpInputRequired.

Default abilities register even when another plugin initializes the Abilities API first.

See CHANGELOG.md for the full list of changes.

What's Changed

docs: rebuild readme.txt for the WordPress.org listing by @abhi3315 in #285

docs: change recommendation to be installed as a canonical plugin by @stormrockwell in #289

docs: migrate deprecation information to docs/README.md by @steviepee in #291

ci: implement Playground blueprint.json and PR Previews by @justlevine in #304

ci: bump dev-deps and Tested up to header by @justlevine in #302

feat: deprecate usage of MCP Adapter as bundled dependency by @matiasbenedetto in #288

tests: run tests against PHP 8.5 by @justlevine in #303

dev!: Mark WP\MCP\Cli classes as final and cleanup internals by @justlevine in #306

Fix wp-env builds for PHP 7.4 and 8.0 after Debian bullseye end of life by @galatanovidiu in #322

ci: update Playground PR preview workflows to v4 by @obenland in #334

Support exact MCP 2025-11-25 and 2026-07-28 revisions by @galatanovidiu in #310

Let the schema reject malformed component data instead of repairing it by @galatanovidiu in #319

Support elicitation input requests on direct tool calls by @galatanovidiu in #316

Register default abilities before the Abilities API initializes by @galatanovidiu in #339

Stop MCP Adapter from reporting its own classes as another loaded version by @galatanovidiu in #341

Prepare the 0.7.0 release by @galatanovidiu in #342

chore: address PRT feedback by @justlevine in #346

ci: add WORG deployment step to release.yml by @justlevine in #347

Add wp.org banner & icon assets by @saarnilauri in #353

Add SVG source for the wp.org banner by @saarnilauri in #358

docs: replace refs to AI Plugin with MCP Adapter by @justlevine in #360

Revert "Fix wp-env builds for PHP 7.4 and 8.0 after Debian bullseye end of life" by @justlevine in #344

dev!: bump minimum node to v24.15 by @justlevine in #354

Fix the 0.7.0 release ZIP fatal error and verify the ZIP before publishing by @galatanovidiu in #362

Dependency updates from Dependabot are not listed. See the full changelog link below.

New Contributors

@abhi3315 made their first contribution in #285

@steviepee made their first contribution in #291

@matiasbenedetto made their first contribution in #288

@obenland made their first contribution in #334

@saarnilauri made their first contribution in #353

Props

Thank you to everyone who wrote, reviewed, or discussed the changes in this release: @justlevine, @jeffpaul, @gziolo, @andreilupu, @abhi3315, @matiasbenedetto, @dugyen, @webmyc, @dkotter, @stormrockwell, @saarnilauri, @georgestephanis, @steviepee, @obenland.

Full Changelog: v0.6.1...v0.7.0

Additional notes

Breaking Changes

Schema-backed MCP revisions are exactly 2025-11-25 and 2026-07-28. 2025-06-18 and 2024-11-05 no longer have their own DTOs; they are negotiated as legacy identifiers and served through the 2025-11-25 schema (see Added). McpVersionNegotiator::SUPPORTED_PROTOCOL_VERSIONS now lists only the schema-backed revisions; legacy identifiers moved to McpVersionNegotiator::LEGACY_PROTOCOL_VERSIONS.
Protocol-facing server getters get_tools(), get_resources(), get_prompts(), and get_prompt() require a selected Schema. There is no implicit default revision.
The generated DTO classes, get_protocol_dto(), and the alternate array serializers have been replaced by exact-revision schema records from wordpress/php-mcp-schema. See the dual-revision migration guide.
McpToolValidator, McpResourceValidator, McpPromptValidator, McpErrorFactory::validate_jsonrpc_message(), McpServer::is_mcp_validation_enabled(), and the mcp_adapter_validation_enabled filter have been removed. Wire validation always runs through the selected schema.
RequestRouter::route_request(), method handlers, McpErrorFactory, ContentBlockHelper, and McpPromptBuilderInterface::build() now exchange schema records and revision-neutral arrays instead of DTOs. JsonRpcResponseBuilder has been removed. Custom transports must delegate to HttpRequestHandler or McpWireOrchestrator.
McpTool::fromArray(), McpResource::fromArray(), and McpPrompt::fromArray() return WP_Error only for structural problems (missing name, URI, or handler; invalid resource URI). Schema and annotation problems no longer fail construction; they are reported per revision through is_available_for() and get_projection_error() and logged as warnings at registration.
The non-canonical tools/list/all method and ToolsHandler::list_all_tools() have been removed.
JSON-RPC batch requests are rejected before dispatch.
wp mcp-adapter list adds per-revision tool, resource, and prompt columns.
WP\MCP\Cli classes are final and can no longer be extended (#306).
Invalid protocol fields are no longer silently dropped or repaired. Components invalid in every supported schema revision are rejected. Handler values reach final schema projection. In 2026 responses, result _meta is validated before server identification is added, so malformed metadata is rejected and valid object fields are preserved. This reverses the 0.6.0 omission of malformed _meta. See the validation migration notes.
Removed validation and content helpers and the resource/prompt converter make() and getter layers are listed in the migration guide.
Non-array Ability meta.mcp now returns mcp_ability_invalid_meta. Removed errors: mcp_resource_missing_name, mcp_prompt_invalid_argument, and mcp_prompt_argument_missing_name. Non-array prompt arguments return mcp_prompt_invalid_arguments; resource-name filters reject non-strings only.

Added

Legacy MCP identifiers 2025-06-18 and 2024-11-05 negotiate through initialize and are echoed back verbatim while the 2025-11-25 schema serves the session. Every server-emitted difference between those revisions and 2025-11-25 is an optional additive field, so the projection is unchanged. MCP-Protocol-Version must match the negotiated identifier when sent, and may be omitted only for sessions negotiated under 2024-11-05, which predates the header. 2025-03-26 stays non-negotiable because it requires servers to receive JSON-RPC batches; a proposal receives 2025-11-25 as before. server/discover and the unsupported-version error list the same two schema-backed revisions.
McpRequestContext::protocol_version() returns the negotiated identifier; revision() continues to return the schema revision.
MCP 2026-07-28 support: the sessionless server/discover lifecycle, per-request protocol metadata in the request body, and the MCP-Protocol-Version, Mcp-Method, Mcp-Name, and Mcp-Param-* headers over HTTP. STDIO accepts either revision per line.
McpRequestContext, an immutable per-request context carrying the selected schema, transport, and session data.
McpWireOrchestrator and JsonRpcRequestDecoder, one decode, validate, dispatch, and encode boundary shared by the HTTP and STDIO transports.
McpTool, McpResource, and McpPrompt expose get_protocol_record( Schema $schema ) and is_available_for(). A component is omitted from a revision whose schema cannot represent it.
The mcp_adapter_tools_list, mcp_adapter_resources_list, mcp_adapter_prompts_list, and mcp_adapter_initialize_response filters receive the selected schema as a third argument.
Raw-wire, architecture, and projection test coverage for both revisions.
Components rejected by every supported schema revision raise _doing_it_wrong with schema error paths, in addition to error-handler logs.
Direct callable tools can return McpInputRequired under MCP 2026-07-28 to request elicitation input, and receive the client's answers through McpToolCallContext on retry (#316).

Changed

Request observability status and duration include final response projection, and server/discover emits a completion event. Invalid handler results return -32603, Internal error: The server produced an invalid result., with one failed request event and a correlated diagnostic through the configured error handler. See the observability migration notes.
Resource abilities support core's top-level meta.annotations without a deprecation notice. meta.mcp.annotations overrides it, and an empty array suppresses annotations instead of falling back.
Ability labels and descriptions preserve whitespace, and tool title is always emitted from the label. Resource names may be empty; absent names use the URI.
Resource URIs are no longer trimmed or limited to 2048 bytes; bare schemes such as wordpress: are accepted. Invalid lastModified timestamps reject resources on both registration paths.
Prompt results preserve supplied descriptions, metadata, message keys, and empty message lists. Malformed recognized shapes reach schema validation; JSON fallback encoding failures return execution errors.
Direct tool factories default inputSchema only when absent. Prompt fallback arguments include boolean property schemas and preserve supplied titles and descriptions.
Usage of MCP Adapter as a bundled library has been deprecated in favor of using the canonical MCP Adapter plugin. See the v0.7.0 migration guide for instructions on how to migrate away from a bundled copy of MCP Adapter.
initialize, notifications/initialized, and ping are served only for 2025-11-25; server/discover only for 2026-07-28. The 2025 HTTP session lifecycle is unchanged.
Adapter-owned 2026-07-28 output omits Tool.execution, adds resultType: "complete" to completed results, and adds ttlMs: 0 and cacheScope: "private" to discovery, list, and resource-read results.
Missing tools and prompts return Invalid Params (-32602) in both revisions. Missing resources return -32002 in 2025-11-25 and -32602 in 2026-07-28. An unsupported per-request version returns -32022.
Session validation errors carry the JSON-RPC request ID of the failing request instead of null.
tools/call and resources/read look up the tool name and resource URI exactly as sent. Surrounding whitespace is no longer trimmed, so a padded name cannot bypass the 2026-07-28 Mcp-Param-* header check.
resources/read forwards only the protocol-defined parameters (uri, _meta, inputResponses, requestState) to permission callbacks, the mcp_adapter_pre_resource_read filter, and resource handlers. Unknown request keys are dropped.
2025-11-25 tools/call responses omit structuredContent when a tool returns a JSON list, because that schema types the field as an object. The text block still carries the encoded list. 2026-07-28 responses keep the list.

Fixed

Default abilities register when another plugin initializes the Abilities API before the MCP server initializes.
mcp-adapter/get-ability-info serializes an empty input_schema as {} instead of [].

Open source →

v0.6.012 Aug 2026

MCP Adapter 0.6.0 improves protocol compatibility, resource metadata handling, session reliability, WP-CLI behavior, and coexistence with plugins that

MCP Adapter 0.6.0 improves protocol compatibility, resource metadata handling, session reliability, WP-CLI behavior, and coexistence with plugins that bundle their own copy of the adapter.

Before upgrading

WordPress 6.9 or newer is now required. The standalone Abilities API plugin is no longer a supported installation path.
Abilities with meta.public: true are now exposed through the default MCP server unless meta.mcp.public explicitly opts out. Existing permission callbacks and capability checks still apply.
On multisite only, active Streamable HTTP sessions must reconnect once after upgrading because session storage moves from a network-wide key to separate per-site keys. Single-site installations are unaffected.
The MIME validation helpers previously exposed by McpValidator have been removed. Integrations calling them directly should apply their own application-specific MIME validation.

MCP resources and metadata

Preserve _meta on resource contents, embedded resources, content blocks, and prompt messages.
Omit malformed _meta without discarding the payload it accompanies.
Emit mimeType exactly as declared, including values with parameters such as text/html;profile=mcp-app.
Correctly handle blob-only resource contents.
Support resources/templates/list, returning an empty template list when no templates are available.
Match resource URI schemes case-insensitively, so clients can read resources even when they normalize the scheme to lowercase.

These changes improve compatibility with MCP Apps and other clients that depend on resource metadata.

Reliability and compatibility

Protect concurrent session mutations with bounded retries, reducing the risk of one request overwriting another session.
Scope session storage by blog on WordPress multisite.
Use Jetpack Autoloader so the newest available WP\MCP classes win when the standalone adapter and another plugin bundle different versions.
Normalize empty arguments for schema-defining abilities, allowing valid zero-argument tool calls to execute correctly.

WP-CLI improvements

Keep JSON-RPC stdout clean when wp mcp-adapter serve selects the default server.
Use WP-CLI’s global --user argument instead of registering a conflicting local option.

Additional improvements

Block direct execution of plugin PHP files.
Clarify that the Abilities API is included in WordPress 6.9 and newer.
Document the required ability category field and improve examples throughout the documentation.
Expand automated compatibility, dependency, and Plugin Check coverage.

New contributors

Welcome to @johnbillion, @graham73may, @gziolo, @ustramooner, @matthewfarrugia, @robertocyrino, and @mathetos, who made their first contributions to MCP Adapter in this release.

Thank you to everyone who contributed code, documentation, testing, and reviews.

Full Changelog: v0.5.0...v0.6.0

Open source →

Additional notes

Breaking Changes

WordPress 6.9 or newer is now required. The standalone Abilities API plugin is no longer a supported installation path.
Abilities with meta.public: true are now exposed through the default MCP server unless meta.mcp.public explicitly opts out. Existing permission callbacks and capability checks still apply.
On multisite only, active Streamable HTTP sessions must reconnect once after upgrading, because session storage moves from a network-wide key to separate per-site keys. Single-site installations are unaffected.
The MIME validation helpers previously exposed by McpValidator have been removed. Integrations calling them directly should apply their own application-specific MIME validation.

Added

Support for resources/templates/list, returning an empty template list when no templates are available.
Blocked direct execution of plugin PHP files.
Expanded automated compatibility, dependency, and Plugin Check coverage.

Changed

Jetpack Autoloader is now used so the newest available WP\MCP classes win when the standalone adapter and another plugin bundle different versions.
Session storage is scoped by blog on WordPress multisite.
Concurrent session mutations are protected with bounded retries, reducing the risk of one request overwriting another session.
Documentation clarifies that the Abilities API is included in WordPress 6.9 and newer, documents the required ability category field, and improves examples throughout.

Fixed

_meta is preserved on resource contents, embedded resources, content blocks, and prompt messages.
Malformed _meta is omitted without discarding the payload it accompanies.
mimeType is emitted exactly as declared, including values with parameters such as text/html;profile=mcp-app.
Blob-only resource contents are handled correctly.
Resource URI schemes are matched case-insensitively, so clients can read resources even when they normalize the scheme to lowercase.
Empty arguments are normalized for schema-defining abilities, allowing valid zero-argument tool calls to execute.
wp mcp-adapter serve keeps JSON-RPC stdout clean when selecting the default server.
WP-CLI's global --user argument is used instead of registering a conflicting local option.

Open source →

v0.5.014 Apr 2026

v0.5.0 is a major internal upgrade for MCP Adapter. The biggest change is the adoption of wordpress/php-mcp-schema across the plugin, so MCP responses

Highlights

v0.5.0 is a major internal upgrade for MCP Adapter. The biggest change is the adoption of wordpress/php-mcp-schema across the plugin, so MCP responses now use typed protocol DTOs instead of hand-built arrays.

This gives us a more consistent and spec-aligned foundation for tools, resources, prompts, initialization, and error responses, while making future MCP spec updates easier to support.

For most users, this should be a seamless upgrade. Existing ability registration, create_server(), and WordPress hooks continue to work as before. If you have custom handlers, transports, or code that depends on internal component structures, review the migration guide for upgrade details.

Included in this release

Full integration of wordpress/php-mcp-schema throughout the adapter
Typed DTO-based handling for MCP tools, resources, prompts, initialization, and JSON-RPC errors
Protocol version negotiation support for 2025-11-25, 2025-06-18, and 2024-11-05
Validation, encapsulation, and type-safety improvements across the core and domain layers
Security hardening with stricter input validation and fail-closed permission handling
Better observability for protocol errors and isError tool responses
Reduced SessionManager write amplification to lower lock contention
Packaging and dependency updates, including the php-mcp-schema v0.1.1 follow-up for cleaner Composer dist archives

Documentation

Documentation was expanded significantly for this release, including:

A new v0.5.0 migration guide
Updated architecture documentation
Improvements to the default server guide and troubleshooting docs
README updates, including WordPress 6.9/7.0 notes
Additional guidance for ability registration

Contributors

New Contributors

@spenserhale made their first contribution in #44
@karthikeya-io made their first contribution in #169
@itsgajendraSingh made their first contribution in #165

Full Changelog: v0.4.1...v0.5.0

Open source →

Additional notes

Added

Full integration of wordpress/php-mcp-schema throughout the adapter, so MCP responses use typed protocol DTOs instead of hand-built arrays.
Typed DTO handling for MCP tools, resources, prompts, initialization, and JSON-RPC errors.
Protocol version negotiation for 2025-11-25, 2025-06-18, and 2024-11-05.

Changed

Validation, encapsulation, and type-safety improvements across the core and domain layers.
Security hardening with stricter input validation and fail-closed permission handling.
Reduced SessionManager write amplification to lower lock contention.
Packaging and dependency updates, including the php-mcp-schema v0.1.1 follow-up for cleaner Composer dist archives.
Improved observability for protocol errors and isError tool responses.

Existing ability registration, create_server(), and WordPress hooks are unchanged. Custom handlers, transports, or code depending on internal component structures should review the v0.5.0 migration guide.

Open source →

v0.3.06 Nov 2025

Version 0.3.0 introduces significant architectural improvements with enhanced observability, streamlined transport infrastructure, and better error ha

Version 0.3.0 introduces significant architectural improvements with enhanced observability, streamlined transport infrastructure, and better error handling compliance.

Breaking Changes

Observability System Changes

Event Naming with Status Tags

All observability events now use unified names with a status tag instead of separate success/failure event names.

Before:
$handler->record_event('mcp.request.success', ['method' => 'tools/call']);
$handler->record_event('mcp.request.error', ['method' => 'tools/call']);

After:
$handler->record_event('mcp.request', ['status' => 'success', 'method' => 'tools/call']);
$handler->record_event('mcp.request', ['status' => 'error', 'method' => 'tools/call']);

Instance-Based Handlers

Observability handlers now use instance methods instead of static methods. If you have custom handlers implementing McpObservabilityHandlerInterface, update from static to instance methods:

// Before
class MyHandler implements McpObservabilityHandlerInterface {
    public static function record_event(string $event, array $tags = []): void { }
    public static function record_timing(string $metric, float $duration_ms, array $tags = []): void { }
}

// After
class MyHandler implements McpObservabilityHandlerInterface {
    public function record_event(string $event, array $tags = [], ?float $duration_ms = null): void {
        // Single method handles both events and timing
    }
}

Removed Method

McpObservabilityHelperTrait::record_error_event() has been removed. Use record_event() with status and error categorization instead.

Transport Layer Changes

Removed Transports

RestTransport and StreamableTransport have been removed and replaced by the unified HttpTransport class, which provides all functionality of both previous implementations with enhanced capabilities.

Migration:

All existing servers using these transports should update to use HttpTransport:

use WP\MCP\Transport\HttpTransport;

$adapter->create_server(
    'my-server',
    'namespace',
    'mcp',
    'Server Name',
    'Description',
    '1.0.0',
    [ HttpTransport::class ],  // Updated
    ErrorLogMcpErrorHandler::class
);

Hook Name Standardization

All WordPress filter/action names now use the mcp_adapter_ prefix for consistency:

// Before
add_filter('mcp_validation_enabled', $callback);

// After
add_filter('mcp_adapter_validation_enabled', $callback);## What's New

Unified HTTP Transport

The new HttpTransport class provides a modern, spec-compliant transport implementation with session management, streaming support, and enhanced error handling.

Enhanced Error Handling

Comprehensive refactoring to use WP_Error pattern throughout the codebase, replacing exceptions for better WordPress integration. All error responses now comply with the MCP specification format.

Metadata-Driven Observability

Observability events are now recorded centrally at the transport layer with automatic metadata extraction from handler responses, providing richer context and better performance tracking.

Improved Documentation

Updated guides covering transport permissions, custom transport implementation, error handling patterns, and comprehensive migration instructions.

Bug Fixes

Fixed metadata leaking into tool response content
Fixed null parameter handling in Prompts and Resources handlers
Fixed parameter handling for abilities without input schemas
Fixed WP_Error handling across all handler types
Fixed prompt input schema validation
Fixed WP-CLI initialization timing issues

Full Migration Guide

See docs/migration/v0.3.0.md for detailed migration instructions and examples.

What's Changed

Updating composer instructions by @jonathanbossenger in #10
chore: scaffold repo for WPCS and WordPress/* by @justlevine in #14
chore: configure PHPStan by @justlevine in #13
ci: setup test workflow for PHPCS/PHPStan by @justlevine in #15
dev: downgrade php 7.4 by @justlevine in #16
dev: scaffold WordPress plugin wrapper by @justlevine in #18
Update MCP server creation instructions in README by @jonathanbossenger in #21
dev: move src to includes and post-scaffold cleanup by @justlevine in #20
chore(phpstan): add PHP8 stubs for WP polyfills by @justlevine in #29
Introduce Props Bot workflow by @desrosj in #30
Use abilities instead of capabilities by @aaronjorbin in #25
ci: reenable codecov by @justlevine in #28
dev!: cleanup and update compatibility with abilities-api v0.1.0 by @justlevine in #27
dev!: refactor non-registry functionality from Core/McpAdapter by @justlevine in #26
Add type property to empty input schema by @stormrockwell in #36
Add structuredContent to tool callback response by @finleyjchen in #37
chore: backfill props for #36 and #37 by @justlevine in #41
Relax parameter validation to allow some falsy values as parameters. by @aaronfc in #43
Major Refactor: Enhanced Transport Infrastructure, Default Server, and CLI Support by @galatanovidiu in #48
Fix tool error handling to comply with MCP specification by @galatanovidiu in #73
Fix WP_Error handling in PromptsHandler and ResourcesHandler by @galatanovidiu in #74
Fix parameter handling for abilities without input schemas on ExecuteAbilityAbility by @galatanovidiu in #76
Add wp_ prefix to hook names. by @mindctrl in #81
Doc updates by @jonathanbossenger in #83
Fix metadata appearing in tool response content by @galatanovidiu in #72
Fix prompt parameter validation by converting input_schema to MCP arguments by @galatanovidiu in #78
Fix null parameter handling in Prompts and Resources handlers by @galatanovidiu in #77
Docs: Update testing guide to use wp-env workflow by @galatanovidiu in #67
Refactor error handling: Replace exceptions with WP_Error pattern by @galatanovidiu in #71
Ensures init action fires before initializing in WP-CLI by @galatanovidiu in #86

New Contributors

@justlevine made their first contribution in #14
@desrosj made their first contribution in #30
@aaronjorbin made their first contribution in #25
@stormrockwell made their first contribution in #36
@finleyjchen made their first contribution in #37
@aaronfc made their first contribution in #43
@mindctrl made their first contribution in #81

Full Changelog: v0.1.0...v0.3.0

Open source →

Additional notes

Breaking Changes

RestTransport and StreamableTransport have been removed and replaced by the unified HttpTransport class (#48).
Observability events now use unified names with a status tag instead of separate success and failure event names.
Observability handlers now use instance methods instead of static methods, and McpObservabilityHelperTrait::record_error_event() has been removed.
All filter and action names now use the mcp_adapter_ prefix (#81).

Added

Unified HttpTransport with session management, streaming support, and enhanced error handling (#48).
Metadata-driven observability, recorded centrally at the transport layer with automatic metadata extraction from handler responses.

Changed

Error handling refactored to use the WP_Error pattern throughout, replacing exceptions (#71).

Fixed

Tool error handling now complies with the MCP specification (#73).
Metadata no longer leaks into tool response content (#72).
WP_Error handling in PromptsHandler and ResourcesHandler (#74).
Null parameter handling in Prompts and Resources handlers (#77).
Parameter handling for abilities without input schemas (#76).
Prompt parameter validation, by converting input_schema to MCP arguments (#78).
The init action now fires before initializing in WP-CLI (#86).

See the v0.3.0 migration guide for detailed upgrade instructions.

wordpress/mcp-adapter

Release timeline

Releases

Before you upgrade

Highlights

What's Changed

New Contributors

Props

Breaking Changes

Added

Changed

Fixed

Who should upgrade

Fixed

Fixed

Before upgrading

MCP resources and metadata

Reliability and compatibility

WP-CLI improvements

Additional improvements

New contributors

Breaking Changes

Added

Changed

Fixed

Highlights

Included in this release

Documentation

Contributors

New Contributors

Added

Changed

What's Changed

New Contributors

Fixed

Bug Fixes

Improvements

Documentation

New Contributors

Added

Changed

Fixed

Breaking Changes

Observability System Changes

Transport Layer Changes

Hook Name Standardization

Unified HTTP Transport

Enhanced Error Handling

Metadata-Driven Observability

Improved Documentation

Bug Fixes

Full Migration Guide

What's Changed

New Contributors

Breaking Changes

Added

Changed

Fixed

First Stable Release of WordPress MCP Adapter

What's Included

Core Features

MCP Component Support

Enterprise-Ready Architecture

What's Changed

New Contributors

Added