This is part of the AI Building Blocks for WordPress initiative. The main projects are PHP AI Client SDK, Abilities API, MCP Adapter, and the AI Experiments Plugin.
Introduction
Model Context Protocol (MCP) is an open protocol that standardizes how applications provide context to LLMs. In WordPress, the MCP Adapter (GitHub) implements this open standard, exposing Abilities to AI assistants, while also connecting to other MCP servers.
MCP’s applications are transformative for various users. Content creators can manage their WordPress sites conversationally, while developers can automate complex workflows across systems. Agencies can build sophisticated integrations, from content migration to performance optimization.
Consider a typical workflow: an AI assistant receives a request to publish a blog post. Through MCP, it can research topics using external tools, generate content, create images, optimize for SEO, and schedule publication. This entire process happens via natural conversation, respecting permissions and requiring approval when configured.
Two-Way Communication
WordPress can operate as both an MCP server and client, exposing its functionality and connecting to other tools within the MCP ecosystem. This bidirectional functionality allows major AI applications and assistants to discover and directly execute actions on your WordPress site.
As an MCP server, WordPress makes its capabilities registered via the Abilities API available as MCP tools and resources. AI assistants can discover, understand, and execute actions like creating posts, managing media, and moderating comments, all through the standardized protocol.
As an MCP client, WordPress can integrate with other MCP servers. Your site (though an embedded Agent, REST API, WP-CLI, PHP functions…) could leverage AI writing tools for content, specialized services for data analysis, or project management systems, becoming an active participant in a network of interconnected capabilities.
To start, we will focus on building the server side of the MCP Adapter.
Flexible Transport and Security
As an MCP server, WordPress supports the Streamable HTTP transport via the existing REST API as well as the stdio transport via WP-CLI. This ensures compatibility with the wider MCP ecosystem and enables compatibility with local development.
For security, the MCP adapter will leverage the built-in application password mechanism for authentication and the capabilities system for granular authorization. When acting as a MCP Client, we plan for WordPress to implement common user approval controls.
Building for Tomorrow
MCP is a rapidly evolving protocol. The WordPress MCP implementation is designed for adaptability, ensuring it can accommodate future changes and emerging standards. This is achieved through the underlying Abilities API, which represents WordPress functionality in a standard-agnostic way. The MCP adapter translates this functionality into MCP’s format, but other adapters could be developed for different protocols as they emerge.
This approach future-proofs WordPress for an AI-driven world. It allows for quick adaptation to new AI systems and protocols without requiring a restructuring of core functionality.
Getting Started
The MCP Adapter requires the Abilities API to expose WordPress functionality and works seamlessly with the PHP Client SDK and AI Experiments Plugin. Whether you’re connecting your site to AI assistants, building AI-powered applications, or contributing to development, join us in #core-ai on Slack or explore the MCP adapter code.
The future of WordPress is one where sites and AI assistants work together as partners. The MCP Adapter is making that future possible today.