AI 조수가 MCP를 통해 WordPress 사이트를 편집 할 수 있습니다.

까지 테스트: 7.0 ** 안정되어 있는 꼬리표: ** 3.0.84 ** 면허: ** GPLv2 이상 ** 면허:** https://www.gnu.org/licenses/gpl-2.0.html

그것은 무엇을

이 플러그인은 MCP (Model Context Protocol)을 통해 WordPress 기능을 노출하여 AI Assistant를 사용하여 WordPress 사이트와 직접 상호 작용합니다. 채팅과 관리자 사이에 더 많은 복사가 없습니다.

Example : “이 25 기사에서 전화 번호를 클릭 할 수 있습니다 클릭 가능한 tel : 링크.” - 30 초 만에 완료, 모든 25 기사.

실제 작업 흐름

실습에서 인간은 전체적인 생태계를 기억해야 한다.

정상적인 본은:

1. 이 저장소에 점 Codex 또는 다른 MCP-capable 대리인
2. 에이전트는 README 및 위키를 읽습니다.
3. 대리인은 필수 더미 및 관련 add-ons를 실행합니다
4. 대리인에게 경계를 가진 명확한 일을 줍니다

인간의 일은 대부분 목표를 설명하는 것입니다. 대리인의 일은 기계학을 알아내는 것입니다.

왜이 다른 느낌

대부분의 WordPress AI 데모는 여전히 지루한 부분을 직접두고 있습니다.

이 생태계는 에이전트가 실제로 WordPress 내부 작업을 수행 할 수 있기 때문에 다릅니다

MCP Expose Abilities

Let AI assistants edit your WordPress site via MCP.

Tested up to: 7.0 Stable tag: 3.0.84 License: GPLv2 or later License URI: https://www.gnu.org/licenses/gpl-2.0.html

What It Does

This plugin exposes WordPress functionality through MCP (Model Context Protocol), enabling AI assistants to directly interact with your WordPress site. No more copy-pasting between chat and admin.

Example: “Fix the phone numbers in these 25 articles to be clickable tel: links.” - Done in 30 seconds, all 25 articles.

The Real Workflow

In practice, the human should not have to memorize the whole ecosystem.

The normal pattern is:

1. point Codex or another MCP-capable agent to this repository
2. let the agent read the README and wiki
3. let the agent work out the required stack and relevant add-ons
4. give the agent a clear task with boundaries

The human’s job is mostly to describe the goal. The agent’s job is to figure out the mechanics.

Why This Feels Different

Most WordPress AI demos still leave you doing the boring part yourself.

This ecosystem is different because the agent can actually do the work inside WordPress:

• fix repetitive content issues across many pages
• update menus, media, plugins, comments, and options
• work with real builder and plugin ecosystems like Elementor, GeneratePress, Rank Math, and Wordfence
• handle the kind of site maintenance people usually postpone because it is repetitive and dull

That changes the experience from:

• Here is what you should do in wp-admin

to:

• Tell the agent what needs doing, and let it carry out the work

Before vs After

Before

• ask the AI what to do
• copy the answer into WordPress by hand
• click through wp-admin for the repetitive bits
• lose momentum because the task is boring
• postpone the cleanup, maintenance, or optimization work again

After

• tell the agent what needs doing
• let it inspect the site directly
• let it make the targeted change
• verify the result
• move on to the next useful improvement instead of getting stuck in admin drudgery

That difference is the whole point of this ecosystem.

Who It Is For

This is a good fit for:

• agencies managing many WordPress sites
• companies with repetitive content and operations work
• organizations that want AI to do real maintenance, not just generate text
• technical teams that are tired of copy-paste workflows between chat and wp-admin

It is especially useful when work gets postponed simply because the manual version is boring.