Spotify Play Count MCP: Plays & Monthly Listeners

io.github.GeminiGeorge22Published by GitHub account GeminiGeorge22v1.0.1Updated Nov 4, 2026

Spotify play counts for any track, album, artist or playlist, plus monthly listeners and followers.

VerifiedStreamable HTTPWeb executable

Overview

Spotify Play Count MCP: Plays & Monthly Listeners's hosted MCP server (mcp.apify.com); OAuth sign-in or API key required; Streamable HTTP; 1 tool.

No AI overview yet: these facts come from the registry entry and the server itself.

Endpoint
mcp.apify.com
Last checked

Installation

In SourceWeft

  1. Open Spotify Play Count MCP: Plays & Monthly Listeners in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.GeminiGeorge22%2Fspotify-play-count-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "spotify-play-count-plays-monthly-listene": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=publicrecords/spotify-play-count-scraper"
    }
  }
}

README

Spotify Play Count MCP: Plays & Monthly Listeners

An MCP server that gives your AI assistant Spotify play counts. Paste a track, album, artist or playlist link (or a spotify: URI) and it returns every track's play count, and for artists their monthly listeners, followers, world rank and top cities. Optionally it adds streams over the last 1, 7 and 30 days for tracks in daily tracking. No Spotify login and no proxy setup.

Built on the public Spotify web pages, via the Apify Actor Spotify Play Count & Monthly Listeners Scraper. Not affiliated with Spotify.

Example prompts

  • "How many plays does each track on this album have? https://open.spotify.com/album/4aawyAB9vmqN3uQ7FjRGTy"
  • "Compare monthly listeners and followers for these three artists."
  • "Which tracks on this playlist have the most plays?"
  • "Track my artist page weekly and show streams per day for every song."

Tool

ToolInputOutput
publicrecords--spotify-play-count-scraperurls (track, album, artist or playlist links or URIs), addDailyStreams, includeArtistAlbums, maxTracksPerTargetOne row per track (track, artists, album, play count, release date, links) and one per artist (monthly listeners, followers, world rank, top cities)

About the daily stream fields (streamsLast1d, streamsLast7d, streamsLast30d, with addDailyStreams on): a track seen for the first time gets empty values on that day. The fields fill in after the first day of history, so a run a day later shows the last day and a week later the last 7 days.

The full input schema is in tools.json, generated from the Actor's public input schema and checked for drift daily.

MCP endpoint

https://mcp.apify.com?tools=publicrecords/spotify-play-count-scraper

Transport: Streamable HTTP (hosted by Apify, see https://docs.apify.com/mcp).

Auth

Sign in with Apify OAuth when your client prompts you, or send the header Authorization: Bearer <APIFY_TOKEN> where <APIFY_TOKEN> is your own Apify API token. Never commit a real token.

Client setup

Claude

Claude Code:

claude mcp add --transport http spotify-play-count "https://mcp.apify.com?tools=publicrecords/spotify-play-count-scraper"

Claude Desktop / claude.ai: Settings → Connectors → Add custom connector, and paste the MCP endpoint URL above.

Cursor

~/.cursor/mcp.json:

json
{  "mcpServers": {    "spotify-play-count": {      "url": "https://mcp.apify.com?tools=publicrecords/spotify-play-count-scraper"    }  }}

VS Code

.vscode/mcp.json:

json
{  "servers": {    "spotify-play-count": {      "type": "http",      "url": "https://mcp.apify.com?tools=publicrecords/spotify-play-count-scraper"    }  }}

To use a token instead of OAuth, add "headers": { "Authorization": "Bearer <APIFY_TOKEN>" } next to "url".

Disclosure: I maintain this Actor.

Local stdio server (open source)

This repo also ships a small MCP server in src/ for clients that only run local stdio servers. It answers initialize and tools/list locally from tools.json, which is generated from the Actor's public input schema and checked for drift in CI and daily, so any client or directory can inspect the tools with no token. tools/call is forwarded to the hosted Apify MCP endpoint above with your own APIFY_TOKEN; without a token a call returns a clear error instead of running anything. The token is only sent in the Authorization header and is never logged.

bash
npx -y github:GeminiGeorge22/spotify-play-count-mcp
json
{  "mcpServers": {    "spotify-play-count": {      "command": "npx",      "args": ["-y", "github:GeminiGeorge22/spotify-play-count-mcp"],      "env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }    }  }}

Or from a clone:

bash
git clone https://github.com/GeminiGeorge22/spotify-play-count-mcp.gitcd spotify-play-count-mcp && npm installAPIFY_TOKEN=YOUR_APIFY_TOKEN node src/server.js

Optional env: APIFY_ACTORS (comma-separated subset of the Actors above) and APIFY_MCP_URL (full endpoint override).

Tests run against an in-memory mock server, with no network and no token: npm test. Requires Node.js 18+.

Python (uvx/pip)

A matching Python version of this server lives in python/, built on the official mcp Python SDK: same tool, same APIFY_TOKEN, same hosted endpoint. Requires Python 3.10+.

bash
uvx spotify-play-count-mcp
json
{  "mcpServers": {    "spotify-play-count": {      "command": "uvx",      "args": ["spotify-play-count-mcp"],      "env": { "APIFY_TOKEN": "YOUR_APIFY_TOKEN" }    }  }}

Or with pip: pip install spotify-play-count-mcp, then run spotify-play-count-mcp. Until the first PyPI release, run it from GitHub: uvx --from "git+https://github.com/GeminiGeorge22/spotify-play-count-mcp#subdirectory=python" spotify-play-count-mcp. Python tests: cd python && pip install -e ".[test]" && env -u APIFY_TOKEN python -m pytest.

See also

Source: README.md at commit 736fe69

Tools

1

publicrecords--spotify-play-count-scraper

Spotify Play Count & Monthly Listeners Scraper

Spotify Play Count & Monthly Listeners Scraper. Play counts for every track of any Spotify album, playlist or artist, plus monthly listeners and followers for artists. Optional streams per day for tracked tracks. No login. When to use: Use when you need Spotify play counts: the total plays of every track behind a track, album, artist or playlist link, plus an artist's monthly listeners, followers, world rank and top cities. Optional streams over the last 1, 7 and 30 days for tracks already in daily tracking; those fields stay empty for a track's first day and fill in once it has history. Good for release tracking, playlist checks and artist comparisons; not for private Spotify for Artists data or royalties. Returns: the run's dataset rows as structured JSON (one row per result), plus the run and dataset IDs for paging the full dataset. Behavior: starts one run of the Apify Actor "publicrecords/spotify-play-count-scraper" through Apify's hosted MCP gateway (mcp.apify.com) with your own APIFY_TOKEN; the run uses your Apify account. Read-only: it only reads public web data and changes nothing on the source site. Docs: https://apify.com/publicrecords/spotify-play-count-scraper

ParametersurlsrequiredaddDailyStreamsmaxTracksPerTargetincludeArtistAlbums

Version history

1
  1. v1.0.1LatestNov 4, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts