Connection Hub: one Cursor login for every client workspace

Consultants, agencies, and platform teams often run separate Opsphere tenants per client — and switching between IDE logins breaks flow during incidents. Connection Hub is a first-party Opsphere platform capability, not a vendor integration: it links multiple client workspaces to one Cursor session through OAuth so you stay in the same IDE while changing operational context.

Link client tenants with ops_account_link_start, open a server-side work context with ops_context_open, and run operational tools scoped by context_id. The gateway resolves credentials server-side — nothing sensitive lands in IDE configuration. Plugin skills link-account and open-work-context guide onboarding; MCP resources opsphere://hub/connections and opsphere://hub/active-context expose connection state to agents.

Hub installations cannot configure integrations or run operational tools without an active work context. Grants are encrypted at rest. The release adds five broker control-plane tools to the gateway catalog; Cursor integration copy on the site now describes Connection Hub alongside the existing official plugin workflow.