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.
View BetterDocs on WordPress.org
Needs WordPress 6.9 or later. Doc abilities require edit_docs (delete-doc requires delete_docs); term abilities require manage_doc_terms, edit_doc_terms, delete_doc_terms, or edit_docs depending on the operation; FAQ abilities require edit_others_docs; settings abilities require edit_docs_settings; the analytics ability requires read_docs_analytics.
Grouped by what each one can change. Every one starts off until you enable it.
Reads plugin versions, Pro state, content counts, and the current user's capabilities.
Reads a single doc by id or slug, including its content, terms, and view/reaction counts.
Lists and filters docs by search text, category, tag, knowledge base, status, author, or slug.
Lists doc categories or doc tags with their doc counts, parents, and knowledge bases.
Lists FAQ groups with their question counts and published/draft state.
Lists FAQs with their questions, answers, and groups, filterable by group, search text, or status.
Lists every setting the site accepts, with its type, default, and allowed values.
Reads current plugin settings merged with defaults; API keys are masked.
Reads one doc's views, unique views, and reactions, for all time or a date range.
Creates a new doc from markdown, HTML, or block content, with optional categories, tags, and knowledge bases.
Updates an existing doc by id; only the fields sent are changed, and term lists sent replace the doc's current terms.
Creates a doc category or doc tag; an existing name is returned unchanged.
Updates a doc category or doc tag by id; a knowledge_bases value sent replaces the category's current list.
Creates an FAQ group; an existing name is returned unchanged.
Renames an FAQ group or changes its description, slug, or published state; omitted fields keep their current values.
Creates an FAQ (a question and answer), optionally in a group.
Edits an FAQ's question, answer, group, or status; omitted fields keep their current values.
Shows one or more FAQ groups on a doc by writing an FAQ block into its content.
Trashes a doc, or permanently deletes it when force is true.
Permanently deletes a doc category or doc tag; docs in it become uncategorized rather than being deleted.
Deletes an FAQ group; its questions survive without a group unless with_all_faqs is true, which deletes them too.
Deletes an FAQ, which is permanent since FAQs are a custom post type that does not use the trash.
Changes plugin settings; every key is validated before anything is written, and enable_mcp cannot be changed this way.
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. BetterDocs 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 BetterDocs 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 23 free abilities register unconditionally into the core Abilities API (deliberately not gated by the plugin's own enable_mcp toggle), each with an explicit readonly/destructive annotation, so the Bridge discovers and can wrap every one of them.
BetterDocs also ships 13 Pro-only stub abilities under a separate betterdocs-pro/ namespace that register as inert placeholders describing a Pro feature; on a Free site calling one returns an upsell error instead of executing, and Pro replaces them with real abilities of the same id when active. These are not counted among the 23 abilities below..
Needs WordPress 6.9 or later. Doc abilities require edit_docs (delete-doc requires delete_docs); term abilities require manage_doc_terms, edit_doc_terms, delete_doc_terms, or edit_docs depending on the operation; FAQ abilities require edit_others_docs; settings abilities require edit_docs_settings; the analytics ability requires read_docs_analytics.
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 read and set whether the featured image is hidden on a post's singular view, do that in bulk across a list of posts, and check which public post types the plugin is currently enabled on.
Verified from BetterDocs'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, WPDeveloper or BetterDocs. 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.