Summary
Cursor expanded its team marketplaces so admins can configure MCP servers once and distribute them across cloud agents, the agents window, the IDE, and the CLI. Team members can then install approved integrations locally without configuring servers themselves, and admins can restrict marketplace access to specific organization groups in addition to SCIM directory groups.
What changed
Cursor's team marketplaces now support centrally managed Team MCP servers distributed across all Cursor surfaces, plus access scoping by organization groups alongside existing SCIM directory groups.
Why it matters
It moves MCP configuration from per-developer setup to governed, admin-curated distribution, which is what enterprises need to roll out approved agent tools at scale without each engineer wiring servers by hand or bypassing controls.
Evidence excerpt
Admins can now configure Team MCP servers once and distribute them across cloud agents, the agents window, IDE, and CLI.