An agent can list the Orbit Fox modules on a WordPress site, see which ones are active and which settings can be changed, and activate or deactivate a module or change its settings.
Sigmize abilities, governed through the Bridge
An agent can read the Sigmize connection status, cached A/B test experiments, cache stats, and plugin settings. It can trigger a sync from the Sigmize platform, change the SDK loading mode, and disconnect the site, which deletes its auth tokens and cached experiments.
- Abilities
- 85 read2 write1 destructive
- Active installs
- 6K+
- Rating
- 74% (3 ratings)
- Version checked
- 1.2.0
- Requires
- WP 5.8+, PHP 7.4+
- Last updated
- 2026-08-20
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
What has to be true first
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 5.8), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
A note on the count below
Counted from the plugin code on 10 November 2026; settings or feature flags that the count does not evaluate may hide some of these abilities.
The 8 Sigmize abilities
Grouped by what each one can change. Every one starts off until you enable it.
Destructive also covers abilities the plugin does not declare read-only: the Bridge treats a missing annotation as destructive until the owner reviews it, so some of them may only look things up.
Read 5
- Read
Sigmize: Connection Status
Returns the current Sigmize connection status, workspace UUID, connection ID, and last sync time.
- Read
Sigmize: List Experiments
Returns the locally-cached list of A/B testing experiments, optionally filtered by status.
- Read
Sigmize: Get Experiment
Returns a single experiment from the local cache by its UUID.
- Read
Sigmize: Cache Stats
Returns statistics about the local experiments cache, including count and last sync time.
- Read
Sigmize: Get Settings
Returns the current Sigmize plugin settings including SDK loading mode and GDPR configuration. Call this before using update-sdk-mode to check the current state.
Write 2
- Write
Sigmize: Request Sync
Triggers an immediate sync that fetches all experiments from the remote Sigmize SaaS platform and overwrites the local experiment cache. Makes an outbound HTTP request to the Sigmize API. Safe to run multiple times, each run fetches the latest data. Avoid calling this repeatedly in quick succession.
- Write
Sigmize: Update SDK Mode
Enables or disables manual SDK loading mode for the Sigmize snippet. When enabled, the Sigmize JavaScript SDK is not automatically injected into pages, the site owner must load it manually. This directly affects whether A/B tests run on the frontend. Confirm with the user before changing, especially when disabling automatic loading, as it will stop all running experiments from functioning.
Destructive 1
- Destructive
Sigmize: Disconnect
Permanently disconnects the site from the Sigmize SaaS platform, deleting all authentication tokens, cached experiment data, and plugin settings. This cannot be undone, the user will need to reconnect and reconfigure from scratch. Always ask the user to explicitly confirm before running this.
No abilities match that search.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Sigmize and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Sigmize registers its own abilities; this plugin discovers and governs them.
Open the Plugins’ own tools screen
In Agent Abilities for MCP, open the Bridge tab (labeled "Plugins’ own tools" in the admin, "Other plugins" before 1.12.0). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Enable one ability at a time
Every ability from Sigmize starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
Connect as a least-privilege user
Approve the connection as a WordPress account scoped to what you actually want the agent to do. Each call still re-checks that account’s capability before it runs.
Read more in how bridging works or the full documentation.
Frequently asked questions
Does Sigmize work with the Bridge?
Yes. Sigmize calls wp_register_ability() for 8 abilities in its current code on wordpress.org, so the Bridge can discover them once the plugin is active.
Do Sigmize's abilities register automatically?
Yes, once Sigmize is active, as far as its code shows. This directory reads the code but does not evaluate every setting or feature flag, so check the plugin's own settings if an ability is missing on your site.
Does Sigmize need anything special to work with the Bridge?
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 5.8), plus PHP 7.4 or later and the plugin active. The abilities check the capability manage_options.
More Other plugins
An agent can transliterate the existing non-Latin slugs of a scoped batch of posts and terms on a WordPress site into Latin characters. This is a write action that changes the stored slugs.
FluentBoards
ConditionalAn AI agent can list and read boards, stages, and tasks (including a personal task list and a cross-board search), then create, update, move, assign, archive, comment on and label tasks, and manage stages and labels.
Verified from Sigmize's own free wordpress.org code (version 1.2.0) on 10 November 2026, not from its marketing claims. Not every ability listed here has been run end to end against a live site. Plugin authors change their code, so a name, a capability, or a condition can be different in a later release. This site is not affiliated with, or endorsed by, Brainstorm Force or Sigmize. Back to the full directory.
Bridge Sigmize, keep the same control.
Every ability starts off, is scoped to the user you connect, and is written to the same audit log as core. Turn on only what you need.
Off by default. Capability checked on every call.