Skip to main content
Glama
Sign In
GeminiGeorge22

Spotify Play Count MCP

by GeminiGeorge22
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Spotify Play Count MCP

No user-submitted related servers found.

    Related Servers

    • Spotify Data MCP Server

      eduair94
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to look up Spotify track play counts, artist monthly listeners, charts, albums, playlists, search results, ISRCs, genres, moods, and BPM through MCP tools.
      MIT

    • spotify-mcp

      sjtan2302
      A
      license
      A
      quality
      B
      maintenance
      Lets AI assistants answer questions about your Spotify listening history, including taste evolution, top artists, recently played, and playlist analysis.
      8
      64 npm
      MIT

    • Spotify MCP Server

      Yonsn76
      F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to control Spotify playback, search for music, manage playlists, and access library information through the Spotify API. Requires Spotify Premium for playback control features.
      4
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    With only one tool exposed, there is no possibility of tool-to-tool confusion or misselection. An agent always knows exactly which tool to call for Spotify play-count data.

    Naming Consistency3/5

    The name 'publicrecords--spotify-play-count-scraper' uses kebab-case with a vendor prefix and double hyphen, and describes an object rather than following a verb_noun pattern. There is no inconsistency to speak of with a single tool, but the convention is not the predictable action-oriented style an agent might expect.

    Tool Count2/5

    A single tool is thin even for a narrow, single-purpose scraper wrapper, and it forces all queries (track, album, artist, playlist) through one monolithic entry point. The tool itself is substantial, but the surface is minimal rather than well-scoped across a few focused operations.

    Completeness4/5

    The tool covers the stated domain well: per-track play counts across tracks/albums/artists/playlists plus monthly listeners, followers, rank, cities, and optional stream history. Gaps exist around search/link resolution and historical export beyond the run's dataset paging, and private Spotify for Artists data is explicitly out of scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources