Cursor Team Marketplace (May 1, 2026): First-Party Plugin Controls Without a Repo

Cursor shipped a Team Marketplace update on May 1, 2026 that makes it easier for orgs to standardize agent tooling without repo-level setup. The headline: admins can now create a team marketplace without connecting a repository first, then centrally manage installation policies for first-party plugins.

TL;DR

• Create a Cursor team marketplace without a repo connection.
• Configure install behavior for first-party plugins directly in marketplace settings.
• Cursor plugins can bundle agent extensions like MCP servers, skills, subagents, rules, and hooks.

What Actually Shipped

According to Cursor's official changelog entry for May 1, 2026:

• Marketplace setup without a repository: admins can create a team marketplace even if they haven't connected a repo yet.
• Centralized first-party plugin controls: admins can add, remove, and configure install behavior for Cursor's first-party plugins.
• Distribution policies: each plugin can be configured as:
  1. Default Off (discoverable and opt-in)
  2. Default On (installed by default, but removable)
  3. Required (installed and not removable)

Why This Matters for Agent Workflows

Cursor is treating plugins as a packaging format for agent capabilities. In the same changelog entry, Cursor says plugins can bundle:

• MCP servers
• Skills
• Subagents
• Rules
• Hooks

If you're rolling out agentic coding across a team, these controls are a practical way to:

• Keep tool access consistent across developers
• Reduce "it works on my machine" drift in agent setups
• Standardize safety defaults (for example, requiring specific hooks or rules)

Source

• Cursor changelog: Team Marketplace Updates (May 1, 2026): https://cursor.com/changelog/05-01-26