# Extract Cursor Directory MCP Servers & AI Plugins

**Use case:** 

This task retrieves remote Model Context Protocol (MCP) server endpoints and AI coding plugins from the Cursor Directory. You will receive structured data, including official homepage URLs, GitHub repositories, and category tags, presented in clean JSON or CSV formats. Ideal for developers and sales teams looking to access specific AI tools quickly.

## Input

```json
{
  "keywords": [
    "mcp",
    "python",
    "nextjs"
  ],
  "maxItems": 30
}
```

## Output

```json
{
  "name": {
    "label": "name",
    "format": "string"
  },
  "slug": {
    "label": "slug",
    "format": "string"
  },
  "itemType": {
    "label": "itemType",
    "format": "string"
  },
  "description": {
    "label": "description",
    "format": "string"
  },
  "mcpEndpointOrConfig": {
    "label": "mcpEndpointOrConfig",
    "format": "string"
  },
  "homepageUrl": {
    "label": "homepageUrl",
    "format": "string"
  },
  "githubSourceUrl": {
    "label": "githubSourceUrl",
    "format": "string"
  },
  "tags": {
    "label": "tags",
    "format": "string"
  },
  "cursorDirectoryUrl": {
    "label": "cursorDirectoryUrl",
    "format": "string"
  }
}
```

## How it works

### 1. Sign up on Apify or log in

The Cursor Directory Scraper — Plugins, MCPs, Rules & AI Leads Actor is ready to run with the inputs already set for "Extract Cursor Directory MCP Servers & AI Plugins". [Sign up or log in](https://console.apify.com/create-task-from-example/WK15FSy0iveKD8Rqp) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "Extract Cursor Directory MCP Servers & AI Plugins" task

The Cursor Directory Scraper — Plugins, MCPs, Rules & AI Leads Actor will start running based on the input automatically. You can also change all the input fields, like search keywords or tech stack (e.g., mcp, python, nextjs, supabase) and max plugins / mcps / rules to extract, to match your specific use case.

### 3. Receive the "Extract Cursor Directory MCP Servers & AI Plugins" output

Monitor the progress in real time. You will be notified as soon as your dataset is complete and ready for review. Each result includes data such as name, slug, itemtype, and more.

### 4. Integrate into your workflow

The final output is delivered in JSON, CSV, or Excel format, ready to be plugged into your workflow. You can also [run the "Extract Cursor Directory MCP Servers & AI Plugins" task via API](https://apify.com/mehdad-datalabs/cursor-directory-plugins-mcp-rules-b2b-scraper.md).

## FAQ

### What data does this task extract from the Cursor Directory?

The Extract Cursor Directory MCP Servers & AI Plugins task extracts plugins, remote MCP server endpoints, AI rules, skills, homepage URLs, GitHub repositories, and category tags.

### What is the maximum number of items this task can extract?

The task is configured to extract a maximum of 30 items from the Cursor Directory.

### Does this task require a Cursor account?

No, this task extracts publicly accessible data without needing a Cursor account.

### Can I run this task using the Apify API?

Yes, this task can be run via the Apify API by calling the Actor with the appropriate input parameters.

### What file formats can the output data be in?

The extracted data can be returned in JSON, CSV, or Excel formats.

### How much does it cost to run this task?

Costs for running this task follow Apify's usage-based pricing, with specific charges for actor startup and extracted items.

## About this Actor

This example demonstrates how to use [Cursor Directory Scraper — Plugins, MCPs, Rules & AI Leads](https://apify.com/mehdad-datalabs/cursor-directory-plugins-mcp-rules-b2b-scraper.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/mehdad-datalabs/cursor-directory-plugins-mcp-rules-b2b-scraper.md) to learn more, explore other use cases, and run it yourself.


## How to integrate an Actor?

This Task's input is already configured above. Use it as-is rather than inventing a new one.

Do not guess an integration path. Every one of them is in the agent quickstart at https://apify.com/agents.md: the Apify MCP server, Agent Skills with the Apify CLI, the JavaScript and Python clients, the REST API, and the account-free path for an agent with no human to sign in. It also carries the rule on stating cost before the first paid run.

For full API examples (JavaScript, Python, CLI, MCP, OpenAPI), see this Task's Actor page: https://apify.com/mehdad-datalabs/cursor-directory-plugins-mcp-rules-b2b-scraper.md

Each client library has reference documentation the quickstart does not restate: [JavaScript/TypeScript](https://docs.apify.com/api/client/js/docs.md) (`npm install apify-client`) and [Python](https://docs.apify.com/api/client/python/docs.md) (`pip install apify-client`).
