An agent can check whether it is allowed to touch a document, read a document's metadata (file type, revision count, lock status), list its revision history, and force-clear another user's edit lock.
View WP Document Revisions on WordPress.org
Needs WordPress 6.9 or later with WP Document Revisions active. Each ability checks its own document capability (edit_documents, read_documents, read_document_revisions, or override_document_lock), so what a connected user can call depends on their document role, not just being logged in.
None of these four abilities carry a readonly annotation in the evidence, so under the Bridge's fail-safe rule (no annotation counts as destructive) all four land in the destructive tier even though most only read data.
Grouped by what each one can change. Every one starts off until you enable it.
Reports whether the current user is logged in, as a basic access check before other document calls.
Retrieves metadata for a document: file type, revision count, and lock status.
Lists the revision history of a document.
Clears the edit lock another user holds on a document so it can be edited again.
Four steps from two active plugins to a governed connection.
Both plugins need to be active on the same WordPress site. WP Document Revisions 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 WP Document Revisions 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. It registers four abilities in the core Abilities API with no meta.mcp.public flag needed, so the Bridge can discover and, once enabled per ability, expose all four.
Yes, unconditionally, once WP Document Revisions is active. Nothing else has to be configured for the Bridge to discover them.
Needs WordPress 6.9 or later with WP Document Revisions active. Each ability checks its own document capability (edit_documents, read_documents, read_document_revisions, or override_document_lock), so what a connected user can call depends on their document role, not just being logged in.
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 WP Document Revisions'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, Ben Balter or WP Document Revisions. 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.