MCP-based WordPress plugins ask you to set up a server, a client and credentials before your AI can do anything. RemoteWP is one WordPress plugin: install it, copy your connection prompt, and your AI agent works on the real site.
Free plan for 1 site · 7-day full Pro trial on activation · No credit card
The Model Context Protocol is a solid standard, but connecting it to WordPress is a project of its own. As of October 2026, a typical setup looks like this.
| MCP-based plugins | RemoteWP | |
|---|---|---|
| What you install | A WordPress plugin plus an MCP server, bridge package or hosted connector | One WordPress plugin |
| Where you configure the AI | In each MCP client: config files or connector settings | Nowhere special: you paste one prompt with your site URL and token |
| Which AI tools work | MCP-compatible clients | Any AI agent that can make HTTP requests: Claude, ChatGPT, Gemini, Cursor, Codex |
| WordPress version | Official MCP Adapter: WordPress 6.9 or newer | WordPress 5.8 or newer |
| Before a file changes | Depends on the plugin | Automatic backup of the file, ready to restore |
| Sensitive files | Depends on the plugin | wp-config.php, .env and .htaccess are blocked from writes |
| Sensitive operations | Depends on the plugin | Publishing, plugin changes and settings updates wait for your approval |
MCP setup details as of October 2026. They vary by plugin and AI client.
Four simple steps: install the plugin once, then work from your AI app. Comparing all options? See how to connect AI to WordPress.
If your team already runs several MCP servers in one client and wants WordPress as one more tool there, an MCP-based plugin fits that workflow. If you want your AI agent working on a WordPress site in minutes, without maintaining a protocol layer, RemoteWP is the simpler path. Comparing specific plugins? See RemoteWP vs Easy MCP AI, AI Engine and the WordPress MCP Adapter.
Free read-only access on 1 site, plus a 7-day full Pro trial when you activate your key.