directories
Cursor Directory is a community hub website where users submit and browse Cursor-related content (plugins, MCP servers, rules, skills, agents, hooks, LSP servers), plus supporting features like events and jobs. It is backed by a Supabase database and is implemented as a Next.js app.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
The README indicates usage of Supabase service role key and a Resend API key (optional). It provides an .env setup approach, but does not describe operational security practices (e.g., server-side handling, rotation, logging redaction) or how the service role key is safeguarded. No security headers, CSP, or API auth/scoping details are provided in the supplied content.
⚡ Reliability
Best When
You want a community-driven catalog of Cursor assets and can integrate via the website UI or by interacting with the underlying Supabase-backed system through its app (not described via public APIs in the provided content).
Avoid When
You need a documented REST/GraphQL API, strict API rate-limit guarantees, or a clearly specified authentication model for third-party integrations.
Use Cases
- • Discovering Cursor plugins and related assets (MCP servers, rules, skills, agents, hooks, LSP servers)
- • Submitting new plugins by providing a repository URL that is auto-detected against an Open Plugins standard
- • Hosting and listing community events
- • Posting and browsing jobs for Cursor/AI development work
Not For
- • A general-purpose API for programmatic retrieval of directory entries (no API details provided here)
- • A self-hosted alternative where you can manage local/offline datasets (README states all data lives in the database)
- • A managed, SLA-backed enterprise data platform
Interface
Authentication
Auth is described at a UX level for submitting content (sign in with GitHub or Google), but no API auth scheme, scope model, or token flow is documented in the provided content.
Pricing
No pricing information is provided in the supplied README content.
Agent Metadata
Known Gotchas
- ⚠ No documented programmatic interface (REST/GraphQL/SDK) is provided in the supplied content, so agents cannot reliably automate discovery/submission beyond UI/manual steps.
- ⚠ Readme does not specify API error formats, rate limiting headers, or retry/idempotency semantics for automated ingestion.
- ⚠ Authentication details for programmatic use (token endpoints/scopes) are not documented.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for directories.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-29.