MCP Adapter for WordPress
MCP Adapter
Official WordPress package that turns Abilities API abilities into MCP tools, resources and prompts
- 1,888 ★ on the repository
- Last commit
- GPL-2.0
Broad access
Why this level
- Performs site actions with the chosen user's rights, up to administrator
- Exposes an HTTP endpoint on the site
Install
- Works in
Manual install
wp mcp-adapter serve --user=adminRuns the stdio server via WP-CLI once the plugin is installed and active.
Access and checks
How we reviewBroad accessThe tool can change data, run commands or handle secrets.
- Performs site actions with the chosen user's rights, up to administrator
- Exposes an HTTP endpoint on the site
This is third-party code. Review the repository files before installing.
What it does
The adapter bridges the WordPress Abilities API with MCP: core, plugin and theme abilities become agent tools. The server is reachable over HTTP at /wp-json/mcp/mcp-adapter-default-server or over stdio through the WP-CLI command wp mcp-adapter serve. Abilities are private by default and exposed with meta.public; the default server offers three meta-tools to discover, describe and execute abilities. Several servers with their own transports and permission checks can run side by side.
Who it is for. For WordPress developers who want to give an agent controlled access to a site or their plugin.
Good fit when
- You want an agent to work with a WordPress site's content and settings
- You build a plugin and want to expose its features to agents via MCP
- You need local access to a development site through WP-CLI
Not a fit when
- The site does not run WordPress
- Your WordPress version lacks the Abilities API
Example request
Show which site abilities are available over MCP and create a draft postMCP
- Transport
- stdio, http
- Authentication
- key is optional
Environment variables
WP_API_URL- Site MCP endpoint URL when using the proxy
WP_API_USERNAME- WordPress username for the proxy
WP_API_PASSWORDsecret- WordPress application password for the proxy
Limitations
Works only inside WordPress with the Abilities API. Abilities must be registered and made public, otherwise the agent cannot see them. HTTP access from stdio-only clients needs the separate @automattic/mcp-wordpress-remote proxy and an application password.
How to disable. Deactivate the MCP Adapter plugin in WordPress and remove the wordpress server from your MCP client config.
FAQ
Why can't the agent see my abilities?
Abilities are private by default. Set meta.public or meta.mcp.public to true when registering.
Which user does the stdio server run as?
The one given in --user. Without it the server runs unauthenticated with limited capabilities.
Discussion
No questions or reviews yet.
Related
MCP serversA Laravel and Lumen package that adds an MCP endpoint to your app's routes and attaches your own tools to it
Laravel MCP
laravel-mcp
The official Laravel package for building MCP servers inside an application: AI clients work with your Laravel project through MCP
Apollo's MCP server: turns chosen GraphQL operations into tools the agent uses to work with your API
mcp-graphql: MCP server for GraphQL APIs
mcp-graphql
Two GraphQL tools for MCP clients: the agent fetches your API schema and runs queries against a single endpoint
Sanity's official agent kit: a remote MCP with project access, skills on content modeling, SEO and migrations, and plugins
A 1C-Bitrix CMS module that turns the website itself into an MCP server exposing infoblocks and the user profile via tokens
README in short
The README presents the adapter as part of the AI Building Blocks for WordPress initiative and lists its features: ability-to-MCP conversion, multiple servers, HTTP and stdio transports, pluggable error handling and permission checks. Details live in the docs: quick start, examples, a CLI guide and migration notes. A WordPress Playground demo is available. Licensed GPL-2.0-or-later.