NetEase Cloud Music Song, Chart & Playlist Scraper: MCP config, n8n workflow and API

NetEase Cloud Music songs, albums, artists, playlists, chart summaries, comments and lyrics metadata.

Fastest route, in Claude Code:

claude mcp add --transport http netease-cloud-music-song-chart-and-playlist "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/netease-cloud-music-song-chart-and-playlist"

One click, signs in with Apify on first use:

Any other client, one command (writes the config for 25+ agents, including Windsurf, Zed, Cline and Goose):

npx add-mcp "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/netease-cloud-music-song-chart-and-playlist" --name netease-cloud-music-song-chart-and-playlist

Every file on this page is generated from the Actor's published schema: 51 of 51 checks pass (validated, not run)
  • MCP configs: 7 of 7 (Uses Apify's hosted MCP endpoint over HTTPS; The tools parameter lists exactly the chosen Actors as owner/name; JSON configs parse and use the client's top-level key and the same URL; Codex TOML has a [mcp_servers.<name>] table with url and bearer_token_env_var; CLI commands quote the same URL and use the streamable HTTP transport; One-click install links decode back to the same URL and carry no token; Only placeholders, no real token)
  • n8n workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • long-run workflow: 11 of 11 (It has a nodes array and a connections object; Every node has a name, type, typeVersion, position and parameters; Node names are unique; Every node type is a known n8n core node (or the Apify node); Every node uses a typeVersion that n8n ships; Every connection points at an existing node; At least one trigger starts the workflow; Every working node is reachable from a trigger; Apify calls use POST and a credential for the token; Actor input matches the Actor's published input schema; No token or credential value is embedded)
  • example input: 5 of 5 (All 1 required input field is present; Every input key exists in the published input schema; Every value has the type the schema declares; Every choice field uses one of its published options; Numbers respect the published minimum and maximum)
  • code snippets: 4 of 4 (curl calls the documented run-sync-get-dataset-items endpoint for this Actor; Python (apify-client 3.x typed Run) and JavaScript use the official apify-client call() then read the run's dataset; Multi-line shell commands continue every line with a backslash; Token read from APIFY_TOKEN, none embedded)
  • SKILL.md: 13 of 13 (SKILL.md starts with YAML front matter; name is 1-64 lowercase letters, digits and single hyphens; name matches the skill folder name; description is present, at most 1024 characters and has no angle brackets; front matter uses only spec fields; compatibility is at most 500 characters; body has instructions; field descriptions end on whole sentences; no credential values are embedded; the token is read from APIFY_TOKEN; the run command calls this Actor's run-sync endpoint; the example input is valid JSON; the example input matches the published input schema)

What the checks cover

What a run costs

Every run pays a start fee plus a price per result. On the Free plan this Actor's start fee is $0.40 (the start event, $0.10 per GB, times its default 4 GB of memory), $0.12 on Business; results cost $0.99 per 1,000 results (pay per event). Checked 2026-11-12.

Results in one runStartResultsRun total
10$0.40$0.010$0.41
100$0.40$0.10$0.50
1,000$0.40$0.99$1.39

Plus Apify platform usage for the run, which the caller pays. A smaller memory setting lowers the start fee if the Actor still finishes. Prices can change; the Store pricing tab is the source of truth.

MCP config

One URL works in every client: https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/netease-cloud-music-song-chart-and-playlist. It exposes this Actor as a tool, plus fetch-actor-details so the agent can read the input schema before calling it. Pick your client:

Claude Code configterminal or .mcp.json

claude mcp add --transport http netease-cloud-music-song-chart-and-playlist "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/netease-cloud-music-song-chart-and-playlist"

Run the command in your project folder. Add --scope user to make it available in every project. Full Claude Code setup

Tools your agent gets

Listed by Apify's MCP server 0.21.5 for this exact URL on 2026-11-11 (a tools/list call; nothing was run).

  • fetch-actor-detailsreads the input schema
  • dataspryva--netease-cloud-music-song-chart-and-playlistruns the Actor and returns its results
  • get-actor-runchecks a run's status
  • get-dataset-itemsreads a run's results
  • get-key-value-store-recordreads a stored record such as a file or summary
  • abort-actor-runstops a run that is still going

n8n workflow

A manual and a daily trigger call the Actor through the HTTP Request node with your Apify token, then hand each record to the destination you pick. The Actor input sits in the request body, already filled with the example below.

Send the records to
  • Run by hand
  • Every day
  • Run Apify Actor

n8n workflownetease-cloud-music-song-chart-and-playlist.n8n.json

Actor on Apify
{
  "name": "NetEase Cloud Music Song, Chart & Playlist Scraper to n8n only",
  "nodes": [
    {
      "id": "dde9713a-e1d6-423c-a8df-1f51ed3d7963",
      "name": "Run by hand",
      "type": "n8n-nodes-base.manualTrigger",
      "typeVersion": 1,
      "position": [
        0,
        0
      ],
      "parameters": {}
    },
    {
      "id": "19c190ba-0149-4afa-a182-7b57e16c113b",
      "name": "Every day",
      "type": "n8n-nodes-base.scheduleTrigger",
      "typeVersion": 1.2,
      "position": [
        0,
        200
      ],
      "parameters": {
        "rule": {
          "interval": [
            {
              "triggerAtHour": 8
            }
          ]
        }
      },
      "notes": "Activate the workflow to run on this schedule."
    },
    {
      "id": "ee1a101e-7308-409f-aae3-47ee7626ec73",
      "name": "Run Apify Actor",
      "type": "n8n-nodes-base.httpRequest",
      "typeVersion": 4.2,
      "position": [
        260,
        100
      ],
      "parameters": {
        "method": "POST",
        "url": "https://api.apify.com/v2/actors/dataspryva~netease-cloud-music-song-chart-and-playlist/run-sync-get-dataset-items",
        "authentication": "genericCredentialType",
        "genericAuthType": "httpHeaderAuth",
        "sendBody": true,
        "specifyBody": "json",
        "jsonBody": "{\n  \"mode\": \"search\",\n  \"searchQueries\": [\n    \"周杰伦\"\n  ],\n  \"searchType\": \"song\",\n  \"artistOrder\": \"hot\",\n  \"playlistCat\": \"华语\",\n  \"maxTracksPerChart\": 0,\n  \"commentOrder\": \"recommended\",\n  \"maxCommentsPerItem\": 100,\n  \"includeReplies\": false,\n  \"maxRepliesPerComment\": 20,\n  \"includeArtistProfile\": false,\n  \"includeLyrics\": false,\n  \"includeAlbumTracks\": true,\n  \"includePlaylistTracks\": true,\n  \"includeToplistInfo\": true,\n  \"maxItems\": 3\n}",
        "options": {
          "timeout": 310000
        }
      },
      "notes": "Actor: dataspryva/netease-cloud-music-song-chart-and-playlist. Select a Header Auth credential: name Authorization, value Bearer + your Apify token. Edit the JSON body to change the input.",
      "notesInFlow": false
    },
    {
      "id": "11f3f052-5794-415a-ab5a-350bdf1f76d7",
      "name": "Setup",
      "type": "n8n-nodes-base.stickyNote",
      "typeVersion": 1,
      "position": [
        0,
        -370
      ],
      "parameters": {
        "content": "## NetEase Cloud Music Song, Chart & Playlist Scraper\n\nSource: [dataspryva/netease-cloud-music-song-chart-and-playlist](https://apify.com/dataspryva/netease-cloud-music-song-chart-and-playlist) on Apify.\n\n1. In **Run Apify Actor**, create a Header Auth credential: name `Authorization`, value `Bearer YOUR_APIFY_TOKEN` with your token.\n2. Click **Execute workflow**. Each record arrives as one n8n item.\n3. Edit the JSON body of **Run Apify Actor** to change the input.\n\nGenerated by recipeforagents.com. Validated, not executed: runs are billed to your Apify account.",
        "height": 340,
        "width": 460,
        "color": 6
      }
    }
  ],
  "connections": {
    "Run by hand": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    },
    "Every day": {
      "main": [
        [
          {
            "node": "Run Apify Actor",
            "type": "main",
            "index": 0
          }
        ]
      ]
    }
  },
  "pinData": {},
  "active": false,
  "settings": {
    "executionOrder": "v1"
  },
  "meta": {
    "templateCredsSetupCompleted": false
  },
  "tags": []
}

Import with Workflows, Import from file, or paste into the canvas. Credentials are not included: you select them after import.

All 7 destination variants pass the same checks at build time. Built-in nodes only, at versions n8n has shipped since 1.80: they import on n8n Cloud and older self-hosted instances without community nodes. Prefer Apify's own node? The verified community node @apify/n8n-nodes-apify runs the same Actor with OAuth sign-in on n8n Cloud.

Runs longer than 5 minutes? The synchronous endpoint answers HTTP 408 after 300 seconds. The long-run variant starts the run, checks it every minute until it ends, then reads its dataset (HTTP Request, If and Stop and Error nodes only).

Download the long-run workflow11 of 11 checks pass, not executed

Call it from code

Run the Actor from a script or your own agent framework with the Apify API. The call waits for the run to finish and returns the records. The input is the example below.

curl

API docs on Apify
curl -X POST "https://api.apify.com/v2/actors/dataspryva~netease-cloud-music-song-chart-and-playlist/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d '{"mode":"search","searchQueries":["周杰伦"],"searchType":"song","artistOrder":"hot","playlistCat":"华语","maxTracksPerChart":0,"commentOrder":"recommended","maxCommentsPerItem":100,"includeReplies":false,"maxRepliesPerComment":20,"includeArtistProfile":false,"includeLyrics":false,"includeAlbumTracks":true,"includePlaylistTracks":true,"includeToplistInfo":true,"maxItems":3}'

Example input

These values come from the Actor's Store prefill and required defaults. Change the search, URL or limit before your first run.

Actor inputinput.json

{
  "mode": "search",
  "searchQueries": [
    "周杰伦"
  ],
  "searchType": "song",
  "artistOrder": "hot",
  "playlistCat": "华语",
  "maxTracksPerChart": 0,
  "commentOrder": "recommended",
  "maxCommentsPerItem": 100,
  "includeReplies": false,
  "maxRepliesPerComment": 20,
  "includeArtistProfile": false,
  "includeLyrics": false,
  "includeAlbumTracks": true,
  "includePlaylistTracks": true,
  "includeToplistInfo": true,
  "maxItems": 3
}

FieldTypeWhat it does
mode required string (10 options) What to fetch. Each mode reads its own list field.
searchQueries array Free-text queries (mode=search). One or more artist, song, album or playlist names.
searchType string (4 options) Which catalog entity to search for (mode=search).
songUrls array music.163.com song URLs or bare song IDs, e.g. 186016.
artistIds array Artist IDs, music.163.com artist URLs, or exact artist names.
artistOrder string (2 options) Order the artist's song catalogue by popularity or release time (mode=byArtist).
albumUrls array music.163.com album URLs or bare album IDs.
playlistUrls array music.163.com playlist URLs or bare playlist IDs. Full tracklists are read.
playlistCat string (71 options) NetEase playlist genre, scene or mood to browse (mode=byPlaylist).
toplistIds array Chart IDs, music.163.com toplist URLs, or Chinese/English chart names. Use all or leave empty for every current chart.
maxTracksPerChart integer Limit tracks read from each chart before the global max items cap (mode=byToplist). 0 reads every track.
commentUrls array Song, album, playlist or chart URLs/IDs. A bare ID is treated as a song; use album:123, playlist:123 or chart:123 to be explicit.
commentOrder string (2 options) Recommended comments or NetEase's hot-comment selection (mode=comments).
maxCommentsPerItem integer Maximum top-level comments read per song, album, playlist or chart (mode=comments). NetEase stops anonymous pagination around 1,100.
includeReplies boolean Fetch the reply floor for comments that have replies (mode=comments).
maxRepliesPerComment integer How many replies to read for each comment when replies are enabled (mode=comments).
includeArtistProfile boolean Emit one artist profile record with bio, images, sizes, rank, identities and fan count (mode=byArtist / byArtistAlbums).
includeLyrics boolean Attach full LRC lyrics plus translation, romanization and word-by-word lyrics when NetEase has them (every song mode).
includeAlbumTracks boolean Emit each album's tracks as song records (mode=byAlbum).
includePlaylistTracks boolean Emit the playlist's full tracklist as song records (mode=byPlaylistUrl).
includeToplistInfo boolean Emit a chart summary record before each chart's tracks (mode=byToplist).
maxItems integer Hard cap on total dataset records for the run, including error records.

6 more optional fields on the Store input tab.

What your agent receives

Each run returns a list of records. The Actor publishes 9 fields, starting with name, artist, album, rankPosition.

Field
recordType
name
artist
album
rankPosition
chartName
playlistName
durationSec
sourceUrl

Agent skill

A SKILL.md in the open Agent Skills format. It teaches Claude Code, Codex and other skill-aware agents when to call this Actor, how to build the input and how to read the result, using the API directly.

SKILL.mdnetease-cloud-music-song-chart-and-playlist/SKILL.md

---
name: netease-cloud-music-song-chart-and-playlist
description: "NetEase Cloud Music songs, albums, artists, playlists, chart summaries, comments and lyrics metadata. Runs the Apify Actor dataspryva/netease-cloud-music-song-chart-and-playlist. Use when the user needs NetEase Cloud Music data with fields such as recordType, name, artist, album, rankPosition, chartName and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "dataspryva/netease-cloud-music-song-chart-and-playlist"
  store-url: "https://apify.com/dataspryva/netease-cloud-music-song-chart-and-playlist"
---

# NetEase Cloud Music Song, Chart & Playlist Scraper

Use this skill to fetch NetEase Cloud Music data with the Apify Actor `dataspryva/netease-cloud-music-song-chart-and-playlist` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | string, required | What to fetch. Each mode reads its own list field. |
| `searchQueries` | array | Free-text queries (mode=search). One or more artist, song, album or playlist names. |
| `searchType` | one of `song`, `album`, `artist`, `playlist` | Which catalog entity to search for (mode=search). |
| `songUrls` | array | music.163.com song URLs or bare song IDs, e.g. 186016. |
| `artistIds` | array | Artist IDs, music.163.com artist URLs, or exact artist names. |
| `artistOrder` | one of `hot`, `time` | Order the artist's song catalogue by popularity or release time (mode=byArtist). |
| `albumUrls` | array | music.163.com album URLs or bare album IDs. |
| `playlistUrls` | array | music.163.com playlist URLs or bare playlist IDs. Full tracklists are read. |
| `playlistCat` | string | NetEase playlist genre, scene or mood to browse (mode=byPlaylist). |
| `toplistIds` | array | Chart IDs, music.163.com toplist URLs, or Chinese/English chart names. Use `all` or leave empty for every current chart. |
| `maxTracksPerChart` | integer | Limit tracks read from each chart before the global max items cap (mode=byToplist). 0 reads every track. |
| `commentUrls` | array | Song, album, playlist or chart URLs/IDs. A bare ID is treated as a song; use `album:123`, `playlist:123` or `chart:123` to be explicit. |
| `commentOrder` | one of `recommended`, `hot` | Recommended comments or NetEase's hot-comment selection (mode=comments). |
| `maxCommentsPerItem` | integer | Maximum top-level comments read per song, album, playlist or chart (mode=comments). NetEase stops anonymous pagination around 1,100. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "search",
  "searchQueries": [
    "周杰伦"
  ],
  "searchType": "song",
  "artistOrder": "hot",
  "playlistCat": "华语",
  "maxTracksPerChart": 0,
  "commentOrder": "recommended",
  "maxCommentsPerItem": 100,
  "includeReplies": false,
  "maxRepliesPerComment": 20,
  "includeArtistProfile": false,
  "includeLyrics": false,
  "includeAlbumTracks": true,
  "includePlaylistTracks": true,
  "includeToplistInfo": true,
  "maxItems": 3
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/dataspryva~netease-cloud-music-song-chart-and-playlist/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/dataspryva~netease-cloud-music-song-chart-and-playlist/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `recordType`, `name`, `artist`, `album`, `rankPosition`, `chartName`, `playlistName`, `durationSec`, `sourceUrl`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.

  • Claude Code: save it as ~/.claude/skills/netease-cloud-music-song-chart-and-playlist/SKILL.md, or .claude/skills/netease-cloud-music-song-chart-and-playlist/SKILL.md in a project.
  • Codex and other agents: ~/.agents/skills/netease-cloud-music-song-chart-and-playlist/SKILL.md, or .agents/skills/netease-cloud-music-song-chart-and-playlist/ in a project.
  • Or let the skills CLI place it for your agent: npx skills add https://recipeforagents.com --skill netease-cloud-music-song-chart-and-playlist
  • Set APIFY_TOKEN in the agent's environment.

Troubleshooting

Why does the client say Unauthorized or invalid token?

Every Apify Actor tool needs a signed-in Apify account. Reconnect the server so the OAuth sign-in runs again, or switch to the token variant: an Authorization: Bearer header with an API token from Apify Console, Settings, API and integrations. For a local server the token must be in the server's own env block, not only in your shell.

Source: Apify MCP server README

Why did my agent's tool list change after an update?

Without a tools parameter Apify's server loads its default tool set, which changes between releases. The URLs on this site pin the tools with ?tools=, so the agent always gets the same Actor tool plus fetch-actor-details. Apify's README gives the same advice for production.

Source: Apify MCP server README

What happens when the agent sends input the Actor rejects?

The server answers with the Actor's input schema, so the agent can fix the arguments and call again. The fetch-actor-details tool in every scoped URL lets it read that schema before the first call.

Source: Apify MCP server README

Questions

How do I connect NetEase Cloud Music Song, Chart & Playlist Scraper to Claude?

In Claude Code run: claude mcp add --transport http netease-cloud-music-song-chart-and-playlist "https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/netease-cloud-music-song-chart-and-playlist". In Claude Desktop or claude.ai add a custom connector with the URL https://mcp.apify.com/?tools=fetch-actor-details,dataspryva/netease-cloud-music-song-chart-and-playlist and sign in to Apify. The agent then gets one tool for this Actor plus a tool that reads its input schema.

What input does NetEase Cloud Music Song, Chart & Playlist Scraper need?

The published input schema requires mode. The example on this page uses the Actor's own Store prefill.

What does NetEase Cloud Music Song, Chart & Playlist Scraper cost to run?

The Apify Store lists $0.99 per 1,000 results (pay per event) for this Actor, checked 2026-11-12. Runs are billed to the Apify account whose token or sign-in the agent uses; Apify platform usage can add to that.

Which tools does the MCP config give my agent?

6 tools: fetch-actor-details, dataspryva--netease-cloud-music-song-chart-and-playlist, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run. Apify's MCP server listed them for this exact URL on 2026-11-11.