WordPress learns to speak MCP

What it does

The MCP Adapter exposes WordPress’s internal “Abilities API” as standard MCP tools, resources, and prompts. Any AI agent that speaks the Model Context Protocol can now query what a WordPress site can do and actually do it — create posts, tweak settings, whatever abilities plugins and core have registered. It supports both HTTP and STDIO transport, so it works over the network or locally via WP-CLI.

The interesting bit

WordPress has never had a clean, standardized way for external AI agents to inspect its capabilities at runtime. This adapter treats the CMS like a discoverable service mesh: abilities self-register as typed MCP components, complete with validation, permission checks, and observability hooks. The Jetpack Autoloader recommendation hints at the real target — a WordPress ecosystem where multiple plugins all expose MCP surfaces without version collisions.

Key highlights

• Converts WordPress abilities into MCP tools, resources, and prompts automatically
• Multi-transport: HTTP (spec-compliant to 2025-06-18) and STDIO for CLI/local use
• Pluggable error handling and zero-overhead observability via interfaces
• Granular permission control per transport and server
• Built-in server discovery and introspection abilities
• Requires PHP ≥ 7.4, WordPress ≥ 6.9, plus the php-mcp-schema typed DTO package

Caveats

• The “Abilities API” itself is not explained in the README; it’s unclear whether this is a new WordPress 6.9+ feature or a project-specific abstraction
• README is heavily truncated, so production readiness and edge-case behavior are hard to assess
• The 2025-06-18 MCP spec is referenced but the php-mcp-schema dependency claims 2025-11-25 support — a version mismatch that may or may not matter

Verdict

Worth watching if you run WordPress in an AI-heavy stack or build plugins that need programmatic discovery. Skip it if you’re not already bought into MCP or if your WordPress install is below 6.9.