# MCP server packages on npm with weekly downloads

**Use case:** 

Searches npm for Model Context Protocol (MCP) server packages and returns name, description, latest version, publish date, repository, and weekly and monthly download counts. Run it weekly to see which MCP servers are gaining users.

## Input

```json
{
  "packages": [
    "crawlee",
    "puppeteer"
  ],
  "searchQueries": [
    "mcp server"
  ],
  "includeDownloads": true,
  "maxItems": 50,
  "incremental": false,
  "outputFormat": "json",
  "requestDelayMs": 500
}
```

## Output

```json
{
  "name": {
    "label": "name"
  },
  "version": {
    "label": "version"
  },
  "weeklyDownloads": {
    "label": "weeklyDownloads"
  },
  "license": {
    "label": "license"
  },
  "repository": {
    "label": "repository"
  },
  "url": {
    "label": "url",
    "format": "link"
  }
}
```

## How it works

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

The npm Package Scraper – Downloads & Dependencies Actor is ready to run with the inputs already set for "MCP server packages on npm with weekly downloads". [Sign up or log in](https://console.apify.com/create-task-from-example/L1vnOApeKcoMA55xz) and you'll land in Apify Console with a copy of this exact task.

### 2. Start the "MCP server packages on npm with weekly downloads" task

The npm Package Scraper – Downloads & Dependencies Actor will start running based on the input automatically. You can also change all the input fields, like package names, search queries, and more, to match your specific use case.

### 3. Receive the "MCP server packages on npm with weekly downloads" 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, version, weeklydownloads, 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 "MCP server packages on npm with weekly downloads" task via API](https://apify.com/devteamdrew/npm-package-scraper.md).

## FAQ

### What does the MCP server packages task return?

npm packages matching "mcp server": name, description, latest version, publish date, repository link, and weekly and monthly downloads from the npm downloads API.

### Can I search for other packages?

Yes. Change Search queries, for example "langchain" or "vite plugin", or list exact package names instead.

### Does it need an npm token?

No. It uses the public npm registry search and downloads APIs.

## About this Actor

This example demonstrates how to use [npm Package Scraper – Downloads & Dependencies](https://apify.com/devteamdrew/npm-package-scraper.md) with a specific input configuration. Visit the [Actor detail page](https://apify.com/devteamdrew/npm-package-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/devteamdrew/npm-package-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`).
