PHPackages wordpress/mcp-adapter - PHPackages - PHPackages [Skip to content](#main-content)[PHPackages](/)[Directory](/)[Categories](/categories)[Trending](/trending)[Leaderboard](/leaderboard)[Changelog](/changelog)[Analyze](/analyze)[Collections](/collections)[Log in](/login)[Sign up](/register) 1. [Directory](/) 2. / 3. [API Development](/categories/api) 4. / 5. wordpress/mcp-adapter ActiveWordpress-plugin[API Development](/categories/api) wordpress/mcp-adapter ===================== Adapter for Abilities API, letting WordPress abilities to be used as MCP tools, resources or prompts v0.4.1(5mo ago)74855.8k↑53.9%95[33 issues](https://github.com/WordPress/mcp-adapter/issues)[1 PRs](https://github.com/WordPress/mcp-adapter/pulls)1GPL-2.0-or-laterPHPPHP ^7.4 || ^8.0CI passing Since Aug 13Pushed 1mo ago24 watchersCompare [ Source](https://github.com/WordPress/mcp-adapter)[ Packagist](https://packagist.org/packages/wordpress/mcp-adapter)[ Docs](https://github.com/wordpress/mcp-adapter)[ RSS](/packages/wordpress-mcp-adapter/feed)WikiDiscussions trunk Synced 1mo ago READMEChangelog (4)Dependencies (14)Versions (21)Used By (1) MCP Adapter =========== [](#mcp-adapter) Part of the [**AI Building Blocks for WordPress** initiative](https://make.wordpress.org/ai/2025/07/17/ai-building-blocks) The official WordPress package for MCP integration that exposes WordPress abilities as [Model Context Protocol (MCP)](https://modelcontextprotocol.io) tools, resources, and prompts for AI agents. [![Ask DeepWiki](https://camo.githubusercontent.com/0f5ae213ac378635adeb5d7f13cef055ad2f7d9a47b36de7b1c67dbe09f609ca/68747470733a2f2f6465657077696b692e636f6d2f62616467652e737667)](https://deepwiki.com/WordPress/mcp-adapter) Overview -------- [](#overview) This adapter bridges WordPress's Abilities API with the [MCP specification](https://modelcontextprotocol.io/specification/2025-06-18/), providing a standardized way for AI agents to interact with WordPress functionality. It includes HTTP and STDIO transport support, comprehensive error handling, and an extensible architecture for custom integrations. Features -------- [](#features) ### Core Functionality [](#core-functionality) - **Ability-to-MCP Conversion**: Automatically converts WordPress abilities into MCP tools, resources, and prompts - **Multi-Server Management**: Create and manage multiple MCP servers with unique configurations - **Extensible Transport Layer**: - **HTTP Transport**: Unified transport implementing [MCP 2025-06-18 specification](https://modelcontextprotocol.io/specification/2025-06-18/basic/transports.md) for HTTP-based communication - **STDIO Transport**: Process-based communication via standard input/output for local development and CLI integration - **Custom Transport Support**: Implement `McpTransportInterface` to create specialized communication protocols - **Multi-Transport Configuration**: Configure servers with multiple transport methods simultaneously - **Flexible Error Handling**: - **Built-in Error Handler**: Default WordPress-compatible error logging included - **Custom Error Handlers**: Implement `McpErrorHandlerInterface` for custom logging, monitoring, or notification systems - **Server-specific Handlers**: Different error handling strategies per MCP server - **Observability**: - **Built-in Observability**: Default zero-overhead metrics tracking with configurable handlers - **Custom Observability Handlers**: Implement `McpObservabilityHandlerInterface` for integration with monitoring systems - **Validation**: Built-in validation for tools, resources, and prompts with extensible validation rules - **Permission Control**: Granular permission checking for all exposed functionality with configurable [transport permissions](docs/guides/transport-permissions.md) ### MCP Component Support [](#mcp-component-support) - **[Tools](https://modelcontextprotocol.io/specification/2025-06-18/server/tools.md)**: Convert WordPress abilities into executable MCP tools for AI agent interactions - **[Resources](https://modelcontextprotocol.io/specification/2025-06-18/server/resources.md)**: Expose WordPress data as MCP resources for contextual information access - **[Prompts](https://modelcontextprotocol.io/specification/2025-06-18/server/prompts.md)**: Transform abilities into structured MCP prompts for AI guidance and templates - **Server Discovery**: Automatic registration and discovery of MCP servers following MCP protocol standards - **Built-in Abilities**: Core WordPress abilities for system introspection and ability management - **CLI Integration**: WP-CLI commands supporting STDIO transport as defined in MCP specification Understanding Abilities as MCP Components ----------------------------------------- [](#understanding-abilities-as-mcp-components) The MCP Adapter transforms WordPress abilities into MCP components: - **Tools**: WordPress abilities become executable MCP tools for AI agent interactions - **Resources**: WordPress abilities expose data as MCP resources for contextual information - **Prompts**: WordPress abilities provide structured MCP prompts for AI guidance For detailed information about MCP components, see the [Model Context Protocol specification](https://modelcontextprotocol.io/specification/2025-06-18/). Architecture ------------ [](#architecture) ### Component Overview [](#component-overview) ``` ./includes/ │ # Core system components ├── Core/ │ ├── McpAdapter.php # Main registry and server management │ ├── McpServer.php # Individual server configuration │ ├── McpComponentRegistry.php # Component registration and management │ └── McpTransportFactory.php # Transport instantiation factory │ │ # Built-in abilities for MCP functionality ├── Abilities/ │ ├── DiscoverAbilitiesAbility.php # Ability discovery │ ├── ExecuteAbilityAbility.php # Ability execution │ └── GetAbilityInfoAbility.php # Ability introspection │ │ # CLI and STDIO transport support ├── Cli/ │ ├── McpCommand.php # WP-CLI commands │ └── StdioServerBridge.php # STDIO transport bridge │ │ # Business logic and MCP components ├── Domain/ │ │ # MCP Tools implementation │ ├── Tools/ │ │ ├── McpTool.php # Base tool class │ │ ├── RegisterAbilityAsMcpTool.php # Ability-to-tool conversion │ │ └── McpToolValidator.php # Tool validation │ │ # MCP Resources implementation │ ├── Resources/ │ │ ├── McpResource.php # Base resource class │ │ ├── RegisterAbilityAsMcpResource.php # Ability-to-resource conversion │ │ └── McpResourceValidator.php # Resource validation │ │ # MCP Prompts implementation │ └── Prompts/ │ ├── Contracts/ # Prompt interfaces │ │ └── McpPromptBuilderInterface.php # Prompt builder interface │ ├── McpPrompt.php # Base prompt class │ ├── McpPromptBuilder.php # Prompt builder implementation │ ├── McpPromptValidator.php # Prompt validation │ └── RegisterAbilityAsMcpPrompt.php # Ability-to-prompt conversion │ │ # Request processing handlers ├── Handlers/ │ ├── HandlerHelperTrait.php # Shared handler utilities │ ├── Initialize/ # Initialization handlers │ ├── Tools/ # Tool request handlers │ ├── Resources/ # Resource request handlers │ ├── Prompts/ # Prompt request handlers │ └── System/ # System request handlers │ │ # Infrastructure concerns ├── Infrastructure/ │ │ # Error handling system │ ├── ErrorHandling/ │ │ ├── Contracts/ # Error handling interfaces │ │ │ └── McpErrorHandlerInterface.php # Error handler interface │ │ ├── ErrorLogMcpErrorHandler.php # Default error handler │ │ ├── NullMcpErrorHandler.php # Null object pattern │ │ └── McpErrorFactory.php # Error response factory │ │ # Monitoring and observability │ └── Observability/ │ ├── Contracts/ # Observability interfaces │ │ └── McpObservabilityHandlerInterface.php # Observability interface │ ├── ErrorLogMcpObservabilityHandler.php # Default handler │ ├── NullMcpObservabilityHandler.php # Null object pattern │ └── McpObservabilityHelperTrait.php # Helper trait │ │ # Transport layer implementations ├─── Transport/ │ ├── Contracts/ │ │ ├── McpTransportInterface.php # Base transport interface │ │ └── McpRestTransportInterface.php # REST transport interface │ ├── HttpTransport.php # Unified HTTP transport (MCP 2025-06-18) │ │ # Transport infrastructure │ └── Infrastructure/ │ ├── HttpRequestContext.php # HTTP request context │ ├── HttpRequestHandler.php # HTTP request processing │ ├── HttpSessionValidator.php # Session validation │ ├── JsonRpcResponseBuilder.php # JSON-RPC response building │ ├── McpTransportContext.php # Transport context │ ├── RequestRouter.php # Request routing │ └── SessionManager.php # Session management │ │ # Server factories ├── Servers/ └── DefaultServerFactory.php # Default server creation ``` ### Key Classes [](#key-classes) #### `McpAdapter` [](#mcpadapter) The main registry class that manages multiple MCP servers: - **Singleton Pattern**: Ensures single instance across the application - **Server Management**: Create, configure, and retrieve MCP servers - **Initialization**: Handles WordPress integration and action hooks - **REST API Integration**: Automatically integrates with WordPress REST API #### `McpServer` [](#mcpserver) Individual server management with comprehensive configuration: - **Server Identity**: Unique ID, namespace, route, name, and description - **Component Registration**: Tools, resources, and prompts management - **Transport Configuration**: Multiple transport method support - **Error Handling**: Server-specific error handling and logging - **Validation**: Built-in validation for all registered components Dependencies ------------ [](#dependencies) ### Required Dependencies [](#required-dependencies) - **PHP**: >= 7.4 - **[WordPress Abilities API](https://github.com/WordPress/abilities-api)**: For ability registration and management ### WordPress Abilities API Integration [](#wordpress-abilities-api-integration) This adapter requires the [WordPress Abilities API](https://github.com/WordPress/abilities-api), which provides: - Standardized ability registration (`wp_register_ability()`) - Ability retrieval and management (`wp_get_ability()`) - Schema definition for inputs and outputs - Permission callback system - Execute callback system Installation ------------ [](#installation) ### With Composer (Primary Installation Method) [](#with-composer-primary-installation-method) The MCP Adapter is designed to be installed as a Composer package. This is the primary and recommended installation method: ``` composer require wordpress/abilities-api wordpress/mcp-adapter ``` This will automatically install both the WordPress Abilities API and MCP Adapter as dependencies in your project. #### Using Jetpack Autoloader (Highly Recommended) [](#using-jetpack-autoloader-highly-recommended) When multiple plugins use the MCP Adapter, it's highly recommended to use the [Jetpack Autoloader](https://github.com/Automattic/jetpack-autoloader) to prevent version conflicts. The Jetpack Autoloader ensures that only the latest version of shared packages is loaded, eliminating conflicts when different plugins use different versions of the same dependency. Add the Jetpack Autoloader to your project: ``` composer require automattic/jetpack-autoloader ``` Then load it in your main plugin file instead of the standard Composer autoloader: ```