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.
Ultimate Multisite abilities, governed through the Bridge
An agent can resolve a tenant site and run authenticated, read-only diagnostics on whether its frontend is available.
- Abilities
- 11 read
- Active installs
- 90+
- Rating
- 100% (12 ratings)
- Version checked
- 2.18.0
- Requires
- WP 5.3+, PHP 8.2+
- Last updated
- 2026-10-28
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
View Ultimate Multisite on WordPress.org
What has to be true first
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 5.3), plus PHP 8.2 or later and the plugin active. The ability checks the capability manage_network.
- Further abilities are registered through loops or helper code, so this list is a floor and their conditions were not checked.
This count can change
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 1 Ultimate Multisite ability
Grouped by what each one can change. Every one starts off until you enable it.
Read 1
- Read
Diagnose site availability
Resolve a tenant site and report authenticated, read-only frontend availability diagnostics.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Ultimate Multisite and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Ultimate Multisite 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 Ultimate Multisite 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 Ultimate Multisite work with the Bridge?
It depends on your setup. Ultimate Multisite calls wp_register_ability() for 1 ability in its current code on wordpress.org, so the Bridge can discover it once the plugin is active. It also registers further abilities through loops or helper code that were not counted here.
What has to be true for Ultimate Multisite's abilities to register?
Further abilities are registered through loops or helper code, so this list is a floor and their conditions were not checked..
Does Ultimate Multisite need anything special to work with the Bridge?
The Abilities API itself needs WordPress 6.9 or later (the plugin lists WordPress 5.3), plus PHP 8.2 or later and the plugin active. The ability checks the capability manage_network.
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 Ultimate Multisite's own free wordpress.org code (version 2.18.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, David Stone or Ultimate Multisite. Back to the full directory.
Bridge Ultimate Multisite, 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.