Linux 软件免费装
Banner图

Webmastery Site Toolkit for MCP

开发者 deboring
更新时间 2026年7月10日 23:44
捐献地址: 去捐款
PHP版本: 8.0 及以上
WordPress版本: 7.0
版权: GPL-2.0+
版权网址: 版权信息

标签

ai automation content-management claude mcp

下载

2.5.0

详情介绍:

Webmastery Site Toolkit for MCP adds 70+ permission-aware abilities across 16 areas that AI agents and MCP clients can call through the official MCP Adapter plugin. It works with popular MCP clients including Claude, ChatGPT, GitHub Copilot, and Gemini. The MCP Adapter provides the transport layer. This plugin provides the site-management vocabulary: posts, pages, media, comments, taxonomy, custom post types, post meta, content hygiene, SEO checks, public webmaster verification, site info, health, security, users, plugins, database, performance, and backup status. Core editorial workflows work well with a dedicated Editor service account. Sensitive workflows such as plugin management, user auditing, site health, database health, backup status, performance status, and security audits require a separate Administrator service account. Highlights: All abilities enforce WordPress capability checks. If the connected account cannot perform the equivalent WordPress action, the ability fails instead of bypassing WordPress permissions. List abilities for posts, pages, custom post types, media, and SEO scores also filter each returned object before exposing full details, so private, trashed, draft, pending, and scheduled content follows WordPress object/status permissions. For full setup instructions, ability tables, and the deeper security model, visit: https://www.virtuallyboring.com/webmastery-site-toolkit-for-mcp/

安装:

  1. Install and activate the MCP Adapter plugin first.
  2. Install Webmastery Site Toolkit for MCP from Plugins > Add New by searching for the plugin name, or upload the plugin zip from Plugins > Add New > Upload Plugin.
  3. Activate Webmastery Site Toolkit for MCP from the WordPress Plugins screen.
  4. Create a dedicated WordPress user for your MCP client. Use Editor for day-to-day content work.
  5. Create an application password for that user from the WordPress user profile screen.
  6. Configure your MCP client with the site endpoint, username, and application password.
  7. Ask your MCP client to call mcp-adapter-discover-abilities and confirm the webmastery-site-toolkit-for-mcp/* abilities appear.

升级注意事项:

2.5.0 Targeted partial-content patches now support pages and eligible custom post types while preserving object-level edit permissions. 2.4.1 Permission hardening reduces low-privilege visibility into private/trash content, runtime versions, and sensitive identity fields. Use Administrator credentials for environment details and plugin management. 2.4.0 Adds expanded Yoast SEO and SEOPress free metadata coverage, including richer social, robots, canonical, breadcrumb, Schema, read-only inspection, and site overview diagnostics. 2.3.0 Adds media URL uploads, webmaster verification checks, content hygiene diagnostics, CPT CRUD, post meta, revisions, comment replies/updates, and Administrator-only site audits. 2.2.0 Adds Yoast score list abilities and supported Yoast protected meta writes. 2.1.0 Adds safer block-level and partial-content editing abilities for MCP clients.

常见问题:

Which AI clients and MCP hosts work with this?

Any MCP client that can reach your site through the MCP Adapter works. This includes Claude (Desktop and Code), ChatGPT, GitHub Copilot, Gemini CLI, Windsurf, and Codex. Most local clients connect through the @automattic/mcp-wordpress-remote bridge.

Does this work without the MCP Adapter plugin?

No. This plugin extends the MCP Adapter plugin and depends on it for MCP transport and ability registration.

Does this work on WordPress.com?

It requires a WordPress site where custom plugins can be installed. Self-hosted WordPress and managed hosts that allow custom plugins should work. WordPress.com Free, Personal, and Premium plans do not allow custom plugin installation.

Which WordPress role should my agent use?

Use a dedicated Editor account for normal content workflows: posts, pages, taxonomy, comments, media, revisions, content blocks, and content hygiene. Use a separate dedicated Administrator account only when you need Administrator-only workflows such as runtime environment details, plugin management, user access audits, site health, database health, performance status, backup status, security audits, or site-wide SEO overview.

Why use a dedicated account?

A dedicated account limits the agent to the role you choose, makes activity easier to attribute, and lets you revoke access by deleting the application password or user.

Do I need Yoast SEO or SEOPress?

No. Structural SEO checks still work without either plugin. Yoast-specific metadata and score abilities require Yoast SEO. SEOPress-specific metadata inspection and writes require SEOPress.

Are write operations safe?

Write operations go through WordPress APIs and capability checks. Posts and pages move to trash rather than being permanently deleted. Media deletion is permanent. Block and partial-content patching can use hashes so stale or ambiguous edits fail safely. Publishing, scheduling, or marking content private requires the relevant WordPress publish capability. User login/email fields and author login names are not exposed to lower-privilege list responses.

What if discovery shows fewer abilities than the documentation?

The connected WordPress site may be running an older plugin version. Update the plugin on that site, then call mcp-adapter-discover-abilities again.

Where is the full documentation?

The complete ability reference and client setup guide are maintained at: https://www.virtuallyboring.com/webmastery-site-toolkit-for-mcp/

更新日志:

2.5.0 2.4.1 2.4.0 2.3.0 2.2.0 2.1.0