cursor/community-plugins

What it solves

This project provides the infrastructure for the Cursor Directory, a centralized hub where developers can discover, share, and manage community-built extensions and tools for the Cursor AI code editor. It solves the problem of fragmented plugin discovery by providing a standardized way to submit and verify components like MCP servers, custom rules, and AI agents.

How it works

The project is a Next.js web application backed by a Supabase PostgreSQL database. Users submit plugin repositories via the website, which then uses an automated pipeline to scan the content for security risks using a Cursor SDK agent. The system includes an administrative interface accessible via an MCP (Model Context Protocol) server, allowing moderators to manage, verify, or block plugins directly from within the Cursor editor.

Who it’s for

This is for developers who want to contribute to the Cursor ecosystem and for administrators responsible for moderating and securing the community plugin directory.

Highlights

• Automated Security Scanning: Uses an AI agent to perform asynchronous security audits on submitted plugins.
• MCP-Powered Moderation: Allows admins to moderate the directory using tools exposed through an MCP server, enabling direct management from the Cursor editor.
• Standardized Specification: Supports various component types including MCP servers, custom rules, and AI agents following the Open Plugins standard.
• Modern Tech Stack: Built with Next.js, Bun, and Supabase, utilizing Supabase Queues for robust background processing of security scans.