Skip to content
Cursor expands team marketplaces with Team MCPs and organization groups | My AI Guide

Cursor expands team marketplaces with Team MCPs and organization groups

By Harsh Desai
Share

TL;DR

Cursor expanded team marketplaces to support Team MCPs and organization groups. Admins configure servers once for distribution across agents, IDE, and CLI with group restrictions.

What changed

Cursor expanded its team marketplaces to include Team MCPs and organization groups. Admins configure Team MCP servers once for distribution across cloud agents, the IDE, and CLI. Marketplace access gets restricted to specific organization groups for Vibe Builders, Basic Users, and Developers.

Why it matters

Vibe Builders and Developers gain from centralized setup that applies across multiple environments, cutting repeated configurations in team workflows. Basic Users see easier access controls similar to how Notion organizes team spaces with group restrictions.

What to watch for

Compare the approach against alternatives like Zed editor team features. Verify by checking admin settings in your Cursor organization dashboard for the new MCP options.

Who this matters for

  • Vibe Builders: Centralize your custom MCP servers once to sync tools across your team's IDE and cloud agents.
  • Developers: Use organization groups to manage access to internal MCP servers and CLI tools at scale.

Harshs take

Cursor is doubling down on the Model Context Protocol (MCP) as the standard for enterprise AI extensibility. By allowing admins to configure servers once for distribution across the IDE, CLI, and cloud agents, they are removing the friction of manual environment syncing. This move signals that the IDE is no longer just a text editor: it is becoming a managed platform for team-wide AI capabilities.

The addition of organization groups for marketplace access mirrors the permission structures found in mature SaaS tools like Notion. This is a necessary evolution for Cursor to move from individual developer seats to large-scale corporate deployments. If you are building internal tools, focus on MCP compatibility.

It is clearly the winning architecture for connecting private data and custom APIs to the coding environment.

by Harsh Desai

Source:cursor.com

About Cursor

View the full Cursor page →All Cursor updates

Go deeper

More from Cursor

Everything AI. One email.
Every Monday.

New tools. Model launches. Plugins. Repos. Tactics. The moves the sharpest builders are making right now, before everyone else.

No spam. Unsubscribe anytime.