Skip to main content
Glama
BASIC-BIT

Soundiiz MCP

by BASIC-BIT
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to Soundiiz MCP

No user-submitted related servers found.

    Related Servers

    • spotify-mcp-server

      qchuchu
      A
      license
      Not graded
      quality
      D
      maintenance
      An unofficial MCP server that provides access to Spotify's Web API through the Model Context Protocol, enabling AI assistants to search music, manage playlists, and control playback.
      6 npm
      9
      ISC

    • MCP PLAYLIST SERVER

      alee2602
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides intelligent playlist curation tools using Spotify track data and audio feature analysis. It enables AI assistants to create mood-based playlists, find similar songs, analyze audio characteristics, and curate personalized music collections.
      -

    • Spotify MCP Server

      nlevy
      A
      license
      A
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that provides Spotify integration, allowing AI assistants and applications to interact with Spotify's music streaming service.
      12
      1
      MIT

    • Spotify MCP Server

      agustinhopneto
      F
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server that enables AI assistants to control Spotify playback and manage playlists.
      -
    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

    C2.9/5.0

    Scored across 23 tools

    Disambiguation2/5

    Several tools have overlapping functionality, such as soundiiz_me and soundiiz_read_get_soundiiz_openapi_v1_merest_getme both retrieving user info, and soundiiz_smartlink_get vs soundiiz_read_get_soundiiz_openapi_v1_merest_getmesmartlinksdetails. This creates ambiguity for an agent choosing which tool to use.

    Naming Consistency1/5

    Tool names are highly inconsistent. Some use short, descriptive patterns (soundiiz_auth_clear, soundiiz_smartlink_delete), while others are auto-generated long paths (soundiiz_read_get_soundiiz_openapi_v1_merest_getme). This mix of naming conventions is confusing and unpredictable.

    Tool Count3/5

    The tool count is 23, which is on the higher side but still within a plausible range for a complex API. However, many tools are redundant, making the set feel bloated rather than well-scoped.

    Completeness2/5

    The tool set covers auth, smartlinks, and syncs, but lacks essential operations like creating or updating smartlinks and syncs. There are only delete, list, get, and overview tools, leaving obvious gaps in CRUD coverage for the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources