A documentation release. Four fixes to the WordPress.org listing, one of them silent. No PHP behaviour changes.
The Description was being truncated, and only committers could see it
Every import reported "The Description section is too long and was truncated. A maximum of 2,500 words is supported." That warning is visible only to the plugin's committers, so the public listing had been losing its tail with nothing to say so.
The cause was not where it looked. The Description itself measured about 1,800 words — well inside the limit by every counting method. But WordPress.org folds sections it does not recognise into the Description, and this readme carries two: External Services (465 words) and Privacy Policy (282). Together, 2,583 — over by 83.
Both are required disclosures and are untouched. Trimming a compliance section to satisfy a cosmetic word count would trade a truncated listing for a review problem. The prose was tightened instead, with every point kept and no bullet removed. It now parses at 2,420 of 2,500.
A title that says what the plugin does
It read "AcrossAI Abilities Manager", which tells a search engine nothing. Now:
AcrossAI Abilities Manager – WordPress Abilities for Claude, ChatGPT & Any AI Agent
The name shown inside wp-admin is unchanged — the directory reads the readme, not the plugin header, so lengthening the header would have changed what you see in your plugins list without changing anything anyone searches. Tags move to abilities, ai assistant, chatgpt, claude, mcp.
The plugin's own one-line description is rewritten too. It described "managing and customizing the abilities of AcrossAI … tailoring the AI's capabilities", which is an AI settings panel, not a plugin that ships 357 abilities — and it is the line WordPress prints under the plugin name in wp-admin.
It works with any Abilities API consumer, not just one MCP server
This was one clause at the end of a paragraph about AcrossAI MCP Manager. Read quickly, it sounded like a plugin built for one server that tolerates others. The opposite is true, and it is the stronger claim: every ability here is registered through WordPress 6.9's own Abilities API with show_in_rest, so anything that reads that API can expose all of it.
Three routes are now named rather than implied — AcrossAI MCP Manager, the WordPress MCP Adapter, and any other consumer: another MCP server, a REST client, or a plugin calling the Abilities API directly. MCP Adapter previously appeared nowhere in the description at all.
The listing no longer counts toolsets as this plugin's feature
AcrossAI MCP Manager owns the toolset layer now. Every count of toolsets is gone from the listing; every count of abilities stays, because those are what this plugin ships. The explanation of why an AI sees a dozen tools instead of hundreds survives — it is still the strongest thing the listing says — but now credits the MCP server for the grouping.
The per-plugin toolsets are still described here: Elementor, Rank Math, Site Kit, UpdraftPlus, All-in-One and the rest genuinely do come from this plugin, and MCP Manager deliberately does not carry them.
Nothing about the code changed. The plugin still registers those toolsets exactly as before, and a site running it with MCP Adapter alone still gets them.
Also
Tested up to WordPress 7.1.
Upgrading
Nothing to do. No breaking changes, no behaviour changes, no new settings. If you are on 0.0.39 the only difference you will notice is the plugin's description line in wp-admin.
Full changelog: https://acrossai.co/changelog/acrossai-abilities-manager/
Compare: v0.0.39…v0.0.40