WordPress (MCP Adapter): Documentation
Updated:
Connection
Install from GitHub Releases, via WP-CLI (wp plugin install), or as a Composer dependency for plugin developers (GPL-2.0-or-later license, 1.5k GitHub stars). STDIO transport works locally through WP-CLI commands; for remote agents there's an HTTP REST endpoint at /wp-json/mcp/ via the @automattic/mcp-wordpress-remote proxy, authenticated with WordPress Application Passwords (Users → Profile → Application Passwords).
Tools
The base server is built around three tools:
mcp-adapter/discover-abilities— lists every Ability registered on the site.mcp-adapter/get-ability-info— parameter schema and description for a given Ability.mcp-adapter/execute-ability— runs an Ability with the supplied arguments.
Any plugin or theme that registers its capabilities through the Abilities API automatically becomes available to an agent — no separate MCP server needed per plugin. When a developer supports it, Abilities are also exposed as MCP Resources and Prompts.
Agent flow
"What abilities are available on this site?", "publish the draft post with ID 42", "upload this image to the media library and insert it into the latest post".
Pricing
The plugin is free; only the WordPress site's own hosting is billed.