AcrossAI MCP Manager

Ändringslogg

0.2.4

• Dependencies — bump wpboilerplate/wpb-access-control 2.0.0 → 3.1.0. Two vendor changes surface in the per-server Access Control tab (?tab=access-control): (1) new ”Any logged-in user” option in the Who can access dropdown — backed by the new TYPE_AUTHENTICATED sentinel in AccessControlManager (returns true iff $user_id > 0), and (2) the existing ”Everyone (no restriction)” option is relabelled ”Public (no login required)” — pure UI relabel, same underlying behavior (TYPE_EVERYONE unchanged, existing rules unaffected). v3.0.0 also removed the built-in BuddyBossProfileTypeProvider + MemberPressMembershipProvider (moved to a separate acrossai/user-access-pro add-on); this plugin never wired them into the Who can access dropdown, so removal has no visible effect here. Docblock at includes/Main.php refreshed to drop the stale BuddyBoss/MemberPress reference. No data migration required.
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant + Stable tag bumped to 0.2.4 matching the plugin header.

0.2.3

• UX — In-context nudges to install the AcrossAI Abilities Manager add-on. When the sibling acrossai-abilities-manager plugin is not active, the server-edit Abilities and Tools tabs (?tab=abilities / ?tab=tools) now surface a small WordPress-native notice-info block above the picker with a link to the shared Add-ons page (admin.php?page=acrossai-addons). Without the add-on both pickers only list the three core abilities WordPress ships by default (core/get-environment-info, core/get-site-info, core/get-user-info); the add-on registers a rich library of built-in abilities that populate both surfaces. Detection is a plain is_plugin_active() check — same message + same link covers both ”not installed” and ”installed-but-off” states. Placed after the existing ”Server is disabled” warning and before the wp_get_abilities() capability check, so the nudge is visible even when the abilities API itself is missing.
• UI — AcrossAI brand logo on the AI Connectors placeholder tab. Replaces the hand-rolled interconnected-nodes SVG on the AI Connectors placeholder promo (?tab=ai-connectors when the acrossai-ai-connectors companion is missing / inactive) with the same brand SVG the vendor uses on the shared Add-ons page (https://acrossai.co/wp-content/uploads/2026/07/acrossai-logo-2.svg). New LOGO_URL class constant on AIConnectorsPromoTab; icon markup swapped from an inline <svg> inside a gradient tile to a plain <img alt="AcrossAI"> tag; deleted the private render_network_svg() method (dead code). CSS: dropped .acai-aic-promo__icon (gradient background + colored SVG) in favor of .acai-aic-promo__logo (height: 48px; max-width: 180px; object-fit: contain) so the brand mark sits cleanly without a decorative background box.
• Refactor — Renamed the ”MCP Tracker” tab to ”Logs”. The per-server tab formerly reached at ?tab=mcp-tracker is now ?tab=mcp-log, and the tab-bar label reads Logs instead of MCP Tracker. Priority slot 80 preserved so the tab-bar ordering is unchanged. Class name McpTrackerTab kept (internal identifier) along with the body copy that identifies the third-party MCP Tracker plugin on WordPress.org (WPVMCPT) product name — those aren’t the tab label, they’re a specific product reference. Deep links to the old ?tab=mcp-tracker fall through to Registry’s ”first surviving tab” default (Overview) rather than 404. Test fixture updated: five 'mcp-tracker' occurrences in RegistryTest.php migrated to 'mcp-log'.
• Docs — Rewrote README.txt as a lean docs-hub pointer. The plugin’s WordPress.org readme now defers to acrossai.co/doc-category/mcp-manager as the source of truth for every feature description — copy lives in one place instead of drifting between two. Description condensed to a two-line multi-client pitch; Key Features reshaped to reflect the current feature set (multiple servers per site, per-server tool/ability curation, per-server access control, frontend embeds, CLI + WP-CLI STDIO transports) with each bullet linking to its docs page; How It Works trimmed to the 6-step get-started path; new Connection Types section calls out the four supported paths (MCP Client, CLI Connections, WP-CLI STDIO, and the paid AI Connectors add-on); Requirements bumped to WordPress 7.0+ / PHP 8.1+ (matches the plugin header — old readme had drifted to 5.9 / 7.4); FAQ trimmed from 7 questions to 5 with a new ”Do I need the paid AI Connectors add-on?” entry; new Support section links to docs hub, FAQ page, and GitHub issue tracker. Header tags expanded (chatgpt, cursor, gemini added). Deleted the stale post-F040 Experimental Direct Claude Connectors section, the CLI-flow deep dive, and the Provider Configuration Paths list — those live in the docs now.
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant + Stable tag bumped to 0.2.3 matching the plugin header.

0.2.2

• Notices — migrated persistent-condition banners to the cross-plugin acrossai_notices filter. The ”MCP adapter package missing” and ”wpb-access-control library missing” warnings no longer render as inline admin_notices banners on every screen. They’re pushed into the shared collection introduced in acrossai-co/main-menu 0.0.30, which surfaces them in two consolidated places: (1) a Notices submenu under the AcrossAI parent menu (with a count bubble; the page also stays reachable when the count is zero and renders an ”All clear” empty state per the 0.0.31 fix) and (2) a single WP-native dismissible summary on every other admin page. Dismissal is now fingerprint-based (per-user meta _acrossai_notices_summary_fp) — adding, resolving, or renaming a notice re-shows the summary automatically. Deletions: Notices::render_missing_adapter_notice, Notices::handle_adapter_notice_dismissal, ADAPTER_DISMISS_META_KEY, ADAPTER_DISMISS_NONCE_ACTION, AcrossAI_MCP_Access_Control::maybe_show_library_notice, and the US4 dismiss-persistence handler in src/js/backend.js — all obsoleted by the shared summary. Additions: Notices::register_shared_notices() returns records with ids acrossai_mcp_manager_adapter_missing (type error) and acrossai_mcp_manager_wpb_access_control_missing (type warning), both scoped with source: 'MCP Manager'. One-shot action-result flashes (?notice=<slug>) stay on the standard admin_notices hook — page-scoped transient messages don’t fit the shared collection model.
• UI — Redesigned the AI Connectors placeholder tab as a centered sales card. When the acrossai-ai-connectors companion add-on is not installed or not active, the AI Connectors tab on the server-edit page (?page=acrossai_mcp_manager&action=edit&server=<id>&tab=ai-connectors) now renders a vertically-centered polished card sourced from https://acrossai.co/ai-connectors/ — headline (”Connect WordPress to Claude, ChatGPT & Grok in one click”), supported-client pills (Claude · ChatGPT · Grok), four benefit bullets, a purple CTA (”Install add-on” / ”Activate add-on” depending on companion state), a ”Learn more” link, and a 14-day money-back trust line. State resolution unchanged — Registry’s last-wins dedup at priority 35 still swaps the placeholder out for the companion’s real AIConnectorsTab the moment the add-on activates.
• Dependencies: bump acrossai-co/main-menu 0.0.29 → 0.0.31. 0.0.30 shipped the shared acrossai_notices filter + Notices submenu + SummaryNoticeEmitter. 0.0.31 fixed a ”Sorry, you are not allowed to access this page.” error on direct visits to admin.php?page=acrossai-notices when the notice count was zero (page callback is now always wired; empty-state sidebar row is hidden via inline <style> on admin_head rather than remove_submenu_page(), which had desynced $_registered_pages).
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant + Stable tag bumped to 0.2.2 matching the plugin header (backfills the Stable tag drift that persisted since 0.2.0).

0.2.1

• Security — Defended REST + AJAX response paths against full-page cache poisoning. Full-page caches (LiteSpeed Cache, WP Rocket, W3 Total Cache, WP Super Cache, host-level FastCGI cache) don’t honor arbitrary Cache-Control: no-store headers when making caching decisions — they gate on DONOTCACHEPAGE (WordPress-community convention) and their admin exclusion list. Companion fix to acrossai-ai-connectors 0.5.3 PR #13 (DEC-OAUTH-DONOTCACHEPAGE-PATTERN). New includes/Utilities/CacheHeaders.php — port of the utility from acrossai-ai-connectors — applies a three-pronged defense (constant + headers + WP filter) on every per-session and per-server response emission surface: GET /servers/{id}/abilities, GET /servers/{id}/tools, GET /auth/status, GET /servers, POST /auth/start, POST /auth/exchange, POST /generate-app-password, and the wp_ajax_acrossai_mcp_dismiss_adapter_notice AJAX endpoint. Prevents cross-server data leaks (per-server ability/tool rosters bleeding into other sessions) and stale-response classes (cached {approved:false} served after the flip to true). Also fixes plugin-header vs ACROSSAI_MCP_MANAGER_VERSION constant drift — B5 bug pattern (constant lagged at 0.1.9 while header sat at 0.2.0). Both now aligned at 0.2.1.

0.2.0

• Dependencies: bump acrossai-co/main-menu 0.0.27 → 0.0.29. Picks up the shared main-menu package’s latest baseline for the 0.2.0 release cycle.
• Feature 040 — Migrated the AI Connectors + OAuth stack to the companion plugin acrossai-ai-connectors (v0.5.0+). MCP Manager now ships only the free-tier tab=npm and tab=clients connection paths; the OAuth click-to-connect flow (Claude Web, ChatGPT connectors, Grok) plus the AI Connectors admin tab now live in the paid acrossai-ai-connectors add-on. Token / client / auth_code storage is unchanged — same table names (wp_acrossai_mcp_oauth_clients, _tokens, _auth_codes, wp_acrossai_mcp_connector_approved_users), same BerlinDB db_version_keys, no data migration. REST namespace kept as acrossai-mcp-manager/v1 for RFC 8414 discovery compatibility. Existing Claude/ChatGPT/Grok OAuth connections continue to authenticate transparently when the add-on is installed — zero re-authorization required. Free users updating without the add-on are undisturbed (mcp-manager remains standalone-activatable; the AI Connectors tab simply doesn’t appear). Deletions: entire includes/OAuth/, includes/Connectors/, includes/Database/{OAuthClients,OAuthTokens,OAuthAuthCodes,ConnectorApprovedUsers}/, admin/Partials/ServerTabs/AIConnectorsTab.php, templates/oauth/consent.php, src/js/ai-connectors.js, src/scss/ai-connectors.scss, all build/js/ai-connectors.* artifacts, and all associated PHPUnit tests. Modifications: Activator.php, Deactivator.php (retains unconditional cron-clear as belt-and-suspenders per FR-004), Main.php (drops all OAuth REST route + infra wiring + 4 OAuth-table bootstrap/reconcile calls), admin/Main.php (drops maybe_enqueue_ai_connectors_app()), admin/Partials/ServerTabs/Registry.php (drops built-in AIConnectorsTab entry — companion re-registers via existing acrossai_mcp_manager_server_tabs filter at priority 35), uninstall.php (drops OAuth DROP TABLE lines + cron-clear + narrows the acrossai_mcp_% option sweep to exclude acrossai_mcp_connector_%), webpack.config.js (drops js/ai-connectors entry), and public/Discovery/ConnectionMethodRegistry.php (FR-019: swaps ConnectorProfileRegistry FQN to the companion namespace and guards with class_exists() so the discovery API returns an empty ai_connector category when the add-on is absent). Coordination invariant: the companion at v0.5.0+ has been audited across 44 checks (23 structural readiness + 21 wiring counterparts) and is deployable — the migration is atomic via the companion’s class_exists( '\AcrossAI_MCP_Manager\Includes\OAuth\AuthorizationController' ) self-disable probe. No compat shim, no Requires Plugins: header, no admin notice — per clarifications Q4/Q5/Q6, this feature adds ZERO new code (pure deletions + header version bump). Durable lesson captured: when a subsystem gets its own plugin, prefer code-only migration (identical table names, identical version keys, byte-identical BerlinDB Table subclass declarations) over data-migration.

0.1.9

• Feature 038 — User-accessible MCP servers shortcode + reusable base class. New shortcode [acrossai_mcp_servers] lists every MCP server the current logged-in user can reach (F015 access-control gate) whose F037 Embeds tab has the master toggle ON and at least one enabled connection method — surfacing per server every enabled NPM / MCP Client / AI Connector DTO from F035. Attributes: heading="", show_description="1", empty_message="…" (all optional). Ships with a data-only abstract base class \AcrossAI_MCP_Manager\Public\Renderers\UserServers\AbstractUserServersRenderer under public/Renderers/UserServers/ so companion plugins (planned BuddyBoss add-on, WooCommerce My Account, WPUM, MemberPress) can subclass and consume the enumeration primitive get_accessible_servers( ?int $user_id = null ): array without re-implementing the F015 + F037 gate cascade. Concrete UserServersBlock shortcode child is final per D36 (extend by filter, not subclass). Two new extension filters: acrossai_mcp_user_accessible_servers (reshape the payload per context; NOT a gate-bypass surface — consumers appending entries MUST replay the gate cascade themselves per SEC-004) and acrossai_mcp_servers_shortcode_html (override markup without subclassing; NOT re-sanitized — listener plugins trusted at filter boundary per SEC-002). Anonymous visitors get silent no-render (empty string). Logged-in users with zero accessible servers get an empty-state wrapper with a translatable message. Inline scoped <style> block emitted at most once per request via a private static flag (FR-016); CSS content is a static literal, no dynamic interpolation permitted (SEC-005 invariant). Icons render as <img> for http:// / https:// URLs and as esc_html text otherwise. Escape-at-render discipline mandated at every seam (FR-014). Pure composition on top of F011 MCPServerQuery + F015 access-control wrapper + F035 ConnectionMethodRegistry + F037 AbstractEmbedTransport (memoized per-DTO gate); zero new DB tables / REST endpoints / admin surfaces / JS. Consumer responsibility (SEC-001): when a companion plugin calls get_accessible_servers( $target_user_id ) with a target other than the current viewer, the consumer MUST independently verify the current viewer’s authority to see the target user’s info — F038 evaluates the F015 gate FOR the target user, not against the caller’s authority. New user-servers PHPUnit suite (tests/phpunit/Public/Renderers/UserServers/) registered in phpunit.xml.dist + CI job; three test files (abstract renderer + concrete block + third-party extensibility) cover the 11 algorithm cases + 12 render cases + 3 extensibility scenarios documented in contracts/*.contract.md §Test contract. @experimental per DEC-CLIENT-RENDERER-PUBLIC-API — data shape freezes at 1.0.0.

• Feature 037 — Per-server Shortcode + Block Embeds tab. New ”Embeds” admin tab under the server-edit page (?page=acrossai_mcp_manager&action=edit&server=<id>) lets site administrators enable/disable frontend shortcode + block output per server, with per-transport sub-toggles for NPM Methods, MCP Clients, and AI Connectors. Master toggle default OFF — fresh install ships zero shortcode output for every server (US1). Persists via new BerlinDB junction table wp_acrossai_mcp_server_embed_transports (presence model per DEC-TOOL-SELECTION-PRESENCE-MODEL) plus new embeds_enabled TINYINT(1) column on wp_acrossai_mcp_servers (D28 3-part schema-drift contract; $version bump 1.1.2 → 1.1.3). New AbstractEmbedTransport base class under includes/Embeds/ — direct application of D35 self-contained-subsystem-contract, mirrors F034 AbstractMCPClient::get_all_registered_clients() line-for-line. Three built-in concrete transports (NpmEmbedTransport, ClientEmbedTransport, AiConnectorEmbedTransport) with transport keys aligned 1:1 with F035 DTO category field values so consumers holding an F035 DTO can call AbstractEmbedTransport::is_enabled_for_server( $server_id, $dto['category'] ) with zero translation. New filter acrossai_mcp_embed_transports for third-party transport registration. New [acrossai_mcp_embed server="<slug>" category="<key>" slug="<optional-dto-slug>"] shortcode with 3-gate cascade: master toggle → per-transport toggle → F015 access control (fail-open per D19 when F015 wrapper absent). Two granular observability actions per FR-024 (acrossai_mcp_embed_master_toggled, acrossai_mcp_embed_transport_toggled) fire ONLY on actual value transitions — audit-log + reactor plugins get first-class integration points. New action acrossai_mcp_server_deleted fires on server-row deletion; F037 wires cleanup listener that prunes junction rows per FR-017. Optional AbstractEmbedTransport::garbage_collect_orphans() helper for companion plugins’ uninstall.php. Admin UI ships as a React app at #acrossai-mcp-embeds-root per D37 / DEC-ADMIN-UI-REACT-FIRST (matches F017 Abilities + F020 Tools patterns) — uses @wordpress/components (ToggleControl, Button, Notice, Spinner), @wordpress/element, @wordpress/api-fetch with nonce middleware only (B25 defense), @wordpress/i18n. Saves via REST endpoint POST /acrossai-mcp-manager/v1/servers/{server_id}/embeds (matches F017/F020 URL shape verbatim); permission_callback verifies manage_options (S2) + WP core wp_rest nonce. Cross-server bypass structurally impossible — REST URL {server_id} path parameter IS the tenant scope. Fail-forward per-listener try/catch on observability actions per R3 (broken audit listeners MUST NOT roll back DB writes). New embeds PHPUnit suite registered in phpunit.xml.dist + CI job. B1 regex bugfix shipped inline: transport-key regex widened from /\A[a-z0-9-]{1,64}\z/ to /\A[a-z0-9_-]{1,64}\z/ to accept the ai_connector key. SEC-037-002 comparator (int) coercion shipped. Marked @experimental until plugin 1.0.0 per DEC-CLIENT-RENDERER-PUBLIC-API inheritance. Consumes ConnectionMethodRegistry::get_all() (F035) as its DTO source; NEVER re-fires F034/F021/F035 filters (verified by SC-005 grep gate). DEV5 no longer applies post-pivot (F037 dropped from consumer count).

• Feature 035 — Public connection-method discovery API. New singleton AcrossAI_MCP_Manager\Public\Discovery\ConnectionMethodRegistry exposes every registered NPM method, MCP client, and AI connector as a unified list of plain-associative-array DTOs — one canonical entry point (get_all()) replaces three separate registries with three different shapes. Third-party plugins (motivating consumer: planned BuddyBoss add-on) can now enumerate every connection method the site supports without re-implementing per-category lookup loops. Every DTO across all three categories carries the same six top-level keys (category, slug, name, description, icon, meta) plus category-specific extras in meta; wp_json_encode() round-trips losslessly so consumers can safely persist to their own storage. Adds two new extensibility filters: acrossai_mcp_npm_methods (closes the NPM extension-seam gap — NPM had no filter surface before this release) and acrossai_mcp_connection_methods (fires once on the assembled get_all() result for cross-category concerns without duplicating three separate filter registrations). Delegates transparently to AbstractMCPClient::get_all_registered_clients() (F034) and ConnectorProfileRegistry::get_profiles() (F021) — never re-fires their filters, verified by two grep gates (SC-005 for delegation, SC-006 for one-way public/ ↛ includes/ layering). NpmClientBlock grows a new get_default_npm_method(): array static helper so the NPM template + option gate has a single source of truth; NPM tab render remains byte-identical (SC-007 automated regression guarded by dedicated NpmDefaultHelperTest). NPM filter contributions dedup by slug later-wins (matches F034 semantics) and are validated against the six-key + value-type contract per SEC-035-001 — malformed entries (slug => array(), meta => 'string', etc.) silently dropped + _doing_it_wrong under WP_DEBUG (SEC-013-008 pattern inheritance). Malformed acrossai_mcp_connection_methods callback returns fall back to the pre-filter assembled result — consumers always receive a well-shaped three-category array regardless of companion-plugin bugs. New discovery PHPUnit suite (tests/phpunit/Public/Discovery/) registered in phpunit.xml.dist + CI job; ~20 test methods across two test files covering singleton shape, DTO invariants, JSON round-trip, find() lookup, memoization + flush_cache(), NPM filter fire + dedup + type-drift dropped, cross-category filter fires-once-only-in-get_all + malformed-return fallback. Zero admin UI, zero REST routes, zero database changes. Marked @experimental until plugin 1.0.0 per DEC-CLIENT-RENDERER-PUBLIC-API.

• Dependencies: bump acrossai-co/main-menu 0.0.23 → 0.0.27. Picks up the shared main-menu package’s latest baseline (Add-ons page metadata, submenu policy refinements).

• Internal: ACROSSAI_MCP_MANAGER_VERSION constant bumped to 0.1.9 matching the plugin header.

0.1.8

• Feature 034 — MCP client subsystem refactor: metadata methods + canonical filter-aware enumeration. Each concrete MCP client class (ClaudeDesktopClient, ClaudeCodeClient, VSCodeClient, GitHubCopilotClient, CodexClient, CursorClient, GeminiClient, CustomClient) now declares its own display metadata via six new methods on AbstractMCPClient — get_icon(), get_description(), get_config_file(), get_top_level_key(), get_instructions(), plus get_priority(): int (default 100, built-ins pre-assigned 10, 20, 30, ..., 80 to preserve pre-refactor sub-nav order). Replaces the private CLIENT_META const in MCPClientsBlock (deleted). Enumeration collapses to a single canonical entry point AbstractMCPClient::get_all_registered_clients() that fires the existing acrossai_mcp_client_classes filter with a DEFAULT_CLIENT_CLASSES seed, validates FQNs per SEC-013-008 (silent-skip on invalid), validates slugs against /[a-z0-9-]{1,64}/ (_doing_it_wrong under WP_DEBUG on violators), dedups by slug with later-wins, and sorts by (priority ASC, slug ASC) — mirroring ConnectorProfileRegistry::get_profiles() line-for-line. The pre-F034 glob-based AbstractMCPClient::get_all_clients() (which ignored the filter) is deleted. MCPClientsBlock::render_body() shrinks from 32 lines to 6 (single call to the canonical enumeration + iteration; no inline default-classes array, no local filter loop, no metadata lookups by slug). Third-party client subclasses contributed via the filter now have a symmetric way to declare their own icon / description / config-file / top-level-key / instructions / sub-nav slot instead of being stranded in the Renderer’s private const. Byte-identical rendered output for the eight built-in clients on the server-edit → Clients tab. No breaking changes for existing third-party subclasses — the six new methods default to empty strings (or 100 for priority). Test coverage: new GetAllRegisteredClientsTest.php covers default state / filter contribution / invalid FQN skip / bad slug reject / duplicate slug later-wins / priority sort with slug tiebreaker; new ConcreteClientMetadataTest.php data-provider parameterized over all 8 built-ins asserts each returns the migrated metadata values; new MCPClientsBlockRenderTest.php under the renderers suite verifies FR-016 render byte-identity via DOM markers AND exercises the SEC-034-001 preservation invariant (hostile third-party subclass returning <script> payloads MUST be escaped at render). mcpclients PHPUnit suite grows to 86 tests / 181 assertions (up from 74 pre-F034). Durable memory captured as D35 / DEC-F034-SELF-CONTAINED-SUBSYSTEM-CONTRACT — generalizable pattern for every future subsystem with an abstract base + filter-based subclass contribution + per-subclass display metadata.

0.1.7

• Feature 033 — Security fix: F030 permission_callback wrapper dropped args and coerced WP_Error to true. Two bugs in PermissionOverrideProcessor::inject_override combined into a plugin-wide permission_callback bypass. The wrapper closure was declared static function () use ( ... ) — zero parameters — so every arg the caller passed was silently discarded. Downstream callbacks that read their input (notably Execute::check_permission looking up $input['ability_name']) saw an empty array and returned WP_Error( 'missing_ability_name', ... ). The wrapper’s call_original helper then did return (bool) call_user_func( $original ); — casting the WP_Error object to boolean true (PHP casts every object to true). The vendor’s if ( true !== $permission ) check in ToolsHandler::call_tool (vendor/wordpress/mcp-adapter/includes/Handlers/Tools/ToolsHandler.php:148) read that as ”permission granted” and proceeded to execute(). Impact: any authenticated user with any role (including subscriber) could invoke any registered ability via mcp-adapter/execute-ability on the default MCP server, even when the Abilities tab had explicitly disabled the ability (is_exposed=0 row in wp_acrossai_mcp_server_abilities) and the ability itself declared meta.mcp.public = false. Fix: closure is now static function ( ...$callback_args ) use ( ... ) and forwards $callback_args on every fall-through path; call_original returns bool|WP_Error — WP_Error results propagate unchanged, only scalar returns are coerced. The six-layer allow-path semantics (DEC-F030-PERMISSION-CALLBACK-OPERATOR-OPT-IN-BYPASS) are unchanged — only the fall-through path is affected. Test coverage: three new regression tests in PermissionOverrideProcessorTest.php — args forwarding, WP_Error preservation, and a @dataProvider-parameterised role sweep across subscriber / contributor / author / editor / administrator proving low-privilege roles are correctly denied post-fix. Durable memory captured as B40 / B-WRAPPER-CLOSURE-MUST-FORWARD-ARGS-AND-PRESERVE-WP-ERROR — generalizable pattern for any closure wrapping a user callback (permission_callback, execute_callback, filter/action decorators, plugin bridges). Follow-up tracked as issue #46: filter-time eligibility gate refactor to skip installing the wrapper entirely for abilities that could never satisfy F030’s six defensive layers — eliminates the wrapper-bug class for the vast majority of abilities.
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant bumped to 0.1.7 matching the plugin header.

0.1.5

• Feature 031 — Add Google Gemini CLI as a supported MCP client. The server-edit Clients tab now surfaces a Gemini card (💎 pill) alongside the existing 7. Uses the same npx @automattic/mcp-wordpress-remote@latest bridge + WP Application Password Basic auth as Claude Desktop / Cursor / other stdio-based clients; config paste target is ~/.gemini/settings.json under the standard mcpServers key. GeminiClient is a near-verbatim mirror of ClaudeDesktopClient (slug gemini, name Gemini CLI, byte-for-byte identical get_config_snippet shape) — no new auth mechanism, no new abstraction, no new render path. Registered in MCPClientsBlock::$default_classes + CLIENT_META['gemini']. Test suite canary bumped from 7 → 8 concrete clients; mcpclients PHPUnit suite now runs 74 tests / 124 assertions (up from 67/111 pre-F031).
• Assets — Refreshed WordPress.org plugin-directory banners (1544×500 + 772×250 PNGs in .wordpress-org/). No code change; visual update only.
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant bumped to 0.1.5 matching the plugin header.

0.1.4

• Feature 030 — Per-server ability permission_callback override. The MCP-server-edit ”Access Control” tab now hosts a second section (below the existing wpb-access-control React panel, separated by <hr>) with a single toggle: when enabled, every ability exposed to this MCP server via the Abilities tab bypasses its own permission_callback for MCP requests routed to this server. Site-wide ability callers (WP admin, non-MCP REST namespaces, WP-CLI) see the original permission_callback unchanged — the closure short-circuits when CurrentServerHolder is empty. Runtime filter registers on wp_register_ability_args at priority 999999, strictly higher than sibling acrossai-abilities-manager’s P100000 injector and this plugin’s own CallbackReplacer P10, so the operator toggle wins deterministically. Gated by six defensive layers documented in DEC-F030-PERMISSION-CALLBACK-OPERATOR-OPT-IN-BYPASS: manage_options capability + per-server nonce (acrossai_mcp_manager_permission_override_{server_id}) + persistent warning banner when ON + native confirm() prompt on submit-to-ON + CurrentServerHolder scope + ExposureResolver::resolve() gate. Adds one column via D28 3-part BerlinDB contract (MCPServer\Table 1.1.1 → 1.1.2 + upgrade_to_1_1_2 callback, idempotent per INFORMATION_SCHEMA.COLUMNS). Fires new observability action acrossai_mcp_permission_override_toggled( $server_id, $value, $user_id, $timestamp ) on every save — operators can attach any logger (Query Monitor, custom audit table, syslog) without a hard dependency. Also adds a promotional card for the sibling acrossai-abilities-manager plugin (already in acrossai-co/main-menu’s baseline addon list — no double-register) with links to install/activate via the shared Add-ons page or edit abilities when active, plus a <details> ”Prefer to use code?” fallback documenting the filter name + priority for developers who prefer not to install another plugin.
• Feature 030 (bonus) — Test-infrastructure fix. tests/phpunit/{Abilities,Database,MCP}/ were orphaned in phpunit.xml.dist — no suite covered them, so CI never ran F011/F017/F026 legacy tests OR any F030 new tests. Fixed by adding 3 new PHPUnit suites (abilities, database, mcp) + 3 matching CI workflow steps in .github/workflows/phpunit.yml. All previously-orphaned tests + all F030 new tests now execute in CI on every push.
• Feature 030 — Durable memory captured. Five new entries in docs/memory/: D29 (six-layer defensive gating framework for any future permission_callback bypass — scoped carve-out from D24), D30 (F030 intentionally passes empty $meta to ExposureResolver::resolve() — scoped carve-out from DEC-ABILITY-OVERRIDE-RESOLUTION), B35 (wp_register_ability_args filter-priority slot map: P10 CallbackReplacer, P100000 sibling, P999999 F030), B36 (inline <script> string-interpolation requires wp_json_encode(), not esc_html/esc_attr — generalizable JS-context escaping rule), DEV5 (per-server-edit tab hand-rolled admin form exception to §IV DataForm mandate per D13 escalation ≥ 2 features).
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant bumped to 0.1.4 matching the plugin header.

0.1.3

• Feature 029 (OAuth) — RFC 6749 §2.3.1 HTTP Basic auth accepted on /token + client_secret_post softening. TokenController now parses Authorization: Basic base64(client_id:client_secret) with CGI fallback (REDIRECT_HTTP_AUTHORIZATION) and applies header-first-then-body credential resolution to both authorization_code and refresh_token grants. When a client registered as client_secret_post submits NO secret at exchange (header AND body both empty), the endpoint now falls through to PKCE-only verification instead of hard-rejecting with invalid_client. Modern MCP hosts (Claude.ai, ChatGPT, Cursor, Cline) frequently register as client_secret_post but behave as public+PKCE at exchange; the softening keeps them interoperable. Confidential clients that DO send a secret are still verified via constant-time ClientRepository::verify_secret (unchanged). Codified as durable decision D27. Residual risk bounded by mandatory PKCE S256 + RFC 8707 audience binding + single-use auth codes + refresh-family revocation.
• Feature 029 (OAuth) — DCR-registered clients now attributed to their connector profile at registration time. ClientRegistrationController::handle_register() walks ConnectorProfileRegistry::get_profiles() and calls matches_dcr_client( $client_name, $redirect_uris ) on each — first matching profile’s slug is persisted as connector_slug (previously always empty). Fixes F024’s per-connector settings gate: DCR-registered clients (Claude.ai etc.) that previously bypassed the operator’s enable/disable toggle now honor it correctly. Bug pattern captured as B33 (admin-gate silent-bypass on data-field left empty).
• Feature 029 (DB) — BerlinDB schema-drift reconciliation for wp_acrossai_mcp_cli_auth_logs + wp_acrossai_mcp_servers. Two live tables had drifted from their Schema.php while stored db_version still matched code — parent::maybe_upgrade() short-circuited forever, and any INSERT referencing a Schema column missing from the actual table returned false, which callers cast to int(0) and treated as success (silent write-loss; identical shape took down Claude OAuth on procureco.uk before F029). Bumps CliAuthLog\Table 1.0.0 → 1.0.1 (adds upgrade_to_1_0_1 callback that ALTER MODIFYs status varchar(20) → varchar(32), failure_code varchar(100) → varchar(64), app_password_uuid varchar(64) → varchar(36)) and MCPServer\Table 1.1.0 → 1.1.1 (adds upgrade_to_1_1_1 callback that ALTER ADD COLUMN for the three F025 protocol flags tool_discover_abilities, tool_get_ability_info, tool_execute_ability). Both callbacks idempotent per-column via INFORMATION_SCHEMA existence/width check. Codified as D28 (BerlinDB $upgrades reconciliation pattern) + B34 (silent write-loss bug pattern).
• Feature 029 (Boot) — Main::reconcile_database_schemas() on admin_init@3. New Loader-wired admin hook fires maybe_upgrade() on all 7 BerlinDB Tables on every admin request. Before F029, maybe_upgrade() only ran from Activator::activate() — activation runs once, so version bumps on in-place upgrades (composer / wp-cli plugin update / manual file replace) stayed inert until deactivate + reactivate. Priority 3 fires BEFORE Settings::maybe_seed_default_server (4) and Settings::handle_actions (5) so schema is reconciled before any handler reads from these tables. Per-admin-request cost: 7 option reads (needs_upgrade short-circuits when versions match).
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant bumped to 0.1.3 matching the plugin header.

0.1.2

• Feature 027 — Fix: DCR token_endpoint_auth_method default flipped to none for public+PKCE clients. ClientRegistrationController::handle_register() (includes/OAuth/ClientRegistrationController.php:310) previously defaulted the RFC 7591 Dynamic Client Registration token_endpoint_auth_method field to client_secret_post when the caller omitted it. Modern MCP hosts (Claude.ai, ChatGPT, Cursor, Cline) register as public+PKCE clients — they omit the field in DCR and never carry a client_secret through the /token exchange. The old default silently stored these clients as confidential; the follow-up authorization-code exchange then failed at TokenController::handle_authorization_code() (includes/OAuth/TokenController.php:106-111) with invalid_client HTTP 401 after the auth code had already been consumed atomically at AuthCodeRepository::consume_atomic line 89 — so the client saw a generic ”Authorization failed” page with no ability to retry. Default now flips to none, matching RFC 8252 §8.4 for public+PKCE clients. Confidential-client callers can still pass token_endpoint_auth_method=client_secret_post explicitly in the DCR body; admin-generated clients at handle_admin_generate are unaffected (they continue to hardcode client_secret_post). New phpunit case test_omitted_auth_method_defaults_to_none_public_client in tests/phpunit/OAuth/DCRRegisterFreshTest.php locks the invariant.

0.1.1

• Feature 028 — Retire Freemius integration; consume acrossai-co/main-menu 0.0.22+ filter-driven Add-ons page. The bundled freemius/wordpress-sdk transitive dependency is dropped entirely (vendor removed it from acrossai-co/main-menu 0.0.22’s require block along with the AcrossAI_Addon\ PSR-4 namespace). This plugin’s Freemius integration in Main::define_admin_hooks() — the \AcrossAI_Addon\AddonsPage instantiation with fs_product_id => '34418' / fs_public_key / fs_slug => 'acrossai-add-ons' / fs_menu / fs_has_addons config, its class_exists+try/catch guards, and its admin-notice fallback closure — is removed in full (94 lines). No opt-in card, no api.freemius.com outbound requests, no umbrella-product license state. Bumps acrossai-co/main-menu 0.0.18 → 0.0.23.
• New consumer self-exclusion filter. A new singleton admin/Partials/AddonsFilter hooks the vendor’s acrossai_addons filter and drops the entry with slug === 'acrossai-mcp-manager' from the array — an already-active plugin should not advertise itself as an installable add-on on the shared Add-ons page. Codified as D26 / DEC-CONSUMER-SELF-EXCLUSION-VIA-VENDOR-FILTER (paired with D20 on the subtractive side). Every future AcrossAI plugin whose slug appears in AddonsPageRenderer::ADDONS MUST ship the same pattern.
• User-visible behavior change: the AcrossAI → Add-ons submenu no longer renders from this plugin. The Add-ons submenu is now rendered by whichever consumer of acrossai-co/main-menu 0.0.22+ activates first. If this plugin is the only AcrossAI plugin active on an install, the Add-ons submenu disappears until a companion plugin activates.
• Related durable memory flipped to Superseded (F028): DEC-ADDONS-PAGE-VENDOR-CTOR-BOOT (external-package self-registering-in-constructor exception to A1 — obsolete because \AcrossAI_Addon\AddonsPage no longer exists), DEC-FREEMIUS-DOUBLE-OPTIN-GATES-ACCOUNT (opt-in state-machine diagnosis — no live surface here anymore), and B28 (Freemius two-level menu.<key> + has_<key> enablement pattern — SDK is gone). Entry bodies retained per PATTERN-MEMORY-SUPERSESSION-VS-ANNOTATION.
• Internal: ACROSSAI_MCP_MANAGER_VERSION constant resynced. Drifted at 0.0.9 across the 0.1.0 release; now correctly reads 0.1.1 matching the plugin header.
• Operator recipe for prior installs (optional cleanup): Freemius’ SDK previously wrote fs_accounts, fs_active_plugins, fs_api_cache, fs_cache_*, and fs_debug_mode rows to wp_options. Nothing this plugin loads reads or writes them post-F028. To purge: DELETE FROM wp_options WHERE option_name LIKE 'fs_%';. The plugin does NOT ship this as an automatic migration (per D21 fresh-install-only retirement pattern established by F016).

0.1.6

• Feature 032 — OAuth per-server scoping (SECURITY FIX + BREAKING CHANGE for legacy DCR sessions).

  ⚠️ BEFORE UPGRADE — READ THIS: this release deletes any pre-F032 DCR-registered OAuth client rows (those without a server-{id}- prefix — e.g., legacy Claude.ai / ChatGPT / Cursor / Cline connections) and their associated tokens + auth codes as part of the D28 upgrade migration. Any live AI-host session bound to a legacy DCR row will disconnect on the next request; affected users must re-run the OAuth authorize flow from their AI host to reconnect. All post-F032 DCR registrations are per-server and unaffected. Consider (a) snapshotting wp_acrossai_mcp_oauth_{clients,tokens,auth_codes} before upgrade, and (b) notifying users with active AI-host connections that they will need to re-authorize once after upgrade.

  Security fix: closes a cross-server privilege-escalation gap where an admin on Server A’s Connectors tab could revoke or delete Server B’s clients + tokens by modifying the client_id in the outbound REST body. Also closes a read-side display leak in the ”authorized users” listing on the AI Connectors tab.

  What ships: adds server_id BIGINT UNSIGNED NOT NULL column (final state) to wp_acrossai_mcp_oauth_clients, wp_acrossai_mcp_oauth_tokens, and wp_acrossai_mcp_oauth_auth_codes via the D28 3-part BerlinDB $upgrades contract (each Table bumps $version 1.0.0 → 1.0.1 with matching upgrade_to_1_0_1() callback). Replaces standalone UNIQUE(client_id) on oauth_clients with composite UNIQUE(client_id, server_id) so the same DCR connector can be registered on multiple MCP servers as independent rows. Every mutating REST endpoint (revoke-client-tokens, delete-client, revoke-connector-tokens) now requires + validates …