cursor.directory APIcursor.directory ↗
Access cursor.directory plugins, MCP servers, categories, and job listings via API. Filter rules by type, category, or keyword across 6 endpoints.
curl -X GET 'https://api.parse.bot/scraper/16f978a9-29ef-4c43-8bcc-a2eb5b380365/list_rules?query=react' \ -H 'X-API-Key: $PARSE_API_KEY'
Returns all plugins (rules, MCP servers, and combined) from the cursor.directory plugins page. Supports filtering by search query and plugin type. The site has restructured from separate rules/MCPs to unified 'plugins' with a type field.
| Param | Type | Description |
|---|---|---|
| sort | string | Sort/tag filter passed to the site. Accepted values: 'popular', 'mcp'. |
| type | string | Filter by plugin type. Accepted values: 'rules' (rules only), 'mcp' (MCP servers only). Omitting returns all types including 'both'. |
| query | string | Search query to filter plugins by name, description, or keywords. |
{
"type": "object",
"fields": {
"data": "array of plugin objects with name, slug, description, type, logo, keywords, rules_count, mcp_count, install_count, href"
},
"sample": {
"data": [
{
"href": "/plugins/nextjs",
"logo": "https://service.cursor.directory/storage/v1/object/public/avatars/plugins/lpafu02k54.png",
"name": "Next.js",
"slug": "nextjs",
"type": "rules",
"keywords": [
"nextjs",
"react"
],
"mcp_count": 0,
"description": "Next.js rules and best practices for Cursor",
"rules_count": 9,
"install_count": 35300
}
],
"status": "success"
}
}About the cursor.directory API
The cursor.directory API provides 6 endpoints for querying AI editor plugins (cursor rules and MCP servers), categories, and job listings from cursor.directory. The list_rules endpoint returns all plugins with fields like install_count, type, keywords, and slug, and accepts filters for plugin type and search query. Developers can drill into individual plugins via get_rule_detail to retrieve full rule content text.
Plugins and Rules
The list_rules endpoint returns every plugin in the directory as an array of objects. Each object includes name, slug, description, type (either rules, mcp, or both), logo, keywords, rules_count, mcp_count, install_count, and href. You can narrow results using the query parameter for keyword search, the type parameter to filter to rules-only or MCP-only entries, or the sort parameter to surface popular or MCP-tagged plugins. The list_rules_by_category endpoint accepts a category string and matches it case-insensitively against each plugin's name, keywords array, and description text.
Plugin Detail and Categories
get_rule_detail takes a slug (obtainable from any listing endpoint) and returns the full rule content text along with title, description, and tags. This is the endpoint to use when you need the actual cursor rule instructions rather than summary metadata. list_categories requires no inputs and returns every category keyword aggregated across the directory, each with a name, slug, and count reflecting how many plugins use that keyword — useful for building navigation or discovering popular tech stacks.
MCP Servers
list_mcps is a dedicated endpoint for Model Context Protocol servers. It filters the plugin set to entries with type mcp or both and supports query for search, limit for result count, and offset for pagination. Each result includes name, slug, description, logo, keywords, install_count, and href. This makes it straightforward to build MCP server discovery tools without manually filtering the full plugin list.
Job Listings
list_jobs returns job listings posted to cursor.directory, with each entry containing title, company, location, and link. The endpoint takes no inputs and returns all available listings. This covers roles typically posted in the AI developer tools space.
- Build a CLI tool that searches cursor rules by language or framework using the
queryparam onlist_rules - Generate a ranked list of the most-installed MCP servers using
install_countfromlist_mcps - Populate a rules browser UI with category-filtered plugins via
list_rules_by_category - Extract and store full cursor rule content from
get_rule_detailfor offline use or analysis - Aggregate category coverage stats using the
countfield fromlist_categories - Monitor new job listings in the AI developer tools space via
list_jobs - Build a recommendation engine that maps tech stack keywords to relevant plugins using
keywordsfields
| Tier | Price | Credits/month | Rate limit |
|---|---|---|---|
| Free | $0/mo | 100 | 5 req/min |
| Hobby | $30/mo | 1,000 | 20 req/min |
| Developer | $100/mo | 5,000 | 250 req/min |
One credit = one API call regardless of which marketplace API you call. Exceeding the rate limit returns a 429 response. Authenticate with the X-API-Key header.
Does cursor.directory have an official developer API?+
How does `list_rules` differ from `list_mcps`?+
list_rules returns all plugin types (rules, MCP servers, and combined entries) and can be filtered with the type parameter. list_mcps is narrower — it returns only entries with type mcp or both and adds limit and offset parameters for pagination, which list_rules does not expose.Does `get_rule_detail` return all code blocks on a plugin page, or just the first?+
content field. You can fork this API on Parse and revise the endpoint to capture additional code blocks if your use case requires them.Are user reviews, ratings, or comment threads for plugins available?+
Can I filter job listings by location type or company?+
list_jobs returns all listings without filtering parameters. Each job object includes location and company fields, so client-side filtering is possible. The endpoint does not currently accept query or filter inputs. You can fork the API on Parse and revise it to add server-side filtering on those fields.