MCP Adapter — WordPress Abilities as MCP Tools (2026)

Main

• The adapter bridges WordPress Abilities to MCP, and the README explicitly maps Abilities to MCP Tools/Resources/Prompts so you can reason about what becomes callable by an agent.
• It supports both HTTP and STDIO transports: the default server is reachable via a REST route, while WP-CLI provides a serve mode for STDIO-style MCP clients.
• For real sites with multiple plugins, it recommends Jetpack Autoloader to avoid Composer dependency conflicts, which is a practical detail most MCP repos skip.
• A clean starting exercise is to register one public ability, then use the adapter discovery tools (discover-abilities, get-ability-info, execute-ability) to validate end-to-end execution.

FAQ

• Do I need WordPress 6.9+?: 6.9+ includes the Abilities API in core; the README notes that WordPress 6.8 requires installing wordpress/abilities-api alongside the adapter.
• How do agents connect?: Use the HTTP endpoint for remote MCP clients, or run the WP-CLI STDIO server if your client expects STDIO transport.
• What should I watch for in production?: Composer version conflicts across plugins; the Jetpack Autoloader recommendation is the default mitigation path.