Skip to main content
Glama
igorgarbuz

Spotify MCP Node Server

by igorgarbuz

Related Servers

Alternatives to Spotify MCP Node Server

No user-submitted related servers found.

    Related Servers

    TDQS

    B3.4/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools have distinct purposes, but 'addToQueue' and 'playMusic' could cause confusion as both involve initiating playback. 'addToQueue' adds to the queue while 'playMusic' starts playback immediately, but an agent might misinterpret their overlap in handling tracks/albums/artists/playlists. Other tools are clearly differentiated by resource and action.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun or verbNoun pattern, such as 'addToQueue', 'createPlaylist', 'getNowPlaying', and 'searchSpotify'. The naming is uniform across all 13 tools, with no mixing of conventions like camelCase and snake_case, making it predictable and readable.

    Tool Count5/5

    With 13 tools, this server is well-scoped for Spotify integration, covering core functionalities like playback control, playlist management, user data retrieval, and search. Each tool serves a clear purpose without redundancy, fitting within the typical 3-15 tool range for such a domain.

    Completeness4/5

    The tool set provides comprehensive coverage for Spotify operations, including CRUD for playlists (create, add/remove tracks, get tracks), playback control (play, queue, actions), and user data (playlists, top items, followed artists, recently played). Minor gaps include no update/delete for playlists or explicit volume control, but agents can work around these with available tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues