Description
AcrossAI Abilities Manager gives your WordPress site 357 ready-made abilities, and gives you control over every one of them.
An ability is a self-describing operation that WordPress 6.9’s Abilities API lets a plugin register — something an AI assistant, a REST client or another plugin can discover and call. WordPress ships the API; almost nothing ships abilities. This plugin does: 357 on any site, with no configuration, rising to over 800 as it detects the plugins you run.
It is free, GPL, and works on its own. Pair it with an MCP server and your site becomes something Claude, ChatGPT, Cursor or any MCP-capable assistant can operate.
What Your Site Can Do, Out of the Box
- Content — posts, pages and any custom post type with meta and revisions; comments; media, categories and tags; generating an image from a prompt straight into the Media Library (when an AI connector is configured); and semantic search that proposes, reviews and applies internal links.
- Blocks — edit a page’s block tree without rewriting the page, build from patterns, generate sections and landing pages, and audit copy and design.
- Appearance — theme.json and global styles, site-editor templates and parts, menus, widget areas, fonts, and site title, logo and icon.
- Users — create and edit users, reset passwords, create roles, and grant or revoke individual capabilities.
- Configuration — any option including values nested inside serialised arrays, permalinks, and which admin screen a setting lives on.
- Database — schema and table sizes, index health, bloated autoloaded options, EXPLAIN on a slow query, table optimisation, and serialisation-safe search-and-replace.
- Files — browse, read, write and delete inside an administrator-defined allowlist; zip backups; wp-config constants; the debug log.
- Cron — every scheduled task, the overdue ones, running one on demand, and whether WP-Cron is firing at all.
- Updates — plugins, themes and core; rollback; and verification against official checksums.
- Diagnostics — Site Health, maintenance mode, recent fatal errors, and un-pausing what WordPress auto-disabled.
- Cache — transients, object cache and rewrite rules.
A Dozen Tools, Not 357
An AI client is handed its tool list once, at connect time, and pays for it out of the context window on every conversation. Exposing 357 separate tools would flood it — most assistants degrade past a few dozen.
So your MCP server groups them into toolsets, and a toolset is a single tool answering three actions: discover to list what it holds, info to read one ability’s parameters, and execute to run it — the same three everywhere. AcrossAI MCP Manager provides that layer; this plugin provides the abilities.
Plugins You Already Run Get Their Own Toolset
Twenty-one integrations ship with the plugin, each with its own page in the integrations directory — and each registers only when that plugin is active, so nothing appears for software you do not have, and each becomes one more dispatcher tool rather than a pile of loose ones. They are listed on the plugin’s own Integrations screen (under AcrossAI), where a single switch turns any one’s abilities on or off.
- Elementor (89 abilities) — pages, templates, kits, widgets, form submissions and cache; a subset needs Elementor Pro.
- Yoast SEO (64) — titles and meta, indexing, breadcrumbs, schema and social defaults.
- Rank Math (61) — SEO, redirections, schema, analytics and settings.
- LiteSpeed Cache (61) — purge by target, and tune TTLs, exclusions and vary rules.
- WooCommerce (34) — catalogue, prices, stock, orders, customers and store health.
- Contact Form 7 (25) — forms, fields, mail templates, tag validation and messages.
- WPCode (24) — snippets, their insertion points and conditional logic.
- CookieYes (22) — cookies, consent categories, the banner and Consent Mode.
- The Events Calendar (18) — create, reschedule and trash events; venues and organizers.
- Event Tickets (16) — tickets, capacity, check-ins, orders and sales.
- Advanced Custom Fields (16) — field groups, plus post types and taxonomies registered through ACF.
- Site Kit by Google (14) — Search Console, Analytics 4, PageSpeed Insights and AdSense.
- Loco Translate (14) — what is untranslated, and writing translations.
- All-in-One WP Migration (9) — what archives exist, how recent, and exporting or removing them.
- UpdraftPlus (8) — when a backup last ran, whether it worked, and its contents.
- Redirection (8) — create, list, update and delete redirects; the 404 error log that shows which URLs need one; redirect groups; and Redirection’s settings.
- WP Mail SMTP (4) — how the site sends mail, and a real test send.
- Classic Editor (4) — the effective editor per post type, and whether users may choose.
- Query Monitor (4) — profile a URL’s slow and duplicated queries, outbound HTTP calls and PHP errors; the PHP, MySQL and WordPress environment; object-cache status; and turning Query Monitor on or off.
- Akismet — spam figures and checking a comment, from Akismet itself.
- WPForms — read forms and stats, create forms, change settings; writes behind an admin switch, off by default.
The two backup integrations are deliberate exceptions: they register whether or not their plugin is installed, so “is this site backed up?” can be answered “no, there is no backup plugin here” rather than having no tool to answer it.
Third-party developers can register a toolset of their own through a filter, without touching this plugin.
More Integrations With AcrossAI Pro
The paid AcrossAI Pro add-on contributes 276 further abilities through the same toolset mechanism, again only when the host plugin is active:
- MailerPress (89 abilities) (Pro) — campaigns, contacts, lists, tags, templates, workflows and settings.
- LearnDash (74) (Pro) — courses, lessons, quizzes, enrolment, progress, groups and reporting.
- BuddyBoss (60) (Pro) — members, groups, activity, forums, messages, media, connections and moderation.
- MailerPress Pro (28) (Pro) — segments, custom fields, webhooks, embed keys and email templates.
- GeoDirectory (25) (Pro) — listings, locations, fields, pricing packages and directory pages.
Everything else on this page is free.
Nothing Is Wide Open
Every ability runs WordPress’s own capability check for the calling user, so reaching one through this plugin grants nobody anything they could not already do. On top of that:
- Roughly half the catalogue is annotated read-only and only about 13% is flagged destructive, so a look-but-don’t-touch surface is a matter of filtering, not trust.
- Higher-risk operations require an explicit confirmation flag before they run.
- Search-and-replace is a dry run unless you say otherwise, and skips post GUIDs unless asked.
- File access is confined to an administrator-defined path allowlist — an empty write-allowlist means “deny all writes” — with a dangerous-extension blocklist and a maximum write size on top.
- Secrets are redacted — database credentials and authentication salts are stripped out of file and debug-log reads.
- Database abilities never accept a raw table name; they work from a fixed allowlist of core tables.
- Any ability can be disallowed site-wide, and one you turn off is unregistered outright rather than merely hidden.
Full Control Over Every Ability
- Browse all abilities — a searchable, sortable, paginated table listing every registered ability with slug, provider, source and current status.
- Toggle allow/disallow — enable or disable any ability site-wide with a single click, saved instantly without a page reload.
- Edit ability metadata — override
readonly,destructive,idempotent,show_in_rest,show_in_mcp,mcp_typeandmcp_serversper ability with a tri-state Yes / No / Inherit control, and reset any of it to registry defaults in one click. - Bulk actions — allow, disallow or reset up to 50 abilities at once.
- Integrations — a dedicated screen listing every integration on the site, each with a single on/off switch that withdraws this plugin’s abilities for it. Each row shows how many abilities it contributes.
- Ability Library — enable or disable add-on ability groups from a dedicated page, with All/Specific mode per group.
- Add-ons page — browse companion plugins from wp-admin; WordPress.org-hosted ones install and activate in place.
Overrides live in their own table. The ability registry is never modified — only fields that differ from registry defaults are stored, so removing the plugin leaves it exactly as found.
Reproduce a Plugin Conflict Without Breaking the Site
Debugging → Conflict Testing toggles any plugin’s effective active state without ever writing to wp_options.active_plugins — reproduce a conflict for one browser session, then restore the site exactly by clearing a single JSON file.
Seven abilities expose the same thing to REST and AI clients, so an assistant can bisect a conflict for you. Each activation is guarded by a core-style sandbox probe, so a fatal-erroring plugin cannot take the site down — the override is refused instead.
Works With or Without an MCP Server
Abilities are the capability layer, not the connection. Every one is registered through WordPress 6.9’s own Abilities API with show_in_rest, so it is reachable over REST and callable by any plugin the moment you activate this one. Nothing is proprietary or bound to a particular transport, so anything that reads the Abilities API can expose these abilities — there is no lock-in:
- AcrossAI MCP Manager — the free MCP server this plugin is built alongside, turning the toolsets into MCP tools with per-server curation and access control.
- MCP Adapter — exposes registered abilities as MCP tools; when active, this plugin also lists its servers in the ability edit panel.
- Any other consumer — another MCP server, a REST client, or a plugin calling the Abilities API directly. These are ordinary WordPress abilities, not a private format.
Requirements
- WordPress 6.9 or later — the Abilities API arrived in 6.9, and this plugin registers nothing without it
- PHP 8.1 or later
- No other plugin is required
Where To Read More
- The plugin — the plugin home page.
- Every ability, searchable — one page per ability, rather than a list in a readme.
- Integrations — the full integrations directory.
- Use cases — real jobs done through an AI assistant, start to finish.
- Full changelog — the complete history, including releases trimmed from the Changelog here for length.
External Services
Two external connections, each triggered only by a logged-in administrator, and neither sends your site content, user data or ability data. Disclosed per the WordPress.org plugin directory guidelines:
AcrossAI (acrossai.co) — on the AcrossAI → Integrations screen the plugin fetches the list of supported integrations once (a cached GET to https://acrossai.co/wp-json/acrossai/v1/integrations), so the list stays current between releases. No site, user or ability data is sent, and if acrossai.co cannot be reached the screen falls back to a copy bundled with the plugin. AcrossAI admin screens also show images hosted on acrossai.co and link to acrossai.co (the Consultations page links to https://acrossai.co/consultations/); those are contacted by the browser, not the server.
Terms: https://acrossai.co/terms/ · Privacy: https://acrossai.co/privacy-policy/
Google (fonts.googleapis.com, youtube-nocookie.com) — AcrossAI admin screens use Google Fonts, and the optional setup wizard embeds short YouTube walkthrough videos via YouTube’s privacy-enhanced host. Two wizard screens preload a muted clip (so YouTube is contacted when they render); the rest load only when you press play, and every embed is paired with a plain link. No tracking cookies unless a video plays.
Terms: https://policies.google.com/terms · Privacy: https://policies.google.com/privacy
Privacy Policy
This plugin does not itself collect, store, or transmit any personal data.
A few admin-only actions can cause an external service to receive data — all described in the External Services section above, and triggered only by an authenticated administrator:
- Opening AcrossAI → Integrations fetches the supported-integrations list from
acrossai.co(no site, user or ability data is sent). - AcrossAI admin screens load Google Fonts and images hosted on
acrossai.co, which receive standard browser metadata only. The Consultations page’s button opensacrossai.co/consultations/in a new tab. - The optional setup wizard embeds YouTube walkthroughs; YouTube is contacted when a preloaded clip renders or when you press play, and every embed is paired with a plain link.
No data is sent to any external server without an administrator action, and the plugin loads no external script into wp-admin.
Installation
- Upload the
acrossai-abilities-managerfolder to/wp-content/plugins/. - Activate the plugin through the Plugins menu in WordPress.
- Navigate to AcrossAI Abilities Manager in the WordPress admin menu.
Quick Connect setup wizard:
On activation the plugin opens a short setup wizard once — how many abilities the site has, how to
edit them, how to act on many at once, what they cover, and how to connect them to an AI assistant.
It does not open on sites already running AcrossAI MCP Manager, which provides its own wizard.
The wizard is re-runnable at any time and is reachable from four places: AcrossAI → Quick
Connect in the sidebar, the Quick Connect via AcrossAI entry in the admin toolbar, the
Quick Connect via AcrossAI link on the Plugins screen, and a button under Setup on the
AcrossAI → Settings → Abilities tab. Those entries are hidden when AcrossAI MCP Manager is active,
to avoid two wizards competing for the same surfaces; the wizard itself stays reachable at
/wp-admin/admin.php?page=acrossai-abilities-manager&quick-connect=1&step=1.
Add-ons:
- Go to AcrossAI → Add-ons to browse available companion plugins.
- All add-ons are free and hosted on WordPress.org; each card offers a one-click Install / Activate / Deactivate action via the standard WordPress plugin installer.
FAQ
Is this plugin free?
Yes, entirely, and under GPL. There is no paid tier of this plugin and no feature is held back.
What can an AI actually do once this is installed?
357 abilities on any site — content, blocks, appearance, users, configuration, database, files, cron, cache, updates and diagnostics — rising to over 800 as it detects plugins such as WooCommerce, Elementor, Rank Math, Yoast SEO, ACF and LiteSpeed Cache. Abilities are the capability layer; connecting an AI assistant to them needs a transport (see below).
Why does my AI only see about a dozen tools when there are 357 abilities?
That is deliberate, and it is what makes the catalogue usable. Your MCP server groups the abilities into toolsets, and each toolset is a single tool answering three actions — discover to list what it holds, info to read one ability’s parameters, execute to run it. Exposing 357 separate tools would flood the model’s context window, and most assistants degrade badly past a few dozen. Your AI reaches everything through those, drilling in only when it needs to.
Does removing the plugin leave anything behind?
The WordPress ability registry is never modified, so deactivating returns it exactly as it was. Overrides you set live in the plugin’s own table; abilities registered by this plugin simply stop being registered.
Do I need another plugin to use this with an AI assistant?
For an AI client to reach these abilities over MCP, yes — you need an MCP server such as AcrossAI MCP Manager, which is also free. This plugin works perfectly well without one: abilities are registered with show_in_rest, so they remain reachable over the WordPress REST API and callable by any plugin.
Can an AI break my site?
It can only do what you allow. Every ability runs WordPress’s own capability check for the calling user, so nothing here grants extra privilege. Roughly half the catalogue is annotated read-only and only about 13% is flagged destructive; higher-risk operations require an explicit confirmation flag; search-and-replace defaults to a dry run; file access is confined to an administrator-defined path allowlist; and secrets such as database credentials and auth salts are stripped from file and log reads. Any ability you disallow is unregistered outright, not merely hidden.
Does it need WordPress 6.9?
Yes. The Abilities API arrived in WordPress 6.9, and this plugin registers nothing without it — the registration path is guarded, so an older site simply gets no abilities rather than an error.
Does this plugin support Multisite?
No. This plugin has not been tested on WordPress Multisite installations.
Does this plugin modify the WordPress ability registry?
No. The plugin stores only overrides — fields that differ from the registry defaults. The ability registry itself (wp_get_ability()) is never modified.
What happens when I reset an override?
The override row is deleted from the database. The ability will inherit its values from the registry again.
What is the Ability Library?
The Library page lets you enable or disable ability groups registered by add-on plugins. Each group shows an ON/OFF master toggle and an All/Specific mode selector. In Specific mode, individual ability slots can be toggled independently.
What is the MCP Adapter integration?
If the MCP Adapter plugin is active on your site, AcrossAI Abilities Manager will display the list of registered MCP servers in the ability edit panel. This is entirely optional — the plugin works without the MCP Adapter.
Does this plugin make external HTTP requests?
Just one from the plugin’s own code: when an administrator opens AcrossAI → Integrations, it fetches the list of supported integrations from https://acrossai.co/wp-json/acrossai/v1/integrations so the list stays current between releases. It carries no site, user or ability data, is cached, and falls back to a copy bundled with the plugin if acrossai.co can’t be reached.
A few admin screens also load Google Fonts and images from acrossai.co, the setup wizard embeds YouTube walkthroughs, and some buttons link out to acrossai.co and the WordPress.org directory — all contacted by the administrator’s browser, not your server. Full disclosure is in the External Services section of this readme.
Screenshots






Changelog
0.0.45 – 2026-11-10
- Added: put a plugin or theme back on an earlier version — the recovery step this plugin had no answer for. Until now an update could only move forward. Once a plugin was on 4.3.5 there was no route back to 4.3.1, which is the single most common thing you need after an update breaks a site.
versions/rollback-pluginandversions/rollback-thememove an installed plugin or theme onto any version WordPress.org published for it, in either direction, andversions/list-asset-versionstells you which versions those are with the installed one marked. Before touching anything,versions/check-asset-rollbackpre-flights the move and states the two consequences people forget: on a multisite, whether other sites use the asset, and for a theme, whether it is the active one. The previous copy is backed up before the new files land and restored automatically if the package fails to apply — that is WordPress’s own mechanism, not ours. The active theme is refused unless you explicitly force it, because its appearance changes for visitors the moment the files are replaced. None of this needs a third-party plugin. If you do run WP Rollback, its local archive of versions it has installed before is used as well, which is the only way to reach an earlier version of a plugin the directory does not host. - Added: repair a plugin or theme whose files have been changed, without changing its version.
plugins/verify-plugin-checksumscan tell you a plugin’s files no longer match what WordPress.org published for its version — a half-finished update, a truncated upload, an edit someone made directly on the server. Nothing could put them back.plugins/reinstall-pluginandthemes/reinstall-themere-apply that exact version’s official package, leaving the version, your settings and your content alone. A child theme is a separate folder and is untouched; files edited inside the theme’s own folder are what this is for, and they are replaced. An active plugin comes back active, and the swap happens behind maintenance mode so visitors do not hit a half-written plugin. These complete a pair that has been half-open sincecore/reinstall-wp-coreshipped for WordPress itself. - Added: install a specific version instead of only the latest.
plugins/install-pluginandthemes/install-themenow take an optionalversion, which matters when you are reproducing a reported bug or matching the versions on a staging site. It is matched exactly — asking for 4.3 will not quietly give you 4.3.1, because the reason to name a version is usually that one specific version is known to work. A version WordPress.org does not publish is refused and the recent releases are listed, rather than installing something close and reporting success. - Added: hold WordPress core on a chosen version.
core/rollback-wp-coremoves core down once, but WordPress offers the newer version again at the next update check and an automatic update can undo it. With the WP Downgrade plugin active,versions/set-core-pin,versions/get-core-pinandversions/clear-core-pinhold core on a version until you clear the pin. Setting a pin does not move core on its own and says so plainly, because an assistant that reported a downgrade which had not happened would be worse than no answer at all. - Fixed: rolling WordPress core back could destroy a site, and nothing asked you first. Asked for an old enough version,
core/rollback-wp-corewould install it — on a site running PHP 8.4, WordPress 4.7 was reachable and would have been installed. That release predates PHP 7.2 entirely; it fatals on every request including wp-admin, leaving no way back except editing files on the server. WordPress’s own update screen performs a compatibility check before it will offer you a button, but the class underneath does not, and this ability was calling that class directly. The check is now performed, plus one WordPress cannot make: WordPress.org publishes a minimum PHP version per release and no maximum, so a version too old for your PHP passes every published test. That is now refused by name, and the ability requires explicit confirmation like every other destructive operation here. The documentation’s own example version was also one the API no longer offers, so following it failed on the first attempt; an unavailable version now names the one that would have worked. - Fixed: a core version pin could be set but never applied. Setting a pin wrote it, reported success, and told you to run the core update — which then refused, every way round, because WP Downgrade repoints the download without changing the version WordPress reports as available. So the pin was something you could set and read and never use. Applying one now works, and because a pin can move core backwards it goes through the same compatibility refusal and the same confirmation as a rollback. Setting a pin also silently broke
core/reinstall-wp-core, which failed while blaming a stale update cache — not the cause, and refreshing it did not help. Reinstalling now refuses with the real reason and warns that it would have installed the pinned version rather than the one you are running. - Fixed:
plugins/verify-plugin-checksumshad never worked. It was requesting checksums from an address that does not serve them, so the one ability whose job is to tell you whether a plugin’s files have been tampered with could not answer. It now reads WordPress.org’s real plugin checksum manifests. Results also no longer hide a file whose status could not be determined — an unknown file was being counted as a matching one, which is the wrong way round for an integrity check. - Fixed: the Query Monitor page profile reported roughly eight times as many scripts and styles as a page actually loads. It was counting the fields describing each asset rather than the assets, so a page with 23 enqueued files was reported as having 187. Anything reading that number to judge whether a page is heavy was being told something untrue. Measured on two unrelated sites before and after.
- Fixed: two Site Health abilities failed whenever an AI client called them.
site-health/get-site-health-inforeturned an undefined-function error for every request. Loading WordPress’s Site Health class makes the class exist but not the four admin libraries it calls, and those are loaded for you only inside a real wp-admin request — which a REST or MCP call is not. Both abilities now load what they need.site-health/get-site-health-statushad the same defect and had simply not been caught yet: whether it worked depended on which other plugins happened to be active. - Fixed: the toolset dispatchers were missing from the Ability Library. The dispatchers your AI client actually calls were registered but hidden from the list, so the Library showed fewer abilities than the site had and you could not inspect or govern the entries doing the most work. They are now listed, and the All count matches what the list contains.
- Changed: the update and install abilities now point at the ability that can re-version.
plugins/update-pluginonly moves forward andplugins/install-pluginonly installs the latest; both now name the abilities that handle a specific version, so an assistant recovering from a bad update is sent to the thing that can fix it instead of guessing. - Changed: the admin submenu order follows the shared AcrossAI menu. No functional change.
0.0.44 – 2026-11-02
- Added: a Database screen, so you decide what an AI client may do to your data. Until now the database abilities were governed by nothing you could see or set — they either ran or they did not. AcrossAI Settings → Database now carries the controls: an access mode of unrestricted, read-only or off; a denylist of tables nothing may touch; a ceiling on how many rows any one query may return; and a time limit so a heavy query cannot run away with the server. Read-only means exactly that — every write ability refuses with a message naming the setting that stopped it, rather than failing in a way that reads like a bug. Two tables are denied permanently and cannot be allowed from this screen or any other: the one holding password hashes and the one holding session tokens and password-reset keys. A query that reaches either through a subquery, an alias or a join is refused as well, because the tables a statement really touches are resolved by asking MySQL what it parsed rather than by reading the SQL ourselves. The screen lists every table on the site so a denylist entry is chosen rather than typed from memory, and a typo cannot quietly cover nothing.
- Hardened before it shipped: a read-only query that could still write a file, and a row ceiling that only applied if you asked for one. Three problems found by testing the new controls rather than trusting them. The row ceiling was read from the policy only when the caller had already named a limit of its own — which an AI client does not — so a ceiling of two rows returned sixty-three and reported the result as complete; it is now applied to what comes back, so it holds for every database ability whatever it was asked for. A
LIMITanywhere in the statement, including inside a subquery or inside a quoted string, switched the ceiling off entirely; that check now looks only at the end of the statement, and the ceiling no longer depends on it at all. AndSELECT … INTO OUTFILEpassed the read-only check because the statement begins withSELECT, which on some hosts turns a read-only query into writing a file anywhere the database user can reach — bypassing the file manager’s own write allowlist completely. It is now refused by name, reads additionally run inside a read-only database transaction so the server itself rejects a write however it is spelled, and the limits of that transaction are written down rather than assumed. - Fixed: on many managed hosts the file abilities could not see your theme or plugins, and said so in a way that sounded like the file was missing. WordPress does not require
wp-contentto sit inside the WordPress folder, and several large hosts put the two in different places — core in a version-numbered directory, your content somewhere else entirely. Every file ability assumed otherwise. On those siteswp-content/themes/your-theme/functions.phpwas reported as an invalid path, and a listing ofwp-content/pluginsshowed three entries instead of your fifty. Worse, reading a file that happened to exist in both places returned the copy shipped with WordPress and called it a success, with nothing in the answer to say it was not yours — so an assistant could tell you it had read your theme when it had read a stock file. Paths are now resolved against the directories WordPress itself reports, so the documentedwp-content/...form reaches your real content directory on every layout, each answer says which directory it came from, and a path that would land on the unused copy is refused and names both candidates instead of quietly returning the wrong file. The same mistake was making the write allowlist’s shipped default point at the wrong directory — denying writes to your real content folder while permitting them inside WordPress’s own — and leaving your live plugins and themes folders out of the protected list that stops a recursive delete. -
Fixed: asking about a plugin by its folder name was answered with “not installed” for a plugin that was installed.
plugins/get-plugin-lifecycle-contextmatched only the exact plugin file, soacrossai-abilities-managerwas rejected whileacrossai-abilities-manager/acrossai-abilities-manager.phpworked — and it reported the plugin as absent rather than as unrecognised, which is a statement about your site that was simply untrue and sent anything automated off to install a plugin it already had. It now accepts a folder name, a display name, the plugin file or a partial match, exactly as activating and deactivating already did, and an ambiguous name returns the candidates to choose from instead of guessing. A plugin that genuinely is not there now says no plugin was found matching that name. -
Fixed: the backup abilities were missing from every site that had no backup plugin active — which is exactly where they were meant to answer. All seventeen UpdraftPlus and All-in-One WP Migration abilities are registered whether or not those plugins are installed, deliberately, so that
updraftplus/get-statusis there to tell you the site is not backed up. But the family they belong to was only declared when the plugin was detected, and WordPress discards an ability whose family it does not know about — without an error anyone would see. So on those sites all seventeen silently did not exist, and asking “is this site backed up?” got no answer at all rather than a no. The family is now declared unconditionally, matching the abilities themselves. - Added: a twelve-ability All in One SEO suite — the settings AIOSEO itself cannot write. AIOSEO’s own abilities read its settings and say so plainly: “settings cannot be modified via abilities — use the AIOSEO admin UI”, and the tree they hand back is undocumented. So an assistant could describe your SEO configuration and change none of it.
aioseo/get-settings-panelnow returns one named panel — breadcrumbs, webmaster verification, RSS content, search appearance, the four sitemaps, social profiles and cards, SEO alerts, the advanced toggles — with every field’s type, default and current value, andaioseo/update-settings-panelwrites them through AIOSEO’s own sanitiser, so a sitemap change regenerates the sitemap and a permalink change flushes rewrite rules exactly as the admin screens would. A field that does not belong to the panel rejects the whole write rather than applying half of it, and the response reports each field read back after the save, so a value AIOSEO reduced or refused is visible instead of assumed.aioseo/get-object-settingsandaioseo/update-object-settingsreach the other half — the title and description templates, schema type and robots directives that every post of a type or term of a taxonomy inherits — which lives in a second settings store nothing else touches. - Added: AIOSEO sitemap health, and the answer to “it is switched on, why does it 404?”. AIOSEO ships no sitemap ability at all.
aioseo/get-sitemap-healthreports whether the XML sitemap is on, its index URL, which post types and taxonomies are really included, whether the RSS, HTML and llms.txt sitemaps are on, whether AIOSEO is writing static files or building on request, and — unless you turn it off — fetches the index to confirm it is actually served and answers with XML. When something is wrong it names the likely cause rather than handing back a flag.aioseo/regenerate-sitemaprebuilds the static files after a settings change, and on a site that builds on request it says there is nothing to rebuild instead of reporting work it did not do. - Hardened before it shipped: five ways to make an AIOSEO write store nonsense and call it a success. Deliberate hostile testing of the new abilities found that a
nullsitemap page size was stored as zero, a list given where a single value belonged was stored as a list, and — the worst of them — a malformed post id in a bulk edit was quietly rounded to post 1 and written there. Each is now refused with a message naming what was wrong, and nothing is written to any post unless every field passes. None of these were reachable through an AI client, which validates against each ability’s declared schema first; they were reachable by other code on the site calling an ability directly, which is exactly the case an ability should not trust. - Fixed before it shipped: a noindex that was stored and ignored. All in One SEO ignores every per-post robots directive while that post’s “use default settings” switch is on, and neither AIOSEO’s own update ability nor an early version of ours turned it off — so asking to noindex a post stored the flag, reported success, and the page went on telling search engines exactly what it had before.
aioseo/bulk-update-post-seonow turns that switch off when you set a directive and tells you it did, and a directive AIOSEO does not actually store on that path is refused outright instead of succeeding silently. - Added: AIOSEO settings backups, status, bulk post SEO and notification dismissal.
aioseo/create-backup,aioseo/list-backupsandaioseo/manage-backupsnapshot every AIOSEO setting and restore or delete one, which makes a bulk settings change reversible in a single call.aioseo/get-statusreports the version and edition, every addon with whether it is installed, and every settings panel with whether your role may write it — AIOSEO keeps its own role matrix separate from WordPress roles, so this is what explains a refusal before you hit it.aioseo/bulk-update-post-seowrites the same SEO fields across a list of posts, where AIOSEO’s own ability takes one at a time; each post goes through AIOSEO’s own service, so a post you cannot edit is refused individually and reports why, and one failure does not abort the rest.aioseo/dismiss-notificationclears a resolved alert, which AIOSEO can raise and list but not dismiss. - Added: All in One SEO gets its own toolset. AIOSEO ships thirteen abilities of its own — reading and writing one post’s SEO fields, listing posts missing a title or focus keyphrase, listing posts by TruSEO score, the cached site audit, active notifications, and full management of its custom robots.txt rules. Until now this plugin did not recognise them, so all thirteen were filed under “Other”, had no toolset of their own, and an AI assistant asking for the SEO tools could not see them. They now appear together as an All in One SEO toolset and Integrations row, exactly like Rank Math’s and Yoast’s. The toolset description also names the two limits of AIOSEO’s own set up front — its settings read has no write counterpart, and its audit returns the last stored scan rather than a fresh one — so an assistant does not plan work that cannot be done.
- Two of our Rank Math abilities are retired, because Rank Math now ships better versions of them.
rank-math/set-module-stateturned one module on or off; Rank Math’s ownrank-math/set-module-statusdoes several in one call and checks dependencies and PRO availability first, while still refreshing the rewrite rules that a sitemap or llms.txt route needs — the one thing ours existed to guarantee.rank-math/get-seo-analysis-resultsread the stored SEO audit; Rank Math’s ownrank-math/audit-site-seoreads the same stored run when you passrefresh: false, and can re-run it or audit a single URL as well. Where Rank Math covers the ground itself, this plugin now steps back rather than shipping a second, narrower copy. Both replacements are in the same Rank Math toolset, so nothing moves. - Fixed: two Rank Math abilities were taking names Rank Math now uses for its own. Rank Math started shipping abilities of its own, and two of them —
rank-math/get-settingsandrank-math/get-sitemap-status— had the same names as two of ours. WordPress gives a name to whichever plugin registers first, so one side lost its ability outright and a request written for one got the other’s input format, with which side won depending on load order. Ours are renamed torank-math/get-settings-panelandrank-math/get-sitemap-health, so both sets now work side by side and reach the same toolset. The new names also describe them better: one returns a single settings panel together with every field’s type and allowed values, which is what the write abilities need and Rank Math’s own snapshot does not carry; the other is a live health check that catches a sitemap which is configured correctly and still returns a 404. If you call either by its old name, update the name — nothing else about them changed.
0.0.43 – 2026-10-28
- Added: generate an image from a prompt and add it straight to the Media Library. The new
media/generate-imageability takes a text prompt, generates an image through WordPress 7.0’s built-in AI client — using whichever connector the site has configured for image generation — and adds the result to the Media Library in a single call, optionally attaching it to a post and setting it as the featured image. Until now an assistant could store an image it already had, but not make one. Because each call makes a paid AI request, it is gated behind a confirmation; it respects the Upload Media Abilities file-type allowlist, and on a site with no image-capable connector it returns a clear message rather than failing. The Upload Media Abilities settings section and the media abilities now point to it. - Added: manage URL redirects and triage 404s with the Redirection plugin. When the Redirection plugin is active, eight new abilities let an AI assistant create, list, update and delete redirects, read the 404 error log to find the URLs a site is missing redirects for, read the redirect hit log, list redirect groups, and read Redirection’s settings. Every redirect is created through Redirection’s own model — with its URL matching, flags and cache flush — rather than a raw database write that would store a redirect that never fires. Deleting a redirect is irreversible and asks for confirmation, and the REST API token is never returned. It also closes a loop the plugin already opened: deleting a published post hands back a suggested redirect, and there is now an ability that creates it.
- Added: profile any page with Query Monitor, in its own toolset. Four new abilities let an AI assistant profile one URL and read what it actually did — its slow and duplicated database queries, outbound HTTP calls, PHP errors and the template that rendered it — plus the PHP, MySQL and WordPress environment, whether a persistent object cache is connected and its hit ratio, and turning Query Monitor’s own output on or off. They form a dedicated Query Monitor toolset and Integrations row rather than being folded into Diagnostics. Requires the Query Monitor plugin; without it each ability returns a clear “not active” message rather than failing.
0.0.42 – 2026-10-26
- Security: database write abilities can no longer be tricked into altering their own SQL.
database/insert-db-row,database/update-db-rowsanddatabase/delete-db-rowspass column names to$wpdb, which wraps them in backticks without escaping. A crafted column name containing a backtick could break out of that quoting — turning, for example, a targeted delete into a full-table one — and the call still reported success. Column names are now checked against an allowlist ([A-Za-z0-9_]) before any write, and a name outside it is refused with a clear message. Legitimate writes are unaffected. - Fixed: database row writes could corrupt a value and still report success.
$wpdbmatches format specifiers (%s/%d/%f) to columns by position, in the order the data object’s keys happen to arrive — and that order is not dependable once a request has crossed an AI client and the transport. A misaligned%dcast a non-numeric value to0, wrote it, and returned success. Formats are now validated against their values before the write (a numeric specifier on a non-numeric value is refused), and a column-keyed object form is accepted that cannot misalign. - Fixed:
content/update-postsilently dropped plugin meta such as Rank Math’s SEO fields. Updating a post with meta likerank_math_titleorrank_math_descriptiondiscarded it while reporting success, even thoughcontent/create-postandcontent/update-post-metaboth write it. Update now writes those keys, refusing only genuinely-internal underscore-prefixed keys — and when it does refuse one, it says so in a per-key warning naming the key and the ability to use instead, instead of an empty warnings list beside a successful response. - Fixed:
admin-menu/list-admin-menu-pagesthrew on every REST and MCP call. It tried to build the admin menu by loading a core admin script that assumes the admin request lifecycle, which raised a fatal outside it. It now assembles the menu safely and reports when the result is partial (plugin and theme pages only, since WordPress’s own entries are declared by a file that cannot be loaded here) rather than erroring. - Added: Integrations screen. A dedicated screen under AcrossAI listing every integration this site has, each with a single on/off switch. Turning an integration off withdraws this plugin’s abilities for it; a row shows how many abilities it contributes and, when switched off, how many the host plugin still provides on its own.
- Added: use this site’s abilities from Elementor’s MCP server. When Elementor’s MCP server is enabled, a client connected to it can now reach the rest of the site — content, media, the database, files, users and every installed plugin’s capability — through two tools (
toolset-wp-siteand a guide), without leaving Elementor’s editor tools. The pair is host-neutral, built to extend to other hosts’ MCP servers in future. - Added: Elementor’s own abilities without switching on its MCP server. Enabling the Elementor integration registers Elementor’s 27 MCP abilities so they are usable through AcrossAI’s servers, without turning on Elementor’s site-wide MCP exposure — that switch stays the site owner’s to set on Elementor’s own screen.
- Added: diagnostics for ability coverage. New diagnostics report abilities that no toolset lists and abilities that match no grouping rule, and name the plugin that lost a slug collision — so a capability that has quietly fallen out of reach can be found.
Earlier releases
Every release before 0.0.42 is recorded in full at https://acrossai.co/changelog/acrossai-abilities-manager/ and in changelog.txt, shipped inside the plugin.
