Cursor expands team marketplaces with Team MCPs and organization groups
TL;DR
Cursor enables admins to configure Team MCP servers once for distribution across cloud agents, the IDE, and CLI. Team marketplaces now support access restrictions by organization groups.
What changed
Admins can configure Team MCP servers once for distribution to cloud agents, the IDE, and CLI. Team marketplaces now allow access restrictions using organization groups. This reaches Developers managing shared tools, Vibe Builders customizing team flows, and Basic Users accessing restricted options.
Why it matters
Vibe Builders benefit when setting up consistent environments for their groups because one config covers multiple access points. In a use case with Developers on organization teams, this avoids duplicate work seen in competitors like VS Code extensions. Basic Users notice cleaner marketplace views limited to their groups.
What to watch for
Compare the group restrictions against alternatives such as standard marketplace setups in other IDEs. Verify the changes by logging into the Cursor admin dashboard and testing a Team MCP server distribution to the CLI.
Who this matters for
- Vibe Builders: Configure a Team MCP server once to sync custom workflows across your team's IDE and CLI tools.
- Developers: Use organization groups to manage tool access and eliminate redundant setup across cloud agents.
Harsh’s take
Cursor is aggressively solving the distribution problem for the Model Context Protocol. By allowing admins to push MCP server configs across the IDE, CLI, and cloud agents simultaneously, they are removing the friction that usually kills team-wide tool adoption. This is a direct hit to VS Code's fragmented extension model where every dev manages their own environment.
The addition of organization groups for marketplace access shows Cursor is maturing into an enterprise-grade platform. It allows for granular control over which teams see which internal tools, preventing marketplace clutter. Operators should move their custom internal data connectors to Team MCPs now to ensure environment parity across the entire engineering org.
by Harsh Desai
About Cursor
View the full Cursor page →All Cursor updatesGo deeper
More from Cursor
- FeatureCursor adds running and managing cloud agents in the Agents Window
Cursor enables running and managing cloud agents in the Agents Window. Users can set up isolated cloud environments in under 10 minutes and switch sessions with /in-cloud.
- FeatureCursor adds /automate skill and triggers for task automation
Cursor users can create automations with the /automate skill. Workflows now trigger via Slack emojis or five new GitHub events, and cloud agents can use virtual computers for demos.
- FeatureCursor adds Customize page and plugin canvases
Cursor's new Customize page centralizes management of plugins, skills, and MCPs. It adds a marketplace leaderboard, prebuilt canvases, and GitLab or Bitbucket imports for team marketplaces.