Command reference ยท Cursor CLI
/plugin
Manages plugins and plugin marketplaces.
/plugin manages plugins and plugin marketplaces directly from within the Cursor CLI session: view installed plugins, browse the marketplace, and install or uninstall plugins. According to the code, short forms available are /plugin list (show installed plugins and marketplace) as well as /plugin marketplace list and /plugin marketplace add <git-url> (register a new marketplace via a git URL). Loaded plugins automatically bring their own skills, slash commands, subagents, and MCP servers into every new session, as soon as they're activated in the chosen scope (user or project), without needing to be loaded manually again afterward.
For automation without an interactive session, there are additionally standalone agent plugin marketplace subcommands outside the chat: add <git-url> --git-ref <branch>, list (with --format json for scripts), update <name>, and remove <name>. These scriptable CLI subcommands are distinct from /plugin within a running conversation, even though both ultimately manage and can read the same underlying marketplace data.
โ WHEN TO USE IT?
Register a team marketplace via script
agent plugin marketplace add https://github.com/team/cursor-plugins --git-ref main
Install a plugin only for this one project
/plugin โ select a plugin, set scope to 'Project'
โ WHEN NOT TO?
Just testing a locally located plugin directory, without a marketplace
The detour via a marketplace entry isn't necessary for that.
Better: Use --plugin-dir <path> at CLI startup
Plugins should be centrally mandated for the whole team
/plugin is the local, interactive management per user and session.
Better: Manage the team marketplace centrally via the Cursor dashboard (Team Marketplaces)
SOURCES
- Cursor Docs โ Slash Commands โ cursor.com