WCUS Prep: MCP Adapter and Abilities API  🔗 **Source:** [WCUS Prep: MCP Adapter and Abilities API](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U) > [!note]+ Document Notes > tags: [Assign relevant tags or keywords to the notee to facilitate organization and retrieval. Add a # before each tag. Tags cannot have special characters. Do not use the tag #articles] > - #wordpress > - #mcp > - #abilitiesapi > - #restapi > - #composer > - #workshop > Author: Jonathan Bossenger > Source: YouTube Livestream (Jonathan Bossenger) > Reference: https://www.youtube.com/watch?v=P2Ti-GZ7Y-U > date created: 2025-08-18 12:48 > > # Title: WCUS Prep — MCP Adapter + Abilities API (WordPress) > <!-- deep-read:sections start --> ## 🧭 Table of Contents: - [📝 Summary](#-summary) - [📖 Main Content](#-main-content) - [🧩 Context & Goals](#-context--goals) - [🛠️ Abilities-API Primer](#️-abilities-api-primer) - [🔌 MCP Adapter & Server Setup](#-mcp-adapter--server-setup) - [🧪 Demo & Troubleshooting](#-demo--troubleshooting) - [🗒️ Notes](#️-notes) - [📖 References](#-references-1) - [🗣️ 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 + Tone](#-logical-validity--tone) - [🛡️ DARVO Analysis](#️-darvo-analysis) - [🔍 SEO Evaluation](#-seo-evaluation) - [🎯 Conclusion](#-conclusion) ### 📚 References: Include a list of sources consulted and cited in the article. - 🎥 Video: https://www.youtube.com/watch?v=P2Ti-GZ7Y-U - 📘 WP REST API Handbook: https://developer.wordpress.org/rest-api/ - 🧩 WP Plugin Handbook (structuring plugins): https://developer.wordpress.org/plugins/ *(External docs for background context; the core facts below cite the video timestamps.)* --- ## 📝 Summary: The livestream previews a **WordCamp US** workshop showing how to connect a local WordPress site to **Model Context Protocol (MCP)** using a new **WordPress MCP Adapter** and the emerging **Abilities API**. Jonathan walks through installing the Abilities API as a plugin, registering a custom ability, spinning up an **MCP server** in a custom plugin, and wiring clients (e.g., VS Code) to call WordPress “abilities” as MCP tools. He covers **Composer** requirements, **application passwords**, **NVM/NPX path gotchas**, and **local SSL** quirks. A working test fetches the first 10 URLs from the local site via the exposed ability. --- ## 📖 Main Content: ### 🧩 Context & Goals - 🔗 **Workshop aim**: connect local WordPress ↔ MCP, showcase **Abilities API** as the registry/executor for actions. ([03:06–05:01](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=186)) - 🆕 **MCP adapter status**: first stable version committed “this week.” ([03:56–04:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=236)) - 🎯 **Session goal**: update existing “List URLs” plugin to the Abilities API and prove MCP end-to-end. ([06:18–07:08](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=378)) ### 🛠️ Abilities-API Primer - 🧠 **Why**: WordPress lacked a structured registry for “abilities” usable by PHP, REST, and AI tooling. ([12:23–13:16](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=743)) - 🧰 **What it provides**: register, list, and **execute** named abilities with **input/output schemas** and **permission callbacks**—plus **built-in REST** routes to run them. ([12:59–14:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=779)) - 🔁 **API shift**: older “Feature API” → new **Abilities API**; use `label`, `description`, `input_schema`, `output_schema`, `execute_callback`, `permission_callback`. No more “type.” ([22:15–23:08](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=1335)) ### 🔌 MCP Adapter & Server Setup - 🧩 **Custom plugin** hosts an **MCP server**: define server ID, namespace, routes; list abilities to expose as MCP tools. ([31:36–33:32](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=1896), [44:40–45:31](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=2680)) - 📦 **Composer** needed when installing via package; manual copy still needs vendor deps (autoload). Include `vendor/autoload.php`. ([47:52–49:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=2872)) - 🔐 **Auth**: use **Application Passwords** for now. ([47:52–48:10](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=2872)) - 🧭 **VS Code config**: workspace `mcp.json` with server command (often `npx`), API URL, username, application password, optional log path. Use **full NPX path** if NVM makes trouble. ([56:31–57:29](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=3391)) ### 🧪 Demo & Troubleshooting - 🧪 **Test**: ask client to fetch “first 10 URLs” via the registered ability; success after giving the server a **clear name** recognizable to the client. ([59:37–61:44](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=3577)) - 🔒 **Local SSL**: add “allow insecure local certs” flag in MCP config when using self-signed dev certs. ([58:38–59:37](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=3518)) - 🔚 **Wrap-up**: next steps include slides and more examples. ([67:00–end](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=4020)) --- ### 🗒️ Notes - 🏁 **Kickoff** ([02:22–03:08](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=142)) - 🎙️ *Context*: Early stream; preparing for **WordCamp US** workshop. - 🧭 *Plan*: Connect local WP → **MCP**, wire **Abilities API**, integrate with editors. - 🆕 **MCP adapter first stable** ([03:56–04:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=236)) - 🚀 *Status*: Committed “this week.” Canonical plugin for WP MCP integration. - 📦 *Access*: Repo available; testing and README fixes underway. - 🧩 **Abilities API rationale** ([12:23–14:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=743)) - 🧠 *Need*: Central registry of capabilities for PHP/REST/AI. - 🧰 *Run via REST*: `/wp-json/wp/v2/abilities` list; “run” endpoint executes callbacks. - 🔐 *Auth*: Requires authenticated user (e.g., Application Passwords). - 🔁 **From Features → Abilities** ([22:15–24:56](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=1335)) - 🧾 *Schema*: `label`, `description`, `input_schema`, `output_schema`, `execute_callback`, `permission_callback`, `meta`. - ✏️ *API diffs*: No “type”; `execute_callback` naming; ordered arrays for readability. - 🔌 **Registering an ability** ([26:01–27:05](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=1561)) - 🛎️ *Hook*: Register on `abilities_api_init`. - 🧪 *Example*: “List URLs” ability accepts `post_type` + `limit`, returns array. - 🧱 **Building the MCP server plugin** ([31:36–33:32](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=1896)) - 🧩 *Plugin header*: Standard WP plugin bootstrap. - ⚙️ *Config*: Server ID, namespace (`ai-experiments`), REST transport, version. - 📦 **Composer vs manual** ([34:55–36:02](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=2095), [47:52–49:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=2872)) - 🧷 *Reality*: Manual copy still needs dependencies → run Composer to build `vendor/`. - 🔗 *Fix*: `require __DIR__.'/vendor/autoload.php';` - 🖥️ **Client configuration (VS Code)** ([56:31–57:29](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=3391)) - 🧭 *mcp.json*: `servers[]` with command, args, env (API URL, username, app password). - 🛣️ *NVM tip*: Use full path to **npx**. - 🧪 *Logging*: Set `LOG_DIR` to plugin path for debugging. - 🔒 **Local SSL tip** ([58:38–59:37](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=3518)) - 🧪 *Flag*: Allow self-signed certs for dev environments in the MCP client config. - ✅ **Working run** ([59:37–61:44](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=3577)) - 🌐 *Request*: “Fetch first 10 URLs.” - 🧭 *Gotcha*: Clear **server name** helps the client resolve the right tools. - 📈 *Outcome*: Tool returns the expected list. - 🧾 **Close** ([67:00–end](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=4020)) - 🧰 *Next*: Slides, more examples; possibly Composer guidance for workshop. --- ## 📖 References: - 🎥 **Primary**: *WCUS Prep: MCP Adapter and Abilities API* — https://www.youtube.com/watch?v=P2Ti-GZ7Y-U - 📘 **Background**: WP REST API — https://developer.wordpress.org/rest-api/ - 📗 **WP Plugins**: https://developer.wordpress.org/plugins/ --- ## 🗣️ Paraphrase: - ✍️ *On the Abilities API purpose* ([12:23–13:16](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=743)) **Original idea**: WordPress needed a structured registry of core abilities usable in PHP and via REST, which AI tools can also call. **Paraphrase**: WordPress lacked a consistent way to declare and invoke capabilities. The Abilities API fills that gap with a single registry, callable from PHP, REST, and AI clients. - ✍️ *On Composer reality* ([47:52–49:13](https://www.youtube.com/watch?v=P2Ti-GZ7Y-U&t=2872)) **Original idea**: Even a “manual” MCP adapter install still requires Composer for dependencies and autoloading. **Paraphrase**: Copying files alone isn’t enough. You still need Composer to pull vendor libraries and include the autoloader for the adapter to work. --- ## 📰 Newsletter: **MCP meets WordPress: editor tools that call your site’s abilities** This week we’re geeking out on **Model Context Protocol** for WordPress. In a fresh WCUS prep stream, Jonathan Bossenger shows how the **Abilities API** lets you register named actions with input/output schemas—then expose them as **MCP tools**. The payoff: your editor (VS Code, Cursor) can run site-specific tasks like “list URLs” safely, with proper auth and REST routes. Expect a few dev quirks (👋 **Composer**, **NVM/NPX paths**, **local SSL flags**), but the flow works end-to-end. Links: Video ▶️ https://www.youtube.com/watch?v=P2Ti-GZ7Y-U • WP REST API 📘 https://developer.wordpress.org/rest-api/ Tip: Start with one small ability (e.g., fetch post slugs) and wire it to MCP before you scale. --- ## ✅ Action Items: - 🧭 **Advocacy framing (for Courtney / OSPO track):** - 🎓 *Education*: Turn this into a hands-on lab for contributors: “Register one ability, expose it via MCP, call it from VS Code.” - 🛡️ *Governance*: Define **permission_callback** standards, app-password policies, and logging defaults for MCP servers. - 📈 *Metrics*: Track “abilities registered,” “MCP tool invocations,” and “mean time to create a secure ability.” - 🔁 *Sustainability*: Publish a **starter plugin template** with Composer scaffolding and scripts; maintainers can fork and ship. - 🌐 *WordPress ecosystem*: Propose a **Training Team module**: “Abilities API 101 + MCP Client Setup.” - 🧭 *OSPO path*: Draft an **internal guideline** mapping abilities to safe scopes (read-only vs mutating), plus review gates. - 🧩 **Reusable prompt for future articles (alignment checklist):** “Extract the article’s concrete **contributor workflows** and map them to: 1) onboarding tasks, 2) governance/permissions, 3) funding or ops time saved, 4) DEIB in docs, 5) OSPO metrics. Then propose a 90-day pilot for WordPress + GoDaddy with clear exit criteria and public progress reporting.” --- ## 🧪 Hypotheses: - 🔬 Adding the Abilities API reduces **custom REST endpoint** code by ≥30% for plugin authors. - 🔒 Projects that adopt **permission_callback** patterns see fewer auth bugs during code review. - 🧰 Teams with a ready MCP server template cut editor-tool integration time by ≥50%. ### 📊 Methodology: - 🧪 **Design**: Before/after repo analysis across 5–10 plugins. - 📈 **Data**: Lines of code for endpoints, PR review comments, time to first successful MCP call. - 🧮 **Analysis**: Diff stats, issue tagging, Wilcoxon test on cycle times. - 🔁 **Reporting**: Public dashboard with anonymized metrics. ### ❓ Questions: - 🧩 Which “ability” categories should be **core examples** (read-only vs write)? - 🔐 What’s the safest default auth for local + cloud editor flows? - 🧰 How can Training Team materials minimize **Composer friction** for newcomers? ### 🔮 Future Research: - ⚙️ Standardize **ability schema** patterns for common WordPress tasks. - 🧪 Explore **token-scoped** alternatives to app passwords for MCP. - ☁️ Package a **hosted** MCP relay for contributors without local SSL. ### 💡 Implications: - 🧑‍🏫 **Education**: Lower barrier to automating site tasks from editors. - 🧱 **Architecture**: Converges PHP, REST, and AI clients on one registry. - 🔒 **Security**: Normalizes permission checks and logging. --- ### 🧠 Learning Styles Assessment: - 📚 **Readability**: Early college. Jargon appears (MCP, schemas, callbacks). - 🖼️ **Visual**: Few visuals. ➕ Add diagrams: “Editor → MCP → WP REST → Ability.” - 🎧 **Aural**: Livestream audio helps auditory learners. ➕ Provide a short audio recap. - ✍️ **Verbal**: Clear narration. ➕ Add glossary for MCP terms. - 🧪 **Kinesthetic**: Strong hands-on coding. ➕ Provide copy-paste starter repo. - 🔢 **Logical**: Step sequences are present. ➕ Include checklists per step. - 🧑‍🤝‍🧑 **Social**: Stream encourages Q&A. ➕ Link to discussion forum/Slack. - 🌱 **Naturalistic**: Not applicable. ➕ Use real-world analogies sparingly. --- ### 📊 Accessibility Assessment: - 🧏 **Screen readers**: YouTube UI is accessible; code on screen needs verbal description. ➕ Add captions (auto + reviewed). - ⌨️ **Keyboard**: YouTube keyboard shortcuts exist. ➕ Provide chapter markers for quick navigation. - 🎨 **Contrast**: Ensure editor theme has high contrast. - 🔎 **Text resizing**: Share code snippets in repo with proper Markdown for zooming. --- ### 🌍 DEIB Assessment: - 🌐 **Cultural relevance**: Topic is global; examples are dev-centric. ➕ Include scenarios from diverse hosting setups. - 🗣️ **Inclusive language**: Neutral. ➕ Define acronyms; avoid insider shorthand. - 🧠 **Neurodiversity**: Linear steps help. ➕ Publish a written step list with checkboxes. - 👥 **Representation**: Single presenter. ➕ Invite community PRs/examples from diverse contributors. - 🛟 **Psychological safety**: Encouraging tone. ➕ Add a code of conduct link for the workshop. --- ### ✅ Logical validity + Tone: - 🧠 **Tone**: Friendly, candid, practical. Light humor; focuses on outcomes. - 🧩 **Sound reasoning**: Shows **cause → effect** (e.g., add autoload → class resolves) with live feedback. - 🔍 **Evidence**: Demonstrates working ability call and REST endpoints. - ⚠️ **Weaknesses**: - *Generality*: Assumes Composer availability; addresses but doesn’t resolve. - *Inference risk*: “Manual install” sounds Composer-free but still needs vendor libs. - 🧭 **Improvements**: Provide an official **no-Composer zip** pre-built for workshops. --- ## 🛡️ DARVO Analysis: - 🙅 **Deny**: None. Presenter openly notes issues (Composer, SSL). - 🗯️ **Attack**: None. No disparaging of critics; only tools/process notes. - 🔄 **Reverse Victim/Offender**: None. No blame shifting. - 🧩 **Conclusion**: No DARVO patterns; communication is transparent and problem-solving. --- ### 🔍 SEO Evaluation: *(YouTube-focused)* - 🔑 **Keywords**: “WordPress MCP,” “Abilities API,” “Model Context Protocol,” “VS Code,” “REST API.” - 🏷️ **Title**: Clear; consider “WCUS Prep: WordPress Abilities API + MCP Adapter (Live Demo)”. - 📝 **Description**: Add step list, repo links, and chapters with timestamps. - 🧱 **Chapters**: Add YouTube chapters matching the timecodes above. - 🔗 **Links**: Include WP docs and any example repo. - 🖼️ **Thumbnail**: High-contrast, readable text (“MCP + WordPress”). - 📱 **Mobile**: Ensure title fits on small screens. - 🗂️ **Schema**: YouTube handles VideoObject; ensure chapters via timestamps. - 📣 **Engagement**: Add pinned comment with commands/config snippets. --- ## 🎯 Conclusion: This WCUS prep stream proves a clean path to wire **WordPress abilities** into **editor tools** via **MCP**. The **Abilities API** centralizes capability registration and execution; the **MCP adapter** exposes them as tools your editor can call. Yes, you’ll wrangle **Composer**, **NPX paths**, and **local SSL**, but the result is powerful: reproducible, permissioned, editor-driven automation for WordPress development. <!-- deep-read:sections end --> [[3. Resources/Readwise/Full Document Contents/Articles/WCUS Prep MCP Adapter and Abilities API|Full Document Contents]] ## Highlights - I’m doing this today and not weeks ago is because the first stable version of the MCP adapter literally was committed this week. ([View Highlight](https://read.readwise.io/read/01k31svrn4j8d8s877ksebhz5w))