Fix: Claude Code MCP Clients tab now shows a JSON config block instead of a claude mcp add shell command. The ~/.claude.json config file path is displayed correctly (was incorrectly listed as ~/.claude/mcp_servers.json), the snippet renders as a copy-pasteable mcpServers block with command/args/env, and the env now pins OAUTH_ENABLED: “false” alongside WP_API_URL / WP_API_USERNAME / WP_API_PASSWORD to keep the @automattic/mcp-wordpress-remote client from falling into an OAuth branch it can’t complete against an Application Password server. Instructions on the tab updated to match (“paste under the top-level key” — no more claude mcp add-json).
Internal: ACROSSAI_MCP_MANAGER_VERSION constant now tracks the plugin header. It had drifted at 0.0.6 across the 0.0.7 and 0.0.8 releases; this release resyncs it to 0.0.9. Consumers reading the constant to key cache entries or telemetry will see a version bump even though there are no functional changes since 0.0.8 beyond the Claude Code tab fix above.
Tests: repair 14 stale JSON fixtures. The ConcreteClientsTest golden fixtures for claude-desktop, vscode, github-copilot, codex, cursor, and custom were missing the WP_API_USERNAME env field that all 6 clients have emitted since Feature 004. Adding the field brings fixtures back in sync with the code — 49/49 tests now pass (was 35/49).
0.0.8
Dependencies: bump acrossai-co/main-menu to 0.0.11.
0.0.7
Docs: rewrite README.txt from the canonical baseline (proper Description, FAQ, Screenshots, install steps).
Docs: fix wp.org import warnings — real Contributors (raftaar1191), plugin-relevant Tags (mcp, ai, copilot, vscode, claude), and a Short Description tagline.
Header: refresh plugin header — Plugin URI https://acrossai.co/, Author raftaar1191, wp.org profile Author URI, License normalized to GPL-2.0-or-later.
Build: expand .distignore to exclude tooling / config / docs / tests / editor dirs from the wp.org build. .gitignore cleaned up.
CI: add GitHub Actions workflows for PHPStan, PHPCompatibility, PHPUnit (mcpclients suite), PHPCS, build-zip, and wp.org deploy.
Requirements: bump minimums to WordPress 7.0 / PHP 8.1.
0.0.6
Migrated the four internal DB modules (MCP Servers, CLI Auth Log, OAuth Tokens, OAuth Audit) to BerlinDB Core 3.0. Fresh installs create tables with BerlinDB-derived schemas; the phantom-version guard on every Table subclass silently self-heals a stamped-but-missing table on the next activation. This release ships to zero live installs — no data migration path is provided; sites with pre-migration schema must be recreated from scratch.
Added an “MCP” tab to the shared AcrossAI Settings page (?page=acrossai-settings) with three operator toggles: enable CLI connections (acrossai_mcp_npm_login_enabled), enable direct Claude Connectors mode (acrossai_mcp_claude_connectors_enabled), and Delete all data on uninstall (acrossai_mcp_uninstall_delete_data). Sibling to acrossai-abilities-manager’s Abilities tab.
BEHAVIOR CHANGE: uninstall.php now preserves ALL plugin data by default. The pre-Feature-012 build dropped acrossai_mcp_oauth_tokens + acrossai_mcp_oauth_audit unconditionally; this build preserves every wp_acrossai_mcp_* table and every acrossai_mcp_* option unless the operator explicitly ticks the “Delete all data on uninstall” checkbox on the MCP settings tab and saves. Sites that expected the pre-Feature-012 OAuth-table wipe on uninstall must tick the new checkbox before uninstall.
Removed the standalone “CLI Auth Log” admin submenu at ?page=acrossai_mcp_manager_cli_auth_log. The underlying wp_acrossai_mcp_cli_auth_logs table + Query/Row classes remain — they continue to power the OAuth authentication flow. Auth-log inspection is now available via WP-CLI (wp db query “SELECT … FROM wp_acrossai_mcp_cli_auth_logs”); the standalone submenu was redundant post-Feature-011.
Refactored the per-server-edit page (?page=acrossai_mcp_manager&action=edit) into a per-tab class hierarchy under admin/Partials/ServerTabs/. Ported 7 additional tabs from the reference plugin (Overview, npm, MCP Clients, WP-CLI, Tools, Abilities, MCP Tracker) plus 2 database-registered-only tabs (Update Server, Danger Zone). The full 11-tab UI is now available for database-registered servers; plugin-registered servers see 9 tabs.
NEW: Public Renderer layer under public/Renderers/ exposes 3 client-configuration blocks (npm, MCP Clients, Claude Connector) as a reusable API so third-party plugins (BuddyBoss, WooCommerce, other AcrossAI-family plugins) can embed the same UI on their own admin or frontend surfaces with zero code duplication. Public API surface: static Renderer::render() method + acrossai_mcp_render_client_block action hook + acrossai_mcp_client_block_context filter + acrossai_mcp_client_classes filter + shortcodes ([acrossai_mcp_npm_block], [acrossai_mcp_clients_block], [acrossai_mcp_claude_connector_block]) + REST endpoint (/wp-json/acrossai-mcp-manager/v1/generate-app-password) with defense-in-depth Application Password lockdown to get_current_user_id(). API is @experimental May change without notice before 1.0.0 (per DEC-CLIENT-RENDERER-PUBLIC-API). Restored CliAuthLogListTable + added ConnectorAuditLogListTable as per-server tab inspectors under DEC-ADMIN-SURFACE-PRUNE-CLI-AUTH-LOG’s blessed reintroduction path. See docs/integrations/buddyboss-example.md and docs/integrations/woocommerce-example.md for third-party integrator onboarding.
Adopted wpboilerplate/wpb-access-control v2 with per-server access rules, MCP-boundary enforcement via the mcp_adapter_pre_tool_call filter shipped by wordpress/mcp-adapter, and a shared Renderer block (AccessControlBlock) that third-party plugins can embed on their own admin surfaces. Fixes 3 fatal v1-API call sites (AccessControlTab.php, CliController.php /servers route, Main.php TODO block). Activator now creates the {prefix}mcp_manager_access_control table; uninstall opt-in gate purges the namespace + drops the table + deletes the version option. Two observability action hooks let operators log denials via any listener: acrossai_mcp_access_control_denied fires immediately before returning WP_Error / empty server list on deny (args: user_id, server_slug, tool_name-or-null, context_slug where context_slug is ‘cli_servers’ at CliController or ‘mcp_tool_call’ at MCP boundary); acrossai_mcp_access_control_missing_server fires when a server was DELETEd mid-flight (args: server_slug, tool_name, user_id). Minimal listener example: add_action(‘acrossai_mcp_access_control_denied’, function($u,$s,$t,$c){ error_log(“[AC deny] user=$u server=$s tool=$t via=$c”); }, 10, 4);. See DEC-ACCESS-CONTROL-V2-ADOPTION + D18 + D19 for the wrapper pattern, canonical MCP-boundary hook, and fail-open observability pattern.
0.0.5
Changed: access-control admin UI now loads assets from the wpb-access-control vendor package’s own compiled React bundle; removed plugin-bundled copies at assets/access-control/
Changed: replace AccessControlUI AJAX bootstrap with REST API registration via AccessControlManager::register_rest_api(); rules are now served and saved via dedicated REST endpoints
Changed: access-control tab renders a React component hydrated by the vendor webpack bundle instead of legacy plain-JS markup
Added: graceful degradation notice when vendor assets are unavailable — enforcement remains active
Updated: wpb-access-control to v1.0.0 (stable baseline); automattic/jetpack-autoloader to latest minor
0.0.4
Improved: bundle access-control UI assets (CSS + JS) directly in the plugin at assets/access-control/ so the admin panel works regardless of whether the wpb-access-control vendor package ships them
0.0.3
Dependencies: update wpb-access-control to BerlinDB-backed version; add berlindb/core; update bshaffer/oauth2-server-httpfoundation-bridge and symfony/deprecation-contracts
