 |
VOOZH | about |
|
VOOZH | about |
This document details the composer.json configuration for the MCP Adapter package, including dependency management, autoloading setup, and development tooling integration. For installation instructions and usage examples, see Installation.
The MCP Adapter is defined as a Composer library package that can be required by WordPress plugins or themes. The package metadata establishes its identity in the Composer ecosystem.
Sources: composer.json2-4
| Field | Value | Purpose |
|---|---|---|
name | wordpress/mcp-adapter | Package identifier in Packagist |
type | library | Indicates this is a reusable library, not a standalone application |
license | GPL-2.0-or-later | GPL v2+ license for WordPress compatibility |
homepage | https://github.com/wordpress/mcp-adapter | Source repository location |
Sources: composer.json2-26
The package uses targeted keywords for discoverability in package registries:
wordpress - WordPress ecosystem integrationmcp / model-context-protocol - Protocol implementationabilities-api - WordPress Abilities API integrationadapter / integration - Architectural roleai - AI agent functionalitySources: composer.json6-15
The stability configuration controls which package versions Composer considers during dependency resolution:
| Setting | Value | Effect |
|---|---|---|
minimum-stability | dev | Allows dev, alpha, beta, RC, and stable versions |
prefer-stable | true | Prioritizes stable releases when available |
This combination allows installation of development versions when necessary (e.g., unreleased WordPress Abilities API) while preferring stable releases when they exist.
Sources: composer.json27-28
The platform configuration enforces PHP 7.4 compatibility for dependency resolution:
This ensures dependencies are resolved as if running on PHP 7.4, even when using newer PHP versions for development. This prevents inadvertently requiring dependencies that need PHP 8.0+.
Sources: composer.json29-32
| Setting | Value | Purpose |
|---|---|---|
sort-packages | true | Maintains alphabetical ordering in composer.json |
optimize-autoloader | true | Generates optimized class maps for production |
preferred-install | dist | Downloads distributions (zip/tar) instead of cloning repositories |
Sources: composer.json33-35
Composer plugins require explicit permission. The MCP Adapter allows these plugins:
| Plugin | Purpose |
|---|---|
automattic/jetpack-autoloader | Version conflict resolution for shared dependencies |
composer/installers | Custom installation paths for WordPress plugins/themes |
dealerdirect/phpcodesniffer-composer-installer | Automatic PHPCS standards registration |
phpstan/extension-installer | Automatic PHPStan extension loading |
Sources: composer.json36-41
The package uses Wpackagist to access WordPress plugins via Composer:
This allows requiring WordPress plugins like wpackagist-plugin/plugin-check as Composer dependencies for development tooling.
Sources: composer.json43-52
The MCP Adapter uses PSR-4 autoloading to map the WP\MCP namespace to the includes/ directory:
Sources: composer.json60-64
This maps any class with namespace WP\MCP\* to a file under includes/. For example:
WP\MCP\Core\McpAdapter → includes/Core/McpAdapter.phpWP\MCP\Transport\HttpTransport → includes/Transport/HttpTransport.phpSources: composer.json60-64
Test classes use the WP\MCP\Tests namespace mapped to the tests/ directory. This is only loaded in development environments when running tests.
Sources: composer.json65-71
When multiple plugins use the MCP Adapter, the Jetpack Autoloader prevents version conflicts by loading the newest version of shared classes.
Sources: docs/getting-started/installation.md15-41
| Benefit | Description |
|---|---|
| Version Conflict Resolution | Automatically loads the newest version of shared classes |
| Plugin Compatibility | Multiple plugins can require different versions of MCP Adapter |
| WordPress Optimization | Designed specifically for WordPress plugin ecosystems |
| Automatic Management | No manual class version tracking required |
To use Jetpack Autoloader:
Require it as a dependency:
Load via autoload_packages.php instead of autoload.php:
Sources: docs/getting-started/installation.md15-41
The package has minimal runtime requirements:
| Dependency | Version Constraint | Rationale |
|---|---|---|
php | ^7.4 || ^8.0 | Supports PHP 7.4 through 8.4, matching WordPress minimum requirements |
The WordPress Abilities API is a runtime dependency but is not listed in composer.json because it's expected to be provided by the WordPress environment (either as a plugin or in core).
Sources: composer.json72-74
The package includes extensive development tooling:
Sources: composer.json75-90
| Category | Package | Version | Purpose |
|---|---|---|---|
| Coding Standards | automattic/vipwpcs | ^3.0 | WordPress VIP coding standards |
slevomat/coding-standard | ^8.0 | Strict PHP coding standards | |
phpcompatibility/php-compatibility | 10.x-dev | PHP cross-version compatibility checks | |
phpcompatibility/phpcompatibility-wp | ^2.1 | WordPress-specific compatibility | |
| Static Analysis | phpstan/phpstan | ^2.1.22 | Static analysis engine |
phpstan/extension-installer | ^1.3 | Automatic extension loading | |
phpstan/phpstan-deprecation-rules | ^2.0.3 | Deprecation warnings | |
szepeviktor/phpstan-wordpress | ^2.0 | WordPress-specific type definitions | |
| Testing | phpunit/phpunit | ^9.6 | Unit test framework |
wp-phpunit/wp-phpunit | ^6.5 | WordPress test suite integration | |
yoast/phpunit-polyfills | ^4.0 | PHPUnit version compatibility | |
| Type Stubs | php-stubs/wp-cli-stubs | ^2.12 | WP-CLI type definitions for StdioServerBridge |
phpstan/php-8-stubs | ^0.4.24 | PHP 8 function stubs for PHP 7.4 analysis | |
| WordPress Tools | wpackagist-plugin/plugin-check | ^1.6 | WordPress plugin validation tool |
Sources: composer.json75-90
The package configures custom installation paths for specific dependencies:
This ensures the plugin-check WordPress plugin is installed to a custom location where it can be accessed for plugin validation during development.
Sources: composer.json53-59
The package defines scripts for common development tasks:
Sources: composer.json91-96
| Script | Command | Purpose |
|---|---|---|
lint:php | phpcs | Check PHP code against WordPress coding standards |
lint:php:fix | phpcbf | Automatically fix coding standard violations |
lint:php:stan | vendor/bin/phpstan analyse --memory-limit=1G | Run PHPStan static analysis with 1GB memory limit |
test | phpunit --strict-coverage | Run PHPUnit tests with strict coverage enforcement |
These scripts can be executed via:
For CI/CD integration details, see CI/CD Pipeline. For PHPStan configuration specifics, see PHPStan Configuration.
Sources: composer.json91-96
The composer.json platform configuration works in conjunction with PHPStan configuration for cross-version analysis:
This ensures dependencies are resolved for PHP 7.4, while PHPStan is configured to analyze code for PHP 7.4–8.4 compatibility via phpstan.neon.dist. See PHPStan Configuration for the full analysis configuration.
Sources: composer.json30-32 phpstan.neon.dist17-19
The wpackagist-plugin/plugin-check dependency enables validation of the MCP Adapter against WordPress plugin standards:
This tool checks for:
Sources: composer.json88 composer.json54-58
Refresh this wiki