Linux 软件免费装
Banner图

Enable Abilities for MCP

开发者 fabiomontenegro1987
更新时间 2026年8月25日 04:49
捐献地址: 去捐款
PHP版本: 8.0 及以上
WordPress版本: 7.0
版权: GPLv2 or later
版权网址: 版权信息

标签

woocommerce ai rest-api content-management mcp

下载

2.0.13 2.0.16 2.0.6 2.0.2 2.0.14 2.0.19 1.9.0 1.9.1 2.1.1 2.0.5 2.0.3 2.0.7 2.0.8 2.0.9 2.0.25 2.2.0 2.2.1 2.3.0 1.6.0 1.7.0 2.0.1 2.0.11 2.0.12 2.0.15 2.0.17 2.0.18 2.0.10 2.0.20 2.0.21 2.0.22 2.0.23 1.9.3 2.0.24 1.8.0 2.1.0 2.5.0 1.9.2 2.0.4 2.4.0 2.5.1

详情介绍:

Enable Abilities for MCP gives you full control over which WordPress Abilities are available to AI assistants through the MCP (Model Context Protocol) Adapter. WordPress 6.9 introduced the Abilities API, allowing external tools to discover and execute actions on your site. This plugin extends that functionality by registering a comprehensive set of content management abilities and providing a simple admin interface to toggle each one on or off. Connect from claude.ai with just a URL Since version 2.1 the plugin ships an embedded OAuth 2.1 server built for claude.ai custom connectors. Add your site in claude.ai → Settings → Connectors, log in with your WordPress user, approve the consent screen — connected. No Client ID, no Application Password, no local configuration. Prefer tokens? Application Passwords (per-user) and a single-admin Bearer token connect Claude Desktop / Claude Code, OpenAI Codex CLI, and Google Antigravity — the Connection tab generates ready-to-paste configuration for each client, and fills in your credentials automatically. Features Available Abilities Read (safe, query-only): Write (create & modify): SEO — Rank Math: SEO — SEOPress: SEO — Yoast SEO: Custom Post Types: WooCommerce: The Events Calendar: Navigation Menus: Tutor LMS: Utility: Requirements

安装:

  1. In your WordPress dashboard, go to Plugins > Add New and search for Enable Abilities for MCP.
  2. Click Install Now, then Activate.
  3. Go to Settings > WP Abilities to manage which abilities are active.
  4. Install and configure the MCP Adapter plugin to connect with AI assistants.

升级注意事项:

2.0.9 Fix: ewpa/update-rankmath-schema was not discoverable by MCP adapters due to an invalid object schema. Update immediately if you use this ability. 2.0.8 New: ewpa/update-rankmath-schema writes Rank Math structured-data schema blocks (FAQPage, Article, Product, etc.) safely as PHP-serialized arrays. Fix: ewpa/update-post-meta now blocks rank_math_schema_* keys to prevent PHP fatal errors. 2.0.6 New: ewpa/get-post-meta reads any single meta field (companion to update-post-meta). New: ewpa_after_update_post_meta action hook lets SEO plugins flush their cache after a write. 2.0.5 Fix: WooCommerce and The Events Calendar abilities were generating PHP notices and not executing correctly due to API key mismatches (name/callback instead of label/execute_callback). Update immediately if WooCommerce or TEC is active. 2.0.4 Tested and confirmed compatible with WordPress 7.0. Fixes an internal version constant mismatch introduced in 2.0.3. 2.0.3 New: SEOPress section (get + update), Yoast SEO section (get + update + sitemap index), Update Post Meta utility ability, and smart SEO plugin auto-detection in get/create/update post abilities. 48 abilities total. 2.0.2 Re-release of 2.0.1 fixes. If your admin tabs still appear as plain buttons after updating to 2.0.1, update to 2.0.2 and purge your Cloudflare or CDN cache. 2.0.1 Fix: activity log now records correctly after file-only updates. Input parameter unified to status across get-posts, get-pages, and get-cpt-items. Uninstall cleanup improved. If you use Cloudflare or a CDN, purge your cache after updating — otherwise the admin interface (tabs, toggle) may show stale assets. 2.0.0 Major update: activity log per user, new three-tab admin interface, Bearer token now optional with toggle, and in-browser credential generator for Application Passwords. No breaking changes — existing Bearer token installs auto-migrated. If you use Cloudflare or a CDN, purge your cache after updating. 1.9.3 New: Update Comment ability (ewpa/update-comment). Change content, author, email, or associated WordPress user of any existing comment. 1.9.2 New: Get Single Page ability (ewpa/get-page). Retrieves full page detail by ID including content, template, parent, and SEO metadata. 1.9.1 Adds formal WooCommerce HPOS compatibility declaration. Resolves the WooCommerce compatibility warning in WP Admin for sites using High-Performance Order Storage. 1.9.0 New WooCommerce (7) and The Events Calendar (4) ability sections. Total 40 abilities. Plus date() timezone fix and zero-error WPCS compliance. 1.8.0 Major update: 8 new Custom Post Type abilities for WooCommerce, ACF, JetEngine, and more. All keys standardized to English with automatic migration. Contextual admin notices for missing dependencies. 1.7.0 MCP Adapter dependency notice, connection example for Claude Desktop, and updated installation instructions for WordPress.org. 1.6.0 New reply to comments ability. Fixed Rank Math focus keyword input for reliable MCP integration. 1.5.0 New API Key authentication. Generate a Bearer token from the admin panel to connect external services like Perplexity via custom MCP connector. 1.4.0 Security and code quality update. Fixes path exposure, SVG uploads, email leaks, and capability levels. Full WPCS compliance. Recommended for all users. 1.3.0 New SEO section with Rank Math metadata read/write abilities. Read and update SEO title, description, focus keywords, robots, Open Graph, and more. 1.2.0 Security update. Adds input validation, per-post capability checks, and sanitization improvements. Recommended for all users.

常见问题:

Do I need anything else for this plugin to work?

Yes. This plugin requires WordPress 6.9+ (which includes the Abilities API) and the MCP Adapter plugin to connect abilities with AI assistants like Claude.

Are all abilities enabled by default?

Yes. On first activation, all abilities are enabled. You can disable any of them from Settings > WP Abilities.

Is it safe to enable write abilities?

Write abilities respect WordPress capabilities. For example, creating a post requires the publish_posts capability, and editing checks per-post permissions. The MCP user must have the appropriate WordPress role.

Does it work on Multisite?

Yes. The plugin can be network-activated. Each site in the network has its own ability configuration, its own OAuth toggle, and its own connector URL — enabling MCP on one subsite never exposes the others. For subdirectory networks (site.com/blog-a, site.com/blog-b) the claude.ai OAuth connector needs the plugin network-activated (or active on the main site): OAuth clients resolve discovery documents against the domain root, which belongs to the main site, so the plugin bridges those requests to the owning subsite automatically.

Does it work with WooCommerce?

Yes. The Custom Post Types section automatically detects WooCommerce products, orders, coupons, and any other registered post type. You can list, create, update, and delete items with full access to WooCommerce meta fields like _price, _sku, _stock_status, _regular_price, and more.

Can I add custom abilities?

This plugin registers abilities using the standard wp_register_ability() API. You can register additional abilities in your own plugin using the wp_abilities_api_init hook.

Another plugin (Fluent Forms, etc.) registers its own MCP abilities — can I control those too?

Yes. Since 2.2, abilities registered by other plugins appear in the Abilities tab under their own "Third-party" section, grouped by plugin namespace, with the same toggles as this plugin's abilities. New third-party abilities start enabled; disabling one unregisters it before any MCP server can expose it — including this plugin's claude.ai OAuth connector and the other plugin's own MCP endpoint. Disabled abilities stay listed so you can re-enable them at any time.

The claude.ai custom connector fails with "Couldn't register with the sign-in service" — why?

In almost every reported case the OAuth flow is fine and the request never reaches WordPress: a security layer in front of your site is blocking Anthropic's backend, which connects with a non-browser User-Agent (python-httpx). Common culprits are hosting WAFs (cPGuard, Imunify360, ModSecurity rules like "generic HTTP client User-Agent") and Cloudflare's Bot Fight Mode or AI-crawler blocking. To diagnose, run curl -A "python-httpx/0.28.1" https://your-site.com/.well-known/oauth-authorization-server from an external machine — a 403 confirms the block. Ask your host to allow that User-Agent (or Anthropic's IP range 160.79.104.0/23) for /.well-known/oauth-*, /oauth/*, and /wp-json/mcp/*, or disable the relevant bot protection for the site.

The OAuth discovery documents return a 301 redirect or 404 — is that a problem?

Yes — strict OAuth clients require a direct 200 on /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. This plugin already prevents WordPress's trailing-slash canonical redirect on those paths and serves the RFC 9728 path-suffixed variants. If they still return 404, your web server is intercepting .well-known/ before WordPress runs (common with Let's Encrypt auto-SSL configs) — see Tools → Site Health for the "MCP OAuth discovery documents" check and ask your host to route those two paths to WordPress.

更新日志:

2.5.1 2.5.0 2.4.0 2.3.0 2.2.1 2.2.0 2.1.1 2.1.0 2.0.25 2.0.24 2.0.23 2.0.22 2.0.21 2.0.20 2.0.19 2.0.18 2.0.17 2.0.16 2.0.15 2.0.14 2.0.13 2.0.12 2.0.11 2.0.10 2.0.9 2.0.8 2.0.7 2.0.6 2.0.5 2.0.4 2.0.3 2.0.2 2.0.1 2.0.0 1.9.3 1.9.2 1.9.1 1.9.0 1.8.0 1.7.0 1.6.0 1.5.0 1.4.0 1.3.0 1.2.0 1.1.0 1.0.0