Cursor plugins

The Cursor plugin specification and official plugins: skills, rules and MCP for workflows and third-party services

  • 14,580 ★ on the repository
  • Last commit
Plugin

Broad access

Why this level

  • Integrations write to external systems: email, CRM, repositories
  • Some plugins access financial accounts
All reasons and checks

cursor/plugins

Install

Works in

In your terminal, with SkillFoxx CLI

npx skillfoxx add plugins/cursor-plugins

Detects the agents on your machine, shows the access level and pins the version.

Other ways to install

Access and checks

How we review

Broad accessThe tool can change data, run commands or handle secrets.

  • Integrations write to external systems: email, CRM, repositories
  • Some plugins access financial accounts

This is third-party code. Review the repository files before installing.

What it does

The repository is a Cursor plugin marketplace. Each plugin lives in its own folder with a .cursor-plugin/plugin.json manifest and can contain skills, .mdc rules and MCP server definitions. First-party plugins include deep branch review, parallel cloud agents, plugin scaffolding and the Cursor SDK. A separate group connects third-party services: GitHub, Playwright, Gmail, Google Drive, HubSpot, Salesforce, BigQuery and more.

Who it is for. For Cursor users and authors who want to build a plugin following the official layout.

Good fit when

  • You want to connect a third-party service to Cursor with a ready plugin
  • You want a reference layout for a Cursor plugin
  • You need ready review and agent orchestration workflows

Not a fit when

  • You do not use Cursor
  • The services you need are unavailable in your country

Example request

Do a deep security and correctness review of the current branch

Limitations

Plugins target Cursor 2.x. Most integrations require accounts in third-party services, many of which are unavailable or restricted in Russia. Cursor itself has limitations in Russia.

How to disable. Disable or remove the plugin in the Plugins section of Cursor settings.

FAQ

What does a plugin consist of?

A plugin.json manifest plus optional skills and rules folders, an mcp.json file, README and CHANGELOG.

Where is the full plugin list?

In the root .cursor-plugin/marketplace.json file.

Discussion

No questions or reviews yet.

Plugins

A Claude Code plugin marketplace: slash commands, subagents, MCP servers and hooks installed with /plugin

PluginExtended access990Repository stars

A large Claude Code plugin and skill marketplace with the ccpi CLI and a category-based catalog site

PluginExtended access2.9KRepository stars

A CLI and MCP server for Agent Skills: spec validation, installs from GitHub and on-demand loading of the right skill

CLIExtended access418Repository stars
Editors’ pick

Anthropic's plugin marketplace for Claude Code: in-house plugins plus vetted third-party ones, installed via /plugin

PluginExtended access45.2KRepository stars

A large kit for Claude Code: subagents, skills, commands, hooks, rules, templates and MCP configs in one plugin marketplace

PluginExtended access2.8KRepository stars

Knowledge-graph memory for agents: Claude Code and Codex plugins, an MCP server and a Python library

PluginExtended access32.9KRepository stars

README in short

The README has a table of all plugins with author, category and marketplace description. Plugins split into Cursor developer tools and third-party integrations in the third_party folder. It describes the marketplace repository layout and a single plugin's structure. MIT licensed.

README badge

Report a problem

Foxx AICursor plugins
Foxx AI

I am Foxx AI and I have already vetted this tool. Ask about install, setup or anything else, and I will keep it simple.