MCP server · 3 tools · 6 endpoints

Spotify MCP server

Tracks, albums, artists, top tracks, playlists and catalogue search from Spotify, without registering an app or handling OAuth.

Get a free key Connect in a minute

100 credits on signup · No card · Sign in with OAuth or paste a key

scrapersocial-spotify mcp.scrapersocial.com/spotifyconnected

you

Search Spotify for <song title> by <artist> and return the track id

agent

calls search 2 credits / result

{ "query": "<keywords>" }

server

returns

results [{ … }] · one per result

Shape only. Keys follow the tool's summary; a real call returns the full record. 1 call · 2 credits

Connect

One URL. Your client already knows what to do with it.

The first call opens a sign-in. New accounts get 100 credits, no card. Every client below shares one account and one balance.

Get a free key

server url https://mcp.scrapersocial.com/spotify

claude.aiOAuth

Settings → Connectors → Add custom connector, then paste the server URL.

mcp.scrapersocial.com/spotify

Web, desktop and mobile. Nothing else to paste.

Claude Codeone command

Run this in a terminal.

$ claude mcp add --transport http scrapersocial-spotify https://mcp.scrapersocial.com/spotify

Approve the sign-in prompt on first use.

Cursorone click

Installs the server and opens the MCP panel.

Add to Cursor

or paste the JSON into .cursor/mcp.json

{
  "mcpServers": {
    "scrapersocial-spotify": {
      "url": "https://mcp.scrapersocial.com/spotify",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

Other clients · VS Code, Windsurf, Gemini CLI, anything that speaks MCP

VS Codeone click or JSON

Add to VS Codeor run MCP: Add Server, choose HTTP and use:

{
  "name": "scrapersocial-spotify",
  "type": "http",
  "url": "https://mcp.scrapersocial.com/spotify"
}

Windsurf~/.codeium/windsurf/mcp_config.json

{
  "mcpServers": {
    "scrapersocial-spotify": {
      "serverUrl": "https://mcp.scrapersocial.com/spotify",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

Gemini CLI~/.gemini/settings.json

{
  "mcpServers": {
    "scrapersocial-spotify": {
      "httpUrl": "https://mcp.scrapersocial.com/spotify",
      "headers": {
        "Authorization": "Bearer sk_live_..."
      }
    }
  }
}

Any clientStreamable HTTP · OAuth 2.1 or Bearer

$ npx add-mcp https://mcp.scrapersocial.com/spotify

One account and one balance across every client and the every-platform hub at mcp.scrapersocial.com.

What it does

What your agent can do with Spotify

Spotify’s own API is free and thorough, and if Spotify is the only thing you’re reading, you should probably use it. The catch is the setup: register an application, store a client secret, refresh tokens, and repeat per project. ScraperSocial’s Spotify spoke skips all of that. One connection, one key, and public catalogue metadata shows up alongside the other platforms your agent already reads.

Six endpoints are live. search is the wrapped tool and takes a text query, returning matching results from the catalogue. The rest are reached with call_endpoint and a path: /v1/spotify/track, /v1/spotify/album, /v1/spotify/artist and /v1/spotify/playlist each take the item’s Spotify id and return its metadata; /v1/spotify/artist-top-tracks takes an artist id and lists their most popular tracks. list_endpoints prints the set at no charge.

Spotify is a streaming catalogue rather than a social network. ScraperSocial treats its public pages as web data: what’s visible on a public track, album, artist or playlist page, as JSON.

Every call costs 2 credits; the two list calls cost 2 per item. Connect https://mcp.scrapersocial.com/spotify and ask about a song.

Four jobs it finishes on its own

Resolving pasted links

Someone drops a Spotify link in a chat and asks what it is. The agent extracts the id, calls the track, album or artist endpoint, and answers with the metadata on the page. Two credits.

Building an artist sheet

Give the agent a list of artist ids and have it pull `/v1/spotify/artist` for each, then `/v1/spotify/artist-top-tracks`. The result is a table of artists and their current top tracks, refreshed whenever you re-run it.

Keeping an eye on playlists

Point `/v1/spotify/playlist` at a public playlist id and the agent gets its details. Useful for keeping a record of the playlists you care about and noticing when they change.

Catalogue search for research

Search by title or artist to find ids before you have them, then chain into the detail endpoints. For metadata-heavy tasks, like matching a messy list of song titles to canonical records, this is the loop.

Limits · read before you connect

What this does not do

Written by a person, not generated. If something here is wrong, tell us.

Public catalogue metadata only. There’s no audio, no playback, no user library, no listening history and no private playlists; the server never signs in to a Spotify account. All six endpoints cost 2 credits, charged per item on the two list endpoints (search and /v1/spotify/artist-top-tracks), with a 1-credit minimum when nothing comes back. Lists are paged at 50 with a cursor. Track and album metadata is cached for a long time because it rarely changes; use fresh: true if you need a re-read. Nothing on this spoke writes to Spotify: no follows, no saves, no playlist edits.

Tools

3 tools, same names as the every-platform hub

One does one Spotify thing each. The last two reach all 6 endpoints by path, so nothing in the catalog is out of an agent's reach.

Full credit table →

Search a platform

search

Keyword search over one platform's public content.

2 credits / result

Reaches the other 5 endpoints

List every Spotify endpoint

list_endpoints

Browse every Spotify endpoint, its input and its credit cost. Free, and calls nothing upstream.

free

Call any Spotify endpoint by path

call_endpoint

Run any Spotify endpoint by its path, so nothing Spotify offers is out of reach of an agent.

endpoint's own cost

Pricing

100 free credits is 50 search results.

Then $5 a month for 1,000 credits, or $4 per 1,000 as a top-up. No card to start. Every call costs 2 credits.

50 search resultssearch · 2 each

Get a free key 100 credits on signup · $5 for 1,000 · full credit table

Prompts

Things to ask once it is connected

Copy one, swap the placeholder, paste it into your client.

What is <spotify track url>? Give me the artist and album

Get the top tracks for artist <spotify artist id>

Search Spotify for <song title> by <artist> and return the track id

Pull the details of playlist <spotify playlist id>

Look up these album ids and build a table of title and artist: <id 1>, <id 2>, <id 3>

Questions

Before you connect

Why use this instead of Spotify's Web API? #

If Spotify is your only source, don't; the official API is free and richer. Use this spoke when you want one MCP connection covering Spotify alongside the social platforms, with no app registration.

What's the price of a lookup? #

2 credits per track, album, artist or playlist, and 2 per item on search and top tracks. The 100 free credits on signup cover fifty lookups; 1,000 credits cost $5.

What's the handle for a track or artist? #

The Spotify id, the string after `/track/`, `/album/`, `/artist/` or `/playlist/` in a share link. The agent can pull it out of a pasted URL.

Is this affiliated with Spotify? #

No. ScraperSocial runs independently and has never had any relationship with Spotify. It reads public catalogue pages and returns them as data.

Can I get audio or my listening history? #

No. Audio, playback, user libraries and listening history aren't public, and the server doesn't sign in.

Go further

If you want music metadata in the same agent that reads TikTok and Instagram, without a second set of credentials to manage, this is the spoke. Connect https://mcp.scrapersocial.com/spotify, paste a track link you already know, and see what comes back for 2 credits.

Get a free key 100 credits, no card

ScraperSocial is independent and not affiliated with, endorsed by or connected to Spotify. Publicly available data only.