WordPress MCP Adapter: Setup for Claude, Cursor and Other Apps
Turns your self-hosted WordPress site into an MCP server, so Claude or Cursor can use the actions that WordPress, plugins and themes expose.
This is the official WordPress plugin for MCP, part of the AI Building Blocks for WordPress effort. You install it on your site, and it publishes any WordPress ability marked public as something an AI app can use. Abilities are private by default, so the assistant sees nothing until a plugin or theme opts an action in. Connect over WP-CLI on the same machine, or over HTTP at your site's MCP address, using the Automattic proxy if your app needs it.
Good for
- Self-hosted WordPress owners who want an assistant to work with their site
- Plugin and theme developers who want to expose actions to AI apps
- Agencies who manage several sites from one assistant
Works in
12 should work
Tap an app to see how to set it up and any known problems.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Supports local MCP servers.
Client does not support this transport.
Client does not support this transport.
Install WordPress MCP Adapter
Claude Code
- 1
Copy this prompt.
Add the WordPress MCP Adapter server to Claude Code. Run this command: claude mcp add wordpress -- wp --path=/path/to/your/wordpress/site mcp-adapter serve --server=mcp-adapter-default-server --user=admin Then check that it loaded and tell me if I need to sign in or restart.
- 2
Paste it into Claude Code. It shows the change and asks before running it.
Requires WP-CLI, MCP Adapter plugin active on the site.
First install and activate the MCP Adapter plugin on your site (WordPress.org plugin directory: mcp-adapter). Then replace the path with your WordPress folder. --user picks the WordPress user whose permissions apply, so prefer an editor over admin. For a remote site, use the Automattic proxy over HTTP instead; the CLI usage guide shows that config.
From the project README. Source.
Tools
Lists what your site lets the assistant do
Returns every ability on your site that has been marked public. Abilities are private until a plugin or theme opts them in.
Try: “What can you do on my WordPress site?”
Read ·
mcp-adapter-discover-abilitiesShows how one site action works
Fetches the full details and inputs of one ability before the assistant runs it.
Try: “Show me how the create-post ability works.”
Read ·
mcp-adapter-get-ability-infoRuns a site action
Runs one of the public abilities with the inputs you give it. What it can change depends on the abilities your plugins register.
Try: “Run the ability that creates a draft post titled Spring Sale.”
Write ·
mcp-adapter-execute-ability
Read from the source code
Permissions
medium risk · 2 things to watch
Medium risk
The assistant can run every action your plugins have marked public, as the WordPress user it connects as, and those actions can include changes. Run it as a user with a low role, and only mark abilities public that you are happy for an AI to run.
What it can do
- Read your data
- Create and change things
- Delete things
- Read-only mode
Watch out for
It runs site actions as a WordPress user
Run it as an editor or lower, not as an administrator, unless you need more. Without --user the WP-CLI mode runs with limited, unauthenticated access. raw.githubusercontent.com
What it can change depends on your plugins
The adapter itself is a bridge. Review which abilities your plugins mark public before connecting an assistant. raw.githubusercontent.com
Technical details
| Talks to | Your own WordPress site |
|---|---|
| Sign-in and keys | Over WP-CLI there are no stored credentials; you choose the user with --user. Over HTTP you use WordPress application passwords or the proxy's other sign-in options. |
| Scopes |
|
Questions
Is the WordPress MCP Adapter official?
Yes. It lives in the WordPress GitHub organization and the README calls it the official WordPress package for MCP integration. It is also listed on WordPress.org.
Does my assistant see everything on my site?
No. Abilities are private by default. The assistant only sees abilities that a plugin or theme has marked public.
How do I connect Claude Desktop to it?
Point the app at the wp command with WP-CLI for a site on the same machine, or use the Automattic proxy for an HTTP connection. The install box shows the WP-CLI route.
What is the MCP address on my site?
It is /wp-json/mcp/mcp-adapter-default-server added to your site address.
How is it different from the WordPress Remote proxy?
This plugin lives on your site and creates the MCP endpoint. The Remote proxy runs on your computer and connects an app to that endpoint when the app cannot connect directly. You need the plugin either way.
Does it work on WordPress.com?
The README describes a plugin for self-hosted sites. It does not say whether it runs on WordPress.com plans.
Information
updated Nov 1, 2026
- Publisher
- Official
- Transport
- stdio, Streamable HTTP
- License
- GPL-2.0
- Last commit
- Oct 28, 2026
Other WordPress MCP servers
Sources
Docs, issue trackers and discussions this page is built from. Issues, quotes and findings above link to their own source.
Show all 3Hide
- raw.githubusercontent.com · raw.githubusercontent.com
- raw.githubusercontent.com · raw.githubusercontent.com
- raw.githubusercontent.com · raw.githubusercontent.com