An agent can submit posts into an editorial workflow, sign off or reassign a workflow step, check its own inbox and task counts, build and edit workflow definitions (steps, connections, email templates), bulk-submit or bulk-sign-off posts, and export or import a workflow as a portable JSON template.
View Oasis Workflow on WordPress.org
Oasis Workflow needs WordPress 6.9 or later; no other plugin or setting is required. Each ability checks one of the plugin's own editorial-workflow capabilities (for example ow_submit_to_workflow, ow_sign_off_step, ow_edit_workflow, ow_delete_workflow, ow_create_workflow, ow_abort_workflow, ow_reassign_task, ow_view_workflow_history), so the connected user's WordPress role must have been granted the matching workflow capability.
Grouped by what each one can change. Every one starts off until you enable it.
Lists the workflows a post type can be submitted into.
Reads the first step definition of a workflow.
Lists the tasks assigned to the current user's inbox.
Reads the number of tasks waiting in the inbox.
Reads a post's current workflow status.
Reads the possible next steps after signing off a task.
Lists users who can be assigned to a workflow step.
Reads a post's full workflow history.
Lists every workflow defined on the site.
Reads whether a multi-user step's task has been claimed.
Reads the plugin's global workflow settings.
Lists posts not yet submitted to a workflow.
Submits a post into an editorial workflow.
Signs off the current step and moves a post forward.
Marks a post's workflow as complete (typically publishing it).
Cancels a post's in-progress workflow.
Claims a multi-user assignment step's task.
Reassigns a workflow task to a different user.
Builds a new workflow, including its steps, from a template.
Edits a step's name or configuration in a workflow.
Adds a new step to an existing workflow.
Removes a step from a workflow.
Rewires which steps connect to which in a workflow.
Checks a workflow's step graph for configuration errors.
Permanently deletes a workflow definition.
Copies an existing workflow into a new one.
Reads how many posts have moved through a workflow over time.
Reads how long posts typically sit at each step.
Reads how many open tasks each user currently has.
Reads a summary of recent activity across a workflow.
Reads the notification email templates for a workflow step.
Edits the notification email templates for a workflow step.
Submits several posts into a workflow at once.
Signs off several workflow tasks at once.
Exports a complete workflow definition as a portable JSON template.
Imports a workflow definition from a portable JSON template.
No abilities match that search.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. Oasis Workflow registers its own abilities; this plugin discovers and governs them.
In Agent Abilities for MCP, open the Bridge tab (labeled "Other plugins" in the admin). Abilities from every registered plugin appear there, grouped by the plugin that registered them.
Every ability from Oasis Workflow starts off. Turn on only the ones you want an agent to reach, or enable the whole set in one click.
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.
Yes. All 36 abilities register unconditionally through the core Abilities API with no feature flag, so the Bridge discovers every one of them; none carry an explicit readonly or destructive annotation, so the Bridge's fail-safe rule classifies all of them as destructive.
Yes, unconditionally, once Oasis Workflow is active. Nothing else has to be configured for the Bridge to discover them.
Oasis Workflow needs WordPress 6.9 or later; no other plugin or setting is required. Each ability checks one of the plugin's own editorial-workflow capabilities (for example ow_submit_to_workflow, ow_sign_off_step, ow_edit_workflow, ow_delete_workflow, ow_create_workflow, ow_abort_workflow, ow_reassign_task, ow_view_workflow_history), so the connected user's WordPress role must have been granted the matching workflow capability.
An agent can discover ACF field groups, custom post types, and custom taxonomies that the site owner has opted into AI access, then list, read, create, update, and delete items of those content types along with their custom field values.
An agent can list and inspect tables, charts and media on the site, read the plugin's system info, licence tier and changelog, and create or edit Simple tables and charts, upload images from a URL, and update table, chart, or global plugin settings.
An agent can list, read, create, update and delete docs, doc categories/tags/glossary terms, FAQs and FAQ groups, attach FAQ groups to a doc, read per-doc view analytics, read the plugin's status, and read or update its settings.
Verified from Oasis Workflow's own free wordpress.org code on 28 September 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, nuggetsol or Oasis Workflow. Back to the full directory.
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.