OAuth DCR — auto-bind to the advertised default server (multi-server sites)
Real MCP hosts (Claude.ai, Grok, ChatGPT, Cursor) do NOT send an RFC 8707 resource parameter in Dynamic Client Registration bodies — RFC 7591 does not carry that field; resource is only an authorize/token concept. The 0.8.0 DCR handler required resource on any site with 2+ MCP server rows and returned 400 invalid_target when the client omitted it. Real clients hit this instantly and surfaced a generic client-side "Couldn't register" / "Unable to authorize app" error, with no WP debug.log signal because DCR returns 4xx JSON, not a PHP error.
DiscoveryController::default_server_row() is now the single source of truth for "the default MCP server for anonymous clients". ClientRegistrationController::handle_register() auto-binds unresolved DCR requests to that same row, so DCR and .well-known/oauth-protected-resource stay in lock-step. Existing admin-generated clients (with an explicit server_id) are unaffected.
Captured as durable memory:
- B8 — the failure mode + prevention guidance.
- A7 — the invariant.
See PR #35.
Discovery — contribute AI-connector DTOs via filter-inversion (paired with mcp-manager)
Adds DiscoveryConnectorAdapter bound to the acrossai_mcp_manager_discovery_ai_connectors filter. Reads every registered ConnectorProfile from the local registry and emits one DTO per profile under the ai_connector category. Replaces the pre-0.8.0 class_exists probe on this plugin's namespace root that mcp-manager relied on to discover profiles — that probe broke when the namespace renamed from AcrossAI_AI_Connectors to AcrossAI_Pro in 0.8.0 (D10 hard-break). Filter-inversion is the BC-safe replacement: mcp-manager fires the filter unconditionally; this plugin contributes DTOs when premium code is active (Freemius gating enforced upstream in the acrossai_pro_profiles filter — unlicensed installs contribute zero DTOs). Requires a paired acrossai-mcp-manager release that fires the filter; ships dormant on older mcp-manager.
See PR #36.
Upgrade notes
- Drop-in replacement for 0.8.0. No schema change, no data migration.
- Immediate benefit for multi-server installs where 0.8.0's DCR was rejecting real MCP hosts.
- Discovery adapter is a no-op until the paired mcp-manager release lands — safe to install now.