Let’s correct something up front: WordPress’s MCP Adapter does not use OAuth. If you’ve read a blog post, a course outline, or a vendor’s marketing page claiming you need to configure an OAuth 2.1 redirect URI for your self-hosted WordPress MCP server, that claim is describing a different product, most likely WordPress.com’s separate, hosted, proprietary MCP offering, not the open-source MCP Adapter plugin this whole track is built on. This course teaches the authentication model that actually ships: WordPress Application Passwords for remote, programmatic MCP clients, and cookie/nonce authentication for logged-in browser sessions. No OAuth flow exists in the adapter itself, and pretending otherwise leads to wasted setup time and, worse, a false sense of the security boundary you’re actually relying on.
Once authentication is correctly understood, the rest of this course builds the layers enterprise and production use actually needs on top of it: how WordPress roles and capabilities govern what an authenticated agent connection can do, how to build dedicated low-privilege accounts and genuinely permission-gated tools, how to keep sensitive data out of an AI agent’s reach in the first place, how to reason about prompt injection from untrusted content, and how to build the audit logging and rate limiting the MCP Adapter and PHP AI Client SDK do not provide out of the box. Every mechanism here is either a real, shipped WordPress or MCP Adapter feature, or an explicitly-labeled custom pattern you build yourself. Nothing in this course is aspirational.
This is Course 4 in the track, and it assumes you’ve already built a working MCP server. If you haven’t, start with Build a WordPress MCP Server From Scratch (Course 2) and Connect AI Assistants to WordPress (Course 3) first. When you’re done here, Course 5, The PHP AI Client SDK for WordPress, picks up the other direction: WordPress calling out to AI models, rather than AI agents calling into WordPress.