Platform Update
Cursor expands team marketplaces with MCP servers and org group access
Cursor's team marketplaces now allow admins to configure MCP servers once and deploy them across multiple surfaces, while organization groups can limit marketplace access beyond SCIM directory groups.

Cursor, the AI-powered code editor, is rolling out two significant updates to its team marketplace system: support for MCP (Model Context Protocol) servers at the team level and the ability to restrict marketplace access by organization group.
MCP servers for teams
Administrators can now configure MCP servers once and deploy them across Cursor's Agent Cloud, Agent window, IDE, and CLI. When an admin sets up team MCP servers for Agent Cloud, those same servers become available in a team marketplace under Dashboard to Integrations & MCP.
Team members can install approved integrations locally without having to configure the servers themselves, reducing friction while maintaining organizational guardrails.
Cursor has published migration documentation for teams that already use MCP servers and want to move them under the new team marketplace model.
Organization group filtering
Team marketplaces now support organization groups in addition to SCIM directory groups at the team level. Under Dashboard to Plugins to Team Marketplaces, administrators can limit marketplace access to specific organization groups. Marketplaces already using SCIM directory groups will retain that configuration.
The changes give larger organizations more granular control over which integrations reach which developers, a common request as Cursor gains adoption in enterprise settings.
The new features are available immediately from the Cursor dashboard.