Skip to main content
Glama
auxa-m45

soundcloud-mcp

by auxa-m45
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to soundcloud-mcp

No user-submitted related servers found.

    Related Servers

    • netease-music-mcp

      yxrytcuucuc
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to query NetEase Cloud Music data such as songs, artists, albums, playlists, lyrics, and a logged-in user's library in compact, paginated, structured form, along with guarded playlist and like write operations.
      15
      MIT

    • Spotify MCP

      deprised
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting a Spotify account to remote MCP clients to search music, manage libraries and playlists, and control playback with per-user OAuth authorization.
      -

    • YouTube MCP Connector

      deepujain
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients to search YouTube videos, read subscriptions and playlists, generate catch-up digests of recent uploads, and manage playlists with approval-gated writes via the YouTube Data API v3.
      MIT
    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

    A3.9/5.0

    Scored across 36 tools

    Disambiguation5/5

    Every tool targets a distinct resource and action: search vs. get, tracks vs. playlists vs. users, and auth vs. content operations are clearly separated. Even similar tools like get_playlist, get_playlist_tracks, and get_playlist_reposters have unique, well-defined purposes.

    Naming Consistency5/5

    All tools follow the soundcloud_ prefix with consistent verb_noun naming: search_*, get_*, create_*, update_*, delete_*, set_*, and list_*. The small variation between get_ and list_ is meaningful, with get_ for single resources and list_ for collections, so the pattern is predictable.

    Tool Count2/5

    At 36 tools, the server exceeds the recommended range and becomes a heavy selection surface for an agent. While each tool is individually specific, the overall count is more than is typically appropriate and could be consolidated or trimmed.

    Completeness5/5

    The tool surface covers the full SoundCloud lifecycle: auth, search, track and playlist CRUD, engagement, user library exploration, and social actions. The api_request escape hatch also fills any edge-case gaps, making the set effectively complete for its domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources