AI Building Blocks for WordPress  ## Metadata - Author: [[WordPress AI]] - Full Title: AI Building Blocks for WordPress - Category: #articles - Document Note: --- tags: - #AI - #WordPress - #OpenSource Author: WordPress AI Team Source: Make.WordPress.org/AI Reference: July 17, 2025 post date created: 2025-07-17 09:00 --- # Title: AI Building Blocks for WordPress 🚧 ## Table of Contents: - [📝 Summary](#📝-summary) - [📖 Main Content](#📖-main-content) - [🗒️ Notes](#🗒️-notes) - [📖 References](#📖-references) - [🗣️ Paraphrase](#🗣️-paraphrase) - [📰 Newsletter](#📰-newsletter) - [✅ Action Items](#✅-action-items) - [🧪 Hypotheses](#🧪-hypotheses) - [📊 Methodology](#📊-methodology) - [❓ Questions](#❓-questions) - [🔮 Future Research](#🔮-future-research) - [💡 Implications](#💡-implications) - [🧠 Learning Styles Assessment](#🧠-learning-styles-assessment) - [📊 Accessibility Assessment](#📊-accessibility-assessment) - [🌍 DEIB Assessment](#🌍-deib-assessment) - [✅ Logical validity](#✅-logical-validity) ## 📝 Summary: The WordPress AI Team announced four key “building blocks” for AI integration—PHP AI Client SDK, Abilities API, MCP Adapter, and AI Experiments Plugin—with a roadmap toward seamless, provider‑agnostic, extensible, community‑driven AI experiences. :contentReference[oaicite:0]{index=0} ## 📖 Main Content: A dedicated initiative forming foundational tooling for AI in WordPress, aiming for open‑source collaboration, transparent design, and evolving toward core integration. ### 🗒️ Notes - **PHP AI Client SDK** - Unified interface for LLM/embedding providers - Two Composer packages: platform‑agnostic + WP‑specific REST/UI integration :contentReference[oaicite:1]{index=1} - **Abilities API** - Central registry for site capabilities—functions/plugins register abilities with schemas and permissions :contentReference[oaicite:2]{index=2} - Enables systematic discovery by AI or other tools - **MCP Adapter** - Implements Model Context Protocol to expose abilities to external AI assistants :contentReference[oaicite:3]{index=3} - Two‑way comms: WP acts as MCP server/client - **AI Experiments Plugin** - Demo plugin bundling all components into workable AI features: provider switches, capabilities, MCP demos :contentReference[oaicite:4]{index=4} - Roadmap: editor assistants, async commenting, content generation, media management ## 📖 References: - WordPress AI Team “AI Building Blocks” July 17 2025 :contentReference[oaicite:5]{index=5} ## 🗣️ Paraphrase: 1. *Original:* “The PHP AI Client SDK … provider‑agnostic approach puts the user first… users manage their provider credentials in one place.” **Paraphrase:** The SDK lets users pick any AI provider and enter credentials just once, offering plugins a unified, vendor-neutral way to integrate features. 2. *Original:* “The Abilities API … establishes a shared language, enabling all WordPress components to express their capabilities…” **Paraphrase:** The Abilities API creates a universal registry so plugins and themes can describe what they do in a standardized way. ## 📰 Newsletter: Hey folks—Big AI news from WordPress! 🎉 The AI Team dropped four foundational tools: a PHP Client SDK for unified LLM usage, an Abilities API to map plugin power to AI agents, an MCP Adapter for external AI access, and a showcase Experiments plugin. These pave the way for chat assistants in the Block Editor, async AI commenting, auto‑alt text in Media Library, and more. The project is fully open, built on Slack (#core‑ai) and GitHub, and designed to invite contributors—from developers and designers to educators and accessibility pros (that’s you!). Dive in and help shape the future of WordPress AI. Links: - Slack: #core‑ai - GitHub: WP‑AI repos - Read more: “AI Building Blocks” post ## ✅ Action Items: As a Developer Advocate at GoDaddy specializing in open source, community onboarding, and WP education: - Align each building block with open‑source strategy in my talks and workshops - Host contributor hangouts around PHP SDK, Abilities, MCP use cases - Seed open‑call feature‑plugin ideas in WP community - Surface needs for community inclusion, accessibility, DEIB in core AI planning ## 🧪 Hypotheses: - Adoption of Abilities API increases by X% after community workshops - MCP‑powered AI agents reduce WP admin time by Y% - Open‑source contributions improve when canonical plugins support onboarding ## 📊 Methodology: - Metrics from GitHub issues, PR counts, Slack participation - Usability tests with admin tasks vs AI - Surveys across contributor demographics ## ❓ Questions: - How will core merge vs plugin distribution be decided? - What KPIs define AI experiment success? - How will this support multilingual and multicultural sites? ## 🔮 Future Research: - AI‑powered content translation workflows - Role‑based permissions in MCP interactions - Vector RAG integration with WordPress search ## 💡 Implications: - Advances sustainable, provider‑agnostic AI in open‑source WP - Enhances educational tools for plugin developers - Supports inclusive AI features across diverse communities ## 🧠 Learning Styles Assessment: - **Visual:** Minimal visuals; add diagrams and flowcharts - **Aural:** No audio; add podcast or audio summary - **Verbal:** Clear language but could benefit from more analogies - **Physical:** Lacks hands‑on demos; suggest interactive plugin demos - **Logical:** APIs well‑structured; include code flow charts - **Social:** Slack/GitHub invites collaboration—good - **Solitary:** Add self‑reflection prompts on integration planning - **Naturalistic:** No nature analogies; could reference organic community growth ## 📊 Accessibility Assessment: - Likely good HTML structure, but confirm alt text - Provide keyboard‑accessible plugin demos - Use high‑contrast, scalable fonts - Ensure screen reader–friendly docs ## 🌍 DEIB Assessment: - Cultural examples limited—add multicultural use cases - Language is neutral; define jargon - Break long text blocks for neurodiversity - Showcase diverse contributors’ voices ## ✅ Logical validity: - **Sound reasoning:** Clear premises about fragmentation and provider‑agnostic need strengthen argument in SDK section. - **Inductive reasoning:** Observations of redundant plugin credential handling support need. - **Causal reasoning:** Claim that unified SDK → better contributions is plausible. - **No fallacies detected.** --- - Summary: We’re creating technical Building Blocks that will allow users and developers to create powerful AI implementations within WordPress. - URL: https://make.wordpress.org/ai/2025/07/17/ai-building-blocks/ As the open web evolves in the era of AI, WordPress must keep pace. To ensure our CMS remains the leading solution to democratize publishing, we are creating and maintaining a collection of projects that form technical Building Blocks for AI within the WordPress project. These Building Blocks will allow users and developers alike to create powerful AI implementations within WordPress – pushing the CMS to serve more needs and be even more flexible than it already is. We have three immediate focuses and four deliverables. When used together, each contributes the required functionality to create anything from AI features, to workflows, to agents, both inside and outside of the software. Each Building Block is listed below with a short description and a more detailed overview article linked for further reading. The PHP AI Client SDK is an abstraction to interact with LLMs and embedding models from any major provider in a unified way. This allows developers to implement AI-powered features rapidly while giving users the freedom to choose their preferred AI provider and/or model. We’re building this as two distinct Composer packages: a platform-agnostic PHP AI Client SDK developed collaboratively with the wider PHP community, and a WordPress-specific package that adds REST API endpoints, API key management, and other foundational WordPress integrations. This approach ensures broad PHP ecosystem compatibility while providing seamless WordPress experiences. #### [Abilities API](https://make.wordpress.org/ai/2025/07/17/abilities-api) The Abilities API transforms WordPress from a collection of isolated functions into a unified, discoverable system. By creating a central registry of capabilities, it allows AI agents, automation tools, and developers to understand and interact with everything WordPress can do – from CLI commands and REST API endpoints to custom logic and plugin functions. #### [MCP Adapter](https://make.wordpress.org/ai/2025/07/17/mcp-adapter) The MCP (Model Context Protocol) Adapter allows WordPress to connect to AI assistants like Claude and ChatGPT. It builds on the Abilities API to translate selected WordPress server-side abilities into a MCP server that exposes them as tools and resources. Rather than hard-coding support for specific standards, we create Adapters, like this one, that translate between the Abilities API and external protocols. The MCP adapter is our first and most important implementation, positioning WordPress at the forefront of AI integration while maintaining the flexibility to support future standards. The AI Experiments Plugin brings together all the AI Building Blocks into a unified experience. It serves as both a powerful tool for users and a reference implementation for developers, demonstrating how the PHP AI Client SDK, Abilities API, and MCP Adapter work together in practice. Starting as WordPress’s AI laboratory for experimentation, the plugin may evolve into a full-fledged AI Feature Plugin. It can provide an AI playground, WP-CLI integration, intelligent agents, and visual workflow builders – everything needed to explore and implement AI capabilities in WordPress. To avoid early lock-in and maintain flexibility as AI technology rapidly evolves, we will use [Canonical and Feature Plugins](https://make.wordpress.org/core/2022/09/11/canonical-plugins-revisited/) as a way to distribute these features to end consumers, while encapsulating the core functionality and logic of the API projects in Composer packages. This makes it easy for plugin developers to use these official Building Blocks even before they are considered for WordPress Core. It is extremely important that developers can and do use these projects in production, and the approach of using Composer packages is our answer to this – aligning with our “*canonical first, Core when ready*” philosophy. **This work directly overlaps with some of the largest components of the** [**Phase 3: Collaboration**](https://make.wordpress.org/core/2023/03/24/phase-3-collaboration/) **roadmap. It unlocks unique, futuristic** **capabilities** **that can be added through plugins. Here are some examples:** We must plan for these building blocks to be surfaced to end users in this new Site Admin interface. We hope to make it easy for developers to create AI Agents, chatbots, workflow automations and more, using the AI Building Blocks, and surfacing functionality through the new Site Admin UI. A logical and non-disruptive implementation of AI is within the Post Editor, specifically surfacing through Real-Time Collaboration and Commenting. Instead of working with human counterparts, comments could be assigned to AI, which would work to resolve them, creating a suggestion or proposed [revision](https://make.wordpress.org/core/2023/07/05/revisions/). Instead of collaborating in real time with people, why not collaborate with AI? Using AI to create and edit media is becoming increasingly popular. Additionally, there are many smaller implementations that AI could help with: auto alt text and captioning, intelligent grouping, multimodal search capabilities, and more. It’s our intention to craft our projects with the end implementations in mind. By WordPress version 7.0, any WordPress user – enterprise or blogger, developer or designer – should be able to access, use, and build powerful AI features to aid in furthering their digital presence on the open web. Before that, product owners and plugin developers will have a robust toolkit to build AI features into their own offerings, which will work seamlessly with whatever core additions we may make in the future. How this is made available to Core is still an open question, as is much with such fundamental releases on the horizon. Over the next several months, we’ll explore which building blocks and features should be merged to Core or remain canonical. Questions like “should AI providers and content generation be included in Core,” “do we add an AI Agent as a canonical plugin,” and “which protocols should we support” will surface and be addressed in Hallway Hangouts, Make proposals, and [#core-ai](https://wordpress.slack.com/archives/C08TJ8BPULS) discussions. We invite you to join in on the work and discussions. This journey will shape how millions publish and share ideas on the open web, and we can’t do it alone. Join the [#core](https://make.wordpress.org/ai/tag/core/)‑ai channel on WordPress Slack, open Github Issues, or begin contributing to the projects to help us build the next generation of AI tools for WordPress. #### Resources and Repositories ##### Repositories ##### Reference Implementations * [AI Services](https://github.com/felixarntz/ai-services) – Reference for PHP AI Client SDK * [Feature API](https://github.com/Automattic/wp-feature-api) – Reference for Abilities API * [WordPress MCP](https://github.com/Automattic/wordpress-mcp) – Reference for MCP (Server) * [AI Command](https://github.com/mcp-wp/ai-command) – Reference for MCP (Server / Client, WP-CLI) *– The WordPress AI Team: Jeff, Felix, Pascal, James*, AI Building Blocks for WordPress, WordPress AI, 01k0c82jjf8zqcmjsqqm2zkr50.