by Themeisle
Turns a WordPress site into an MCP server that Claude and ChatGPT can run.
Best for agencies, SEO teams and WooCommerce owners who want an AI assistant to publish and edit WordPress without a middleman service. It replaces copy and paste between a chat and the editor. Approval before destructive actions and a kill switch exist, but each risky tool group needs switching on.
A self-hosted WordPress MCP server with OAuth, per-token permissions, an audit log and change history.
Its edge is breadth, with hundreds of tools across WordPress, WooCommerce, SEO plugins and analytics plus an audit trail, but other MCP plugins can reach the same WordPress REST surface.
Main trade-off
Exposing hundreds of tools to an agent means the safety settings must be configured correctly by the site owner.
The plugin is free on WordPress.org under GPLv2 or later, with no vendor account or usage fee. Third-party SEO and data providers such as Semrush, DataForSEO and Ahrefs are paid separately on your own keys.
wp plugin install easy-mcp-ai --activate
Exposed as MCP tools such as wp_create_post and wp_search_posts at /wp-json/easy-mcp-ai/v1/mcp on your own site, which an AI client calls by name once it is connected through OAuth or an API token.
The permissions this connector asks for, as its own documentation states them.
6 actions an agent can call. Open one for its parameters and an example.
Example call
{"tool": "wp_search_posts", "arguments": {"query": "home office", "per_page": 5, "snippet": true}}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| query | string | Required | The search query string. |
| per_page | integerdefault 10 | Optional | Number of results per page, 1 to 100. |
| page | integerdefault 1 | Optional | Page number for pagination. |
| snippet | booleandefault false | Optional | Include a plain-text excerpt around the first match. |
Returns
| Field | Type | Description |
|---|---|---|
| results | array | Matching items with their type and, when requested, a snippet. |
Example call
{"tool": "wp_get_post", "arguments": {"post_id": 87}}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| post_id | integer | Required | The ID of the post to retrieve. |
Example call
{"tool": "wp_list_posts", "arguments": {"status": "draft", "per_page": 20, "orderby": "date", "order": "desc"}}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| status | string | Optional | Post status to filter by. |
| per_page | integerdefault 10 | Optional | Results per page. |
| page | integerdefault 1 | Optional | Page number. |
| search | string | Optional | Keyword to match. |
| orderby | stringdefault date | Optional | Field to sort by. |
| order | stringdefault desc | Optional | Sort direction. |
Example call
{"tool": "wp_create_post", "arguments": {"title": "Home office setup guide", "content": "<p>Start with the desk.</p>", "status": "draft"}}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| title | string | Optional | The title for the post; required unless allow_empty_title is true. |
| content | string | Optional | The content; HTML is allowed and sanitized. |
| status | stringdefault draft | Optional | publish, draft, pending, private or future (with a date to schedule). |
| categories | array | Optional | Array of category IDs to assign. |
| tag_names | array | Optional | Tag names or slugs; a missing tag is created first. |
| featured_media | integer | Optional | The ID of the featured media attachment. |
| slug | string | Optional | The URL-friendly name for the post. |
Returns
| Field | Type | Description |
|---|---|---|
| post_id | integer | The ID of the created post. |
| status | string | The status the post was saved with. |
| url | string | The post's address on the site. |
Example call
{"tool": "wp_replace_in_post", "arguments": {"id": 87, "field": "post_content", "search": "teh", "replace": "the", "expected_count": 2}}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| id | integer | Required | The post ID. |
| field | string | Required | post_content, post_excerpt or post_title. |
| search | string | Required | The text to find. |
| replace | string | Required | The replacement text. |
| regex | booleandefault false | Optional | Treat search as a regular expression. |
| max_replacements | integerdefault -1 | Optional | Cap on replacements; -1 means unlimited. |
| expected_count | integer | Optional | Refuse the change unless this many matches are found. |
Example call
{"tool": "wp_upload_media_from_url", "arguments": {"url": "https://example.com/desk.jpg", "title": "Standing desk", "alt_text": "A standing desk with two monitors"}}Parameters
| Parameter | Type | Needed | Description |
|---|---|---|---|
| url | string | Optional | A public HTTPS address of the file; local and private addresses are refused. |
| title | string | Optional | Media title. |
| alt_text | string | Optional | Alternative text for the image. |
| post_id | integer | Optional | Attach the file to this post. |
| featured_image | boolean | Optional | Set the image as the post's featured image. |
Easy MCP AI is a WordPress plugin that runs a Model Context Protocol server on the site itself, so Claude, ChatGPT, Cursor and other MCP clients can read and publish content through OAuth or API tokens. It lists 280+ tools in its WordPress.org readme and about 40,000 active installs.
MCP server inside WordPress
Runs as pure PHP on your own site with no Node process or hosted relay, so an AI client connects directly to the site.
OAuth 2.1 and per-token permissions
Each token gets read-only, full or a custom tool set, and every call runs under the capabilities of a real WordPress user.
Audit log and change history
Records each tool call and keeps before and after snapshots of AI edits so a change can be compared or put back.
WooCommerce and SEO plugin tools
47 WooCommerce tools plus tools for Yoast, Rank Math, SEOPress, ACF and The Events Calendar.
Analytics and keyword data
56 tools read Google Analytics 4, Search Console, Semrush, SE Ranking, DataForSEO and Ahrefs data through your own keys.
Safety switches
A kill switch, approval before destructive actions and a Strict Draft mode that stops AI from publishing live content.
Draft and publish from a chat
An agent researches a topic, writes a post, assigns categories and publishes it without the editor being opened.
Bulk SEO field cleanup
An agent reads Yoast or Rank Math titles and descriptions across posts and rewrites the weak ones.
Product catalogue updates
An agent edits WooCommerce products, variations and prices in bulk from a spreadsheet pasted into the conversation.
Traffic questions in plain English
An agent pulls GA4 and Search Console figures into the chat and answers which pages lost traffic.
The nearest AI agent skills on Hokai for the same job.
| Skill | Works with | Connects by | Checked |
|---|---|---|---|
| Claude · ChatGPT · Codex · Cursor +2 | MCP | 22 Nov | |
| -- | MCP | 17 Nov | |
| -- | Skill file | 27 Oct | |
| Claude · ChatGPT · Cursor · Windsurf | MCP | 25 Oct |
The plugin is free on WordPress.org, with no vendor account, relay or usage fee. Only the outside services it reads from cost money: Semrush, SE Ranking, DataForSEO and Ahrefs data tools run on your own paid keys, while Google Analytics and Search Console use your own Google account.
Yes. It is distributed under GPLv2 or later and its source is published in the WordPress.org plugin repository. You install it on your own site, so there is no hosted tier to buy. Three block-building tools call a free cloud service run by the vendor, which a site owner can switch off.
Any client that supports MCP over streamable HTTP. The readme covers the main chat assistants and editor-based agents, from Claude and ChatGPT to Zed and Cline. Clients that only support stdio connect through the mcp-remote bridge, which runs on your own computer rather than on a hosted server.
The usual cause is a missing bearer token or a host that strips the Authorization header. For OAuth, disconnect and approve the connector again. On sites behind Cloudflare Flexible SSL, OAuth sign-in refuses to issue tokens until SSL is set to Full (Strict), while existing API tokens keep working.
Only what the connected user's WordPress role allows, and risky tools can be restricted. An administrator can require approval before destructive actions, disable 39 risky tools, or turn on Strict Draft mode so nothing goes live through an AI client. The change history keeps before and after snapshots so edits can be restored.
Install Easy MCP AI and a WordPress site becomes its own Model Context Protocol server. An AI client such as Claude, ChatGPT or Cursor connects straight to the site and calls tools to create posts, edit pages, update WooCommerce products and set Yoast or Rank Math fields, with nothing in between. Writing happens in the AI client, not in the plugin: an agent invokes the tools, and the person only approves access. WordPress.org lists Themeisle as its author, and the plugin's site names Vertigo Studio S.A. of Bucharest as operator. The plugin entered the WordPress.org directory on 25 March 2026.
On 22 November 2026 the version 2.5.0 zip was downloaded from WordPress.org and its source read: the six actions on this page were written from the input schemas in that code, which holds 384 tool definitions, more than either figure the vendor advertises, though how many a given site exposes was not tested. The server is PHP inside WordPress, reached at a REST route on the site, so no Node process or hosted relay is needed. A client signs in with OAuth 2.1 or presents a bearer API token, and every call runs as a real WordPress user under that user's own capabilities. Read-only, write and destructive tools are labelled, an administrator can switch on approval before destructive actions, and an audit log and change history record what the agent did.
It works with any client that speaks MCP over streamable HTTP, including Claude, ChatGPT, Cursor and Windsurf. Its tool list covers drafting and publishing, bulk SEO field edits, and pulling Search Console or GA4 numbers into a chat. See the wider MCP servers guide and the integration skills list.
It is a poor fit for a site you cannot install plugins on, or a team that wants an agent hosted by someone else: its support runs through the WordPress.org forum, and sensitive tools stay off until an administrator enables them. The wider WordPress rivals, WPVibe, Royal MCP and miniOrange's MCP plugin, are not yet on Hokai. Against the official WordPress MCP Adapter, one tester on its WordPress.org page liked the per-connection OAuth approval better than site-wide application passwords.
The call: install it on a staging copy first if you run WordPress and already use Claude, ChatGPT or Cursor, and keep Strict Draft mode on until you trust it; skip it if your host blocks plugins or you need a hosted service with a support contract.
Protocol, authentication, permissions and the call contracts on this page are read from Themeisle's own documentation. The verdict is Hokai's reading of them, not the maintainer's claim.