Only if you want the one-click hosted-OAuth flow for Claude, ChatGPT, or Grok. All other connection styles (MCP Client, CLI, WP-CLI STDIO) are free and shipped with this plugin. See AI Connectors add-on<\/a>.<\/p><\/dd>\n\n<\/dl>\n\n\n0.2.10<\/h4>\n\n\n- Admin \u2014 Embeds tab hidden from the per-server-edit page.<\/strong> The Embeds<\/strong> tab (formerly reached at
?page=acrossai_mcp_manager&action=edit&server=<id>&tab=embeds<\/code>) is no longer registered in Registry::all_tabs()<\/code> and its self-registration in Main::define_public_hooks()<\/code> (EmbedsTab::register()<\/code>) is now commented out \u2014 so the tab's REST controller (\/acrossai-mcp-manager\/v1\/servers\/{server_id}\/embeds<\/code>) and its React bundle (build\/js\/embeds.js<\/code> + .css<\/code>, ~389 KiB) no longer enqueue on the server-edit screen. Direct URL access to ?tab=embeds<\/code> falls through to Registry's default (first surviving tab = Overview) rather than 404 \u2014 same graceful-fallback path any unknown slug takes. Built-in tab count: 12 \u2192 11. The admin\/Partials\/ServerTabs\/EmbedsTab.php<\/code> class file, the underlying [acrossai_mcp_embed]<\/code> shortcode, the block, and the AbstractEmbedTransport<\/code> transports in includes\/Embeds\/<\/code> are all retained \u2014 hiding is admin-UI-only; the frontend embed rendering pipeline is unaffected. Re-enabling the tab is a two-line change (re-add EmbedsTab::instance()<\/code> to Registry + uncomment the register()<\/code> call). Tests in tests\/phpunit\/Admin\/ServerTabs\/RegistryTest.php<\/code> updated: expected counts adjusted (12 \u2192 11 for canonical + database-source servers; 10 \u2192 9 for plugin-source servers); ordering array + docblock counts refreshed; a new assertNotContains( 'embeds', $slugs )<\/code> line locks in the invariant.<\/li>\n- Internal:
ACROSSAI_MCP_MANAGER_VERSION<\/code> constant + Stable tag<\/code> bumped to 0.2.10<\/code> matching the plugin header.<\/strong><\/li>\n<\/ul>\n\n0.2.9<\/h4>\n\n\n- Dependencies \u2014 bump
acrossai-co\/main-menu<\/code> 0.0.31<\/code> \u2192 0.0.33<\/code>.<\/strong> The upstream vendor renamed its \"AI Connectors\" baseline Add-ons entry to AcrossAI Pro<\/strong> in 0.0.32<\/code> \u2014 the shared Add-ons page (admin.php?page=acrossai-addons<\/code>) and Dashboard card now advertise the renamed plugin (acrossai-pro\/acrossai-pro.php<\/code> install folder, acrossai-pro<\/code> registry slug) instead of the former AI Connectors listing. 0.0.33<\/code> refreshed the AcrossAI Pro card copy \u2014 description now also mentions user access control across AcrossAI plugins \u2014 and points every AcrossAI Pro CTA (Add-ons card more_url<\/code> \/ learn_more_url<\/code>, Dashboard primary\/secondary CTAs) at https:\/\/acrossai.co\/pricing\/#pricing<\/code>. No changes required in this plugin:<\/strong> MCP Manager's AddonsFilter::remove_self()<\/code> filters the acrossai_addons<\/code> list by its own slug (acrossai-mcp-manager<\/code>), so the vendor's baseline entry rename doesn't affect what shows on the Add-ons page here. The per-server-edit Connectors\/Integrations<\/strong> tab still points at the separate acrossai-ai-connectors<\/code> WordPress plugin (WP plugin folder slug, distinct from the vendor's addons-registry slug), so the promo card + CTA are unaffected. Transitive: automattic\/jetpack-autoloader<\/code> v5.0.21<\/code> \u2192 v5.0.23<\/code> (patch).<\/li>\n- Internal:
ACROSSAI_MCP_MANAGER_VERSION<\/code> constant + Stable tag<\/code> bumped to 0.2.9<\/code> matching the plugin header.<\/strong><\/li>\n<\/ul>\n\n0.2.8<\/h4>\n\n\n- \u26a0\ufe0f Security \u2014 Behavior change \u2014 MCP
resources\/read<\/code> and prompts\/get<\/code> requests are now gated by the per-server Access Control rule (F1 fix).<\/strong> Prior to 0.2.8 the plugin only hooked the vendor's mcp_adapter_pre_tool_call<\/code> filter. The two sibling pre-dispatch filters \u2014 mcp_adapter_pre_resource_read<\/code> (vendor\/wordpress\/mcp-adapter\/includes\/Handlers\/Resources\/ResourcesHandler.php:138<\/code>) and mcp_adapter_pre_prompt_get<\/code> (...\/Prompts\/PromptsHandler.php:157<\/code>) \u2014 had no subscriber. Combined with the Feature 042 transport layer intentionally deferring to F015 for rule-configured servers (returning the vendor 'read'<\/code> default so any authenticated user passes the transport gate, on the assumption that F015 would then enforce), any authenticated user could POST {\"method\":\"resources\/read\",\"params\":{\"uri\":\"\u2026\"}}<\/code> (or {\"method\":\"prompts\/get\"}<\/code>) against a server configured \"Editors only\" and the operator's rule was never consulted<\/strong>. 0.2.8 extracts the enforcement body of gate_mcp_tool_call<\/code> into a shared private apply_ac_gate()<\/code> helper and adds two sibling public callbacks \u2014 gate_mcp_resource_read<\/code> + gate_mcp_prompt_get<\/code> \u2014 wired adjacent to the existing tool-call filter in Main::define_public_hooks()<\/code>. Deny path returns a WP_Error<\/code> with a gate<\/code> value of mcp_resource_read<\/code> \/ mcp_prompt_get<\/code> (previously always mcp_tool_call<\/code>). Observability hooks are reused: acrossai_mcp_access_control_denied<\/code> and acrossai_mcp_access_control_missing_server<\/code> now fire from three MCP boundary sites \u2014 the $context<\/code> arg discriminates and the $subject<\/code> arg is polymorphic (tool name \/ resource URI \/ prompt name depending on which gate fired). New PHPUnit coverage at tests\/phpunit\/Includes\/AccessControl\/McpDispatchGatesTest.php<\/code> \u2014 fail-open parity per gate, missing-server observability hook subject-arg carries URI\/prompt name, three-context deny-hook contract, all three vendor filter registrations verified.\n\n\n- Operator action if you were relying on the resource\/prompt bypass<\/strong>: audit any server that exposes MCP resources or prompts AND has a rule configured. Non-privileged users who previously succeeded on
resources\/read<\/code> \/ prompts\/get<\/code> will now receive HTTP 403 with the same acrossai_mcp_access_denied<\/code> error code the tool-call gate has emitted since 0.0.7. Broaden the rule in the Access Control<\/strong> tab if the previous fail-open was intended (unlikely \u2014 most operators wanted the rule to apply).<\/li>\n<\/ul><\/li>\n- \u26a0\ufe0f Security \u2014 Behavior change \u2014 F042 transport layer now fails CLOSED when the wpb-access-control vendor package is unavailable (F2 fix).<\/strong> Prior to 0.2.8 both access-control gates failed OPEN under the same condition:
AcrossAI_MCP_Access_Control::gate_mcp_tool_call<\/code> returned $args<\/code> (allow) when class_exists( AccessControlManager::class )<\/code> was false; TransportPermissionDefault::filter_default_capability<\/code> returned the vendor 'read'<\/code> default under the mirror condition (class_exists( RuleQuery::class )<\/code>). Because both gates degraded in the same direction, a single dependency failure \u2014 composer breakage, autoloader race on rest_api_init<\/code>, missed dependency after site clone, vendor package rename \u2014 collapsed the entire two-gate stack, letting every authenticated user reach every tool on every server. 0.2.8 inverts F042's missing-vendor branch to return 'manage_options'<\/code> instead. Paired with F015's fail-open on the same condition, the stack now degrades to admin-only<\/strong> rather than \"wide open to every logged-in user\" when the vendor library is missing. Class docblock on TransportPermissionDefault<\/code> explicitly documents the intentional asymmetry \u2014 \"F015 fails open + F042 fails closed = admin-only when the vendor breaks\" \u2014 so the invariant survives future refactors. The class_exists()<\/code> call is now behind a protected has_access_control_library()<\/code> seam to enable direct test coverage (tests\/phpunit\/Includes\/AccessControl\/TransportPermissionMissingVendorTest.php<\/code>).\n\n\n- Operator action<\/strong>: none in the healthy-vendor case (Composer install intact). If your deploy pipeline can produce a state where
vendor\/wpboilerplate\/access-control<\/code> is absent, non-admin MCP traffic will now receive 401 instead of full access. Restore the vendor package and MCP endpoints resume normal per-rule enforcement.<\/li>\n<\/ul><\/li>\n- Admin \u2014 Server list at
?page=acrossai_mcp_manager<\/code> redesigned for a tighter, more actionable layout.<\/strong> Column changes: removed<\/strong> Slug (redundant with the Route\/Route Namespace columns and the Name column's inline edit link), Route Namespace + Route merged<\/strong> into a single Route<\/code> column displayed as <namespace>\/<route><\/code> with duplicate slashes at the join collapsed, removed<\/strong> Version (still surfaced on the per-server-edit Overview tab). Final column order: \u2610 | Name | Status | Registered From | Route | Actions<\/code>. Actions column extended<\/strong> \u2014 the existing Enable\/Disable toggle is now bundled with 5 quick-access buttons: Edit<\/strong> (primary-styled) links to the server-edit page, and four per-tab quick-links (Connectors<\/strong>, Access Control<\/strong>, Abilities<\/strong>, MCP Clients<\/strong>) jump directly to the corresponding tab on the edit page. Quick-links render as subtle rounded pill-badges with a dashicon prefix (dashicons-admin-plugins<\/code> \/ dashicons-shield<\/code> \/ dashicons-superhero-alt<\/code> \/ dashicons-admin-users<\/code>) \u2014 lighter than full buttons but more scannable than plain text links. New .acrossai-actions-cell<\/code> flex wrapper in src\/scss\/backend.scss<\/code> keeps the button cluster wrapping cleanly on narrow viewports; Status + Registered From columns capped at 120px so the freed horizontal space flows to Route + Actions. Preserves the existing per-row nonce on the Enable\/Disable toggle. No DB or REST changes.<\/li>\n- UI \u2014 AI Connectors tab renamed to \"Connectors\/Integrations\".<\/strong> The per-server-edit tab label at
?page=acrossai_mcp_manager&action=edit&server=<id>&tab=ai-connectors<\/code> now reads Connectors\/Integrations<\/strong> instead of \"AI Connectors\". Tab slug (ai-connectors<\/code>) is intentionally unchanged so the last-wins tab-registration override from the acrossai-ai-connectors<\/code> companion plugin keeps landing on the same placeholder \u2014 no companion-plugin coordination required. AiConnectorEmbedTransport::label()<\/code> (a separate F037 embed transport) is left as-is; only the per-server-edit tab label is affected.<\/li>\n- Internal:
ACROSSAI_MCP_MANAGER_VERSION<\/code> constant + Stable tag<\/code> bumped to 0.2.8<\/code> matching the plugin header.<\/strong><\/li>\n<\/ul>\n\n0.2.7<\/h4>\n\n\n- Docs \u2014 Fixes for the WordPress.org plugin import.<\/strong> Trimmed the
Tags:<\/code> header from 8 tags to 5 (mcp, ai, claude, chatgpt, cursor<\/code>) \u2014 WordPress.org silently drops any tag past the fifth; the surplus (copilot<\/code>, vscode<\/code>, gemini<\/code>) never showed up in the plugin listing anyway. Condensed the changelog for versions prior to 0.2.0<\/code> into a single \"Earlier versions\" pointer to the GitHub Releases page so the full changelog stays under WordPress.org's 5,000-word cap (previously ~8,258 words \u2192 the older entries were truncated on import and never rendered on the plugin page). Same information, still discoverable \u2014 just hosted on GitHub instead of duplicated in README.txt<\/code>.<\/li>\n- Internal: