MCP Adapter

Part of the AI Building Blocks for WordPress initiative

The official WordPress package for MCP integration that exposes WordPress abilities as Model Context Protocol (MCP) tools, resources, and prompts for AI agents.

Overview

This adapter bridges WordPress's Abilities API with the MCP specification, 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

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 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

MCP Component Support

• Tools: Convert WordPress abilities into executable MCP tools for AI agent interactions
• Resources: Expose WordPress data as MCP resources for contextual information access
• Prompts: 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

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.

Architecture

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/
│   │   # Shared contracts
│   ├── Contracts/
│   │   └── McpComponentInterface.php       # Contract for MCP components
│   │   # Shared utilities
│   ├── Utils/
│   │   ├── McpNameSanitizer.php            # MCP name sanitization
│   │   ├── McpValidator.php                # MCP name/URI/schema validation
│   │   ├── McpAnnotationMapper.php         # Annotation mapping from abilities
│   │   ├── SchemaTransformer.php           # Schema format transformation
│   │   ├── ContentBlockHelper.php          # Content block DTO factory
│   │   └── AbilityArgumentNormalizer.php   # Argument normalization
│   │   # 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
│       ├── ConsoleObservabilityHandler.php          # Console output handler
│       └── FailureReason.php                        # Standardized failure reasons
│
│   # 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

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

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

• PHP: >= 7.4
• WordPress: >= 6.9
• php-mcp-schema (^0.1.0): Typed DTOs for MCP protocol types (MCP 2025-11-25)

Installation

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/mcp-adapter

Using Jetpack Autoloader (Highly Recommended)

When multiple plugins use the MCP Adapter, it's highly recommended to use the 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:

<?php
// Load the Jetpack autoloader instead of vendor/autoload.php
require_once plugin_dir_path( __FILE__ ) . 'vendor/autoload_packages.php';

Benefits of using Jetpack Autoloader:

• Version Conflict Resolution: Automatically loads the latest version of shared packages
• Plugin Compatibility: Prevents errors when multiple plugins use different versions of MCP Adapter
• WordPress Optimized: Designed specifically for WordPress plugin development
• Automatic Management: No manual intervention needed when plugins update their dependencies

As a Plugin (Alternative Method)

Alternatively, you can install the MCP Adapter as a traditional WordPress plugin, though the Composer package method is preferred for most use cases.

From GitHub Releases

Download the latest stable release from the GitHub Releases page.

Development Version (Git Clone)

For the latest development version or to contribute to the project:

# Clone the repository
git clone https://github.com/WordPress/mcp-adapter.git wp-content/plugins/mcp-adapter

# Navigate to the plugin directory
cd wp-content/plugins/mcp-adapter

# Install dependencies
composer install

This will give you the latest development version from the trunk branch with all dependencies installed.

With WP-Env

// .wp-env.json
{
  "$schema": "https://schemas.wp.org/trunk/wp-env.json",
  // ... other config ...
  "plugins": [
    "WordPress/mcp-adapter",
    // ... other plugins ...
  ],
  // ... more config ...
}

Using MCP Adapter in Your Plugin

Using the MCP Adapter in your plugin is straightforward, just check availability and instantiate:

use WP\MCP\Core\McpAdapter;

// 1. Check if MCP Adapter is available
if ( ! class_exists( McpAdapter::class ) ) {
    // Handle missing dependency (show admin notice, etc.)
    return;
}

// 2. Initialize the adapter
McpAdapter::instance();
// That's it!

Basic Usage

The MCP Adapter automatically creates a default server that exposes registered WordPress abilities through a layered architecture. This provides immediate MCP functionality without requiring manual server configuration.

How it works:

• WordPress abilities registered via wp_register_ability() with the meta.mcp.public flag set to true are discoverable and executable on the default server via its built-in adapter tools
• On the default server, public abilities are accessed through mcp-adapter/discover-abilities, mcp-adapter/get-ability-info, and mcp-adapter/execute-ability rather than being auto-registered individually in tools/list
• Alternatively, abilities can be explicitly listed when creating a custom MCP server; in that case, they can be exposed directly as MCP tools, resources, or prompts without requiring the meta.mcp.public flag
• The default server supports both HTTP and STDIO transports and supports multiple MCP protocol versions
• Built-in error handling and observability are included
• Access via HTTP: /wp-json/mcp/mcp-adapter-default-server
• Access via STDIO: wp mcp-adapter serve --server=mcp-adapter-default-server

// Simply register a WordPress ability
add_action( 'wp_abilities_api_init', function() {
    wp_register_ability( 'my-plugin/get-posts', [
        'label' => 'Get Posts',
        'description' => 'Retrieve WordPress posts with optional filtering',
        'category' => 'site',
        'input_schema' => [
            'type' => 'object',
            'properties' => [
                'numberposts' => [
                    'type' => 'integer',
                    'description' => 'Number of posts to retrieve',
                    'default' => 5,
                    'minimum' => 1,
                    'maximum' => 100
                ],
                'post_status' => [
                    'type' => 'string',
                    'description' => 'Post status to filter by',
                    'enum' => ['publish', 'draft', 'private'],
                    'default' => 'publish'
                ]
            ]
        ],
        'output_schema' => [
            'type' => 'array',
            'items' => [
                'type' => 'object',
                'properties' => [
                    'ID' => ['type' => 'integer'],
                    'post_title' => ['type' => 'string'],
                    'post_content' => ['type' => 'string'],
                    'post_date' => ['type' => 'string'],
                    'post_author' => ['type' => 'string']
                ]
            ]
        ],
        'execute_callback' => function( $input ) {
            $args = [
                'numberposts' => $input['numberposts'] ?? 5,
                'post_status' => $input['post_status'] ?? 'publish'
            ];
            return get_posts( $args );
        },
        'permission_callback' => function() {
            return current_user_can( 'read' );
        },
        'meta' => [
            'mcp' => [
                'public' => true, // Required for default MCP server access
            ],
        ],
    ]);
});

// With the meta.mcp.public flag, the ability is exposed through the default MCP server.
// In the default server configuration, discover it via `discover-abilities`
// and invoke it via `mcp-adapter/execute-ability` rather than expecting
// it to appear as its own entry in `tools/list`.
// Without the meta.mcp.public flag, abilities are only accessible
// through custom MCP servers that explicitly list them.

For detailed information about creating WordPress abilities, see the Abilities API developer documentation.

Connecting to MCP Servers

The MCP Adapter supports multiple connection methods. Here are examples for connecting with MCP clients:

STDIO Transport (Local Development)

For local development and testing, you can interact directly with MCP servers using WP-CLI commands:

# List all available MCP servers
wp mcp-adapter list

# Test the discover abilities tool to see all available WordPress abilities
echo '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"mcp-adapter-discover-abilities","arguments":{}}}' | wp mcp-adapter serve --user=admin --server=mcp-adapter-default-server

# Test listing available tools
echo '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}' | wp mcp-adapter serve --user=admin --server=mcp-adapter-default-server

MCP Client Configuration

Configure MCP clients (Claude Desktop, Claude Code, VS Code, Cursor, etc.) to connect to your WordPress MCP servers.

{
  "mcpServers": {
    "wordpress-default": {
      "command": "wp",
      "args": [
        "--path=/path/to/your/wordpress/site",
        "mcp-adapter",
        "serve",
        "--server=mcp-adapter-default-server",
        "--user=admin"
      ]
    },
    "wordpress-custom": {
      "command": "wp",
      "args": [
        "--path=/path/to/your/wordpress/site",
        "mcp-adapter",
        "serve",
        "--server=your-custom-server-id",
        "--user=admin"
      ]
    }
  }
}

{
  "mcpServers": {
    "wordpress-http-default": {
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote@latest"
      ],
      "env": {
        "WP_API_URL": "http://your-site.test/wp-json/mcp/mcp-adapter-default-server",
        "LOG_FILE": "/path/to/logs/mcp-adapter.log",
        "WP_API_USERNAME": "your-username",
        "WP_API_PASSWORD": "your-application-password"
      }
    },
    "wordpress-http-custom": {
      "command": "npx",
      "args": [
        "-y",
        "@automattic/mcp-wordpress-remote@latest"
      ],
      "env": {
        "WP_API_URL": "http://your-site.test/wp-json/your-namespace/your-route",
        "LOG_FILE": "/path/to/logs/mcp-adapter.log",
        "WP_API_USERNAME": "your-username",
        "WP_API_PASSWORD": "your-application-password"
      }
    }
  }
}

Advanced Usage

Creating Custom MCP Servers

For advanced use cases, you can create custom MCP servers with specific configurations:

add_action('mcp_adapter_init', function($adapter) {
    $adapter->create_server(
        'my-server-id',                    // Unique server identifier
        'my-namespace',                    // REST API namespace
        'mcp',                            // REST API route
        'My MCP Server',                  // Server name
        'Description of my server',       // Server description
        'v1.0.0',                        // Server version
        [                                 // Transport methods
            \WP\MCP\Transport\HttpTransport::class,  // Recommended: MCP 2025-06-18 compliant
        ],
        \WP\MCP\Infrastructure\ErrorHandling\ErrorLogMcpErrorHandler::class, // Error handler
        \WP\MCP\Infrastructure\Observability\NullMcpObservabilityHandler::class, // Observability handler
        ['my-plugin/my-ability'],         // Abilities to expose as tools
        [],                              // Resources (optional)
        [],                              // Prompts (optional)
    );
});

Custom Transport Implementation

The MCP Adapter includes production-ready HTTP transports. For specialized requirements like custom authentication, message queues, or enterprise integrations, you can create custom transport protocols.

See the Custom Transports Guide for detailed implementation instructions.

Custom Transport Permissions

The MCP Adapter supports custom authentication logic through transport permission callbacks. Instead of the default is_user_logged_in() check, you can implement custom authentication for your MCP servers.

See the Transport Permissions Guide for detailed authentication patterns.

Custom Error Handler

The MCP Adapter includes a default WordPress-compatible error handler, but you can implement custom error handling to integrate with existing logging systems, monitoring tools, or meet specific requirements.

See the Error Handling Guide for detailed implementation instructions.

Custom Observability Handler

The MCP Adapter includes built-in observability for tracking metrics and events. You can implement custom observability handlers to integrate with monitoring systems, analytics platforms, or performance tracking tools.

See the Observability Guide for detailed metrics tracking and custom handler implementation.

Migration

• Migration Guide: v0.5.0 — Breaking changes and upgrade instructions
• Migration Guide: v0.3.0 — Transport, observability, and hook name changes

License

GPL-2.0-or-later