Host-plugin integrations

10 plugin integrations, 94 governed WordPress MCP abilities.

WooCommerce, ACF, Rank Math, Yoast SEO, AIOSEO, Slim SEO, The Events Calendar, Event Tickets, Avada and GeoDirectory each add abilities to your WordPress MCP server while they are active. When a plugin is not active, its abilities simply are not there. Either way they are off until you enable them, checked against the permissions of the user you connect, and written to the same audit log as everything else.

One card per host plugin.

The counts below sum to the 94 integration abilities. Each set is detected automatically and governed exactly like WordPress core.

WooCommerce52 abilities
Guarded write

products, orders, customers (touches real personal data, gated behind a clear notice)

  • Requires WooCommerce 9.1+
  • Off until enabled
  • Personal data
Advanced Custom Fields7 abilities
Guarded write

read and write ACF field data

  • Requires Advanced Custom Fields
  • Off until enabled
  • Personal data
Rank Math SEO5 abilities
Guarded write

read and manage Rank Math data

  • Requires Rank Math
  • Off until enabled
Yoast SEO3 abilities
Guarded write

read and manage Yoast data

  • Requires Yoast SEO
  • Off until enabled
All in One SEO3 abilities
Guarded write

read and manage AIOSEO data

  • Requires All in One SEO
  • Off until enabled
Slim SEO2 abilities
Guarded write

read and write a post's Slim SEO fields

  • Requires Slim SEO
  • Off until enabled
The Events Calendar13 abilities
Guarded write

events, venues, and organizers, through the calendar's own ORM

  • Requires The Events Calendar 6.17.3.1+
  • Off until enabled
Event Tickets3 abilities
Read only

read tickets and attendees for an event (read only, no purchase write)

  • Requires Event Tickets 5.29.3.1+
  • Off until enabled
  • Personal data
Avada2 abilities
Guarded write

read Fusion Builder markup, and replace text without touching the shortcode tree

  • Requires the Avada theme with Fusion Builder
  • Off until enabled
GeoDirectory4 abilities
Guarded write

read and write business and place listings

  • Requires GeoDirectory
  • Off until enabled
The Integrations tab in wp-admin, with Yoast, Rank Math, All in One SEO and ACF marked Not installed, and WooCommerce marked Active with 0 of 52 abilities on
The Integrations tab. An integration lists its abilities only while the host plugin is active, so the four that are not installed stay collapsed, and WooCommerce sits at 0 of 52 until you switch abilities on. A real screenshot of the plugin admin.

Off until you enable it, personal data flagged first

Activate a supported plugin and its abilities appear, governed the same way as core. Deactivate it and they are gone. Every set stays off until you switch it on. WooCommerce and Advanced Custom Fields can reach real customer records and field data, so they sit behind a clear admin notice before you enable them, and run only for the capabilities of the user you connected.

WooCommerce order abilities on the Integrations tab, filtered to writes, where ordinary writes have a switch while the order update, order status and refund rows carry a HIGH-RISK badge and a padlock instead
The high-risk lock, filtered to WooCommerce order writes. Ordinary writes have a switch you can flip. The ones that move money or change an order carry a HIGH-RISK badge and a padlock, so enabling them is not enough on its own. A real screenshot of the plugin admin.

Built-in integrations, or bridge any other plugin

The 10 sets above (WooCommerce, Advanced Custom Fields, Rank Math SEO, Yoast SEO, All in One SEO, Slim SEO, The Events Calendar, Event Tickets, Avada, GeoDirectory) are integrations we build and maintain. Bridging is different: it exposes abilities that any other active plugin registers on its own, held to the same governance. That set is dynamic and site-specific, so it is not part of the 94 counted here.

See how bridging works

Works with WPML

WPML is not a counted integration here, it adds no abilities of its own. What it changes is the existing content reads: on a WPML site, posts, pages, search, terms, media, products, and single-item reads take an optional language argument and report which language they returned, and a single read can fetch a specific translation. The plugin never translates anything, it only reads what WPML already holds, and sites without WPML are unaffected.

Read how language-aware reads work

Extend the catalog without loosening control.

Activate a supported plugin and its abilities show up, governed the same way. Deactivate it and they are gone. You stay in charge of every switch.

Activate a plugin, the rules do not change. Off by default, gated, logged.