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.
Slug Automator abilities, governed through the Bridge
An agent can generate an English URL slug from a post title using AI. That is the only ability this plugin lists.
- Abilities
- 11 destructive
- Active installs
- 100+
- Rating
- 100% (2 ratings)
- Version checked
- 0.6.0
- Requires
- WP 7.0+, PHP 8.2+
- Last updated
- 2026-10-14
- Abilities verified
- 10 November 2026
- Installs and rating as of
- 10 November 2026
View Slug Automator on WordPress.org
What has to be true first
Needs WordPress 7.0 or later (the plugin's own minimum; the Abilities API itself needs 6.9), plus PHP 8.2 or later and the plugin active. The ability checks the capability edit_post.
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 1 Slug Automator ability
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.
Destructive 1
- Destructive
Generate Slug
Generates an English URL slug from a post title using AI.
How to switch these on
Four steps from two active plugins to a governed connection.
Install Slug Automator and Agent Abilities for MCP
Both plugins need to be active on the same WordPress site. Slug Automator 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 Slug Automator 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 Slug Automator work with the Bridge?
Yes. Slug Automator 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.
Do Slug Automator's abilities register automatically?
Yes, once Slug Automator 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 Slug Automator need anything special to work with the Bridge?
Needs WordPress 7.0 or later (the plugin's own minimum; the Abilities API itself needs 6.9), plus PHP 8.2 or later and the plugin active. The ability checks the capability edit_post.
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 Slug Automator's own free wordpress.org code (version 0.6.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, Toro_Unit (Hiroshi Urabe) or Slug Automator. Back to the full directory.
Bridge Slug Automator, 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.