v0.3.5 — new servers get their type’s tools, and no second server is created

Supersedes 0.3.4, which was tagged but never reached a site — WordPress.org holds updates ~6 hours for review, and two problems surfaced inside that window. If you are on 0.3.3, this is the update to take.

What the update does to your site

No database change. Schema stays at 1.1.7. Updating from 0.3.4 touches no column. Updating from 0.3.3 runs one migration, the one 0.3.4 already described: it adds server_type varchar(32) NOT NULL DEFAULT 'mcp-adapter' to {prefix}acrossai_mcp_servers and corrects one row. Nothing is dropped and no data is lost.

No second server is created. 0.3.4 would have added an AcrossAI-branded server at acrossai/mcp to every site. It does not any more — a second MCP endpoint appearing unasked is your decision, and the AcrossAI server type already covers it: create a server and choose that type when you want one. If your site already has that row it is left exactly as it is, still working, and it is now deletable like any other server rather than locked as plugin-managed.

⚠️ One change that can undo an edit, carried over from 0.3.4. The plugin's own server rows are now kept in step on each admin page load: name, description, route, route namespace and version on plugin-managed servers are plugin-owned and get restored if they differ. If you renamed Default MCP Server, or changed its description or route, that change is reverted on update — create your own server instead, where nothing overwrites it. What stays yours: whether a server is enabled, its server type, and every tool and ability selection.

Fixed since 0.3.4

A new server now arrives with its type's tools already selected. Creating a server — from the classic form or the Quick Connect wizard — used to hand it the same three mcp-adapter/* protocol tools whatever type you picked, because that is what the database columns default to. A type's tool set was only ever written when you pressed Reset to Type Defaults. A new MCP Adapter server now includes Server guide from the start, and a new AcrossAI server starts with the AcrossAI toolsets rather than the wrong three.

Existing servers are untouched. Where a type has tools a server does not, the Tools tab still offers them with a one-click Apply, and your own selection is never overwritten.

The Server type control is hidden when there is only one type to choose. With no add-on installed there was nothing to pick, yet the create form and the Tools tab still showed a dropdown whose only other option was unavailable. It returns the moment a second type is installed.

Servers list in the order they were created, with nothing pinned above anything else.

Also in this release (from 0.3.4)

• Server types, and Reset finally restores the right tools. Reset used to restore the same three protocol tools on every server regardless of purpose — on a server meant to serve AcrossAI toolsets that produced the wrong defaults and discarded your selection. New filter acrossai_mcp_server_types lets any plugin contribute a type; see docs/extending-server-types.md.
• Search and pagination for mcp-adapter/discover-abilities, filtering by search, category, namespace or tab_group.
• The Tools tab lists tools and the Abilities tab lists abilities — both screens were showing the wrong set. New filter acrossai_mcp_manager_tool_abilities.
• A connecting AI client is told what this server is, per server type, through MCP initialize.
• The Tools tab says when a change has not reached connected clients yet. An MCP client caches the tool list when it connects and the protocol gives a WordPress server no way to reach one already connected, so the tab says so rather than leaving you with a count that is not yet true for anyone.
• Fixes: the tool exposure gate never fired because the adapter renames tools; an empty tool set fell back to vendor defaults, advertising tools you had removed; the picker offered only the current type's tools.

Compatibility

Requires AcrossAI Abilities Manager 0.0.34 or later for the AcrossAI type's toolsets. Everything else works without it — a server whose type needs the add-on says so plainly and can always be switched to MCP Adapter.

Note on the changelog

The full history now lives in changelog.txt, shipped inside the plugin. WordPress.org truncates a readme's changelog at 5,000 words and had begun cutting this one, so the readme carries recent releases and that file holds the rest.

Full changelog: v0.3.4…v0.3.5