mixcloud-mcp-server
Related Servers
Alternatives to mixcloud-mcp-server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceBridges the Mixcloud API to AI assistants via MCP, enabling search for mixes, artist lookup, uploads, and user profile access.71GPL 3.0
- AlicenseAqualityCmaintenanceEnables MCP clients to search SoundCloud and retrieve tracks, playlists, and users, as well as perform authenticated actions such as likes, reposts, follows, comments, playlist editing, and uploads with multi-account OAuth support.36MIT
- AlicenseAqualityBmaintenanceEnables MCP clients to build and edit Spotify playlists from natural language descriptions.789 npmMIT

LabelGrid MCP Serverofficial
AlicenseAqualityAmaintenanceThe official MCP server for LabelGrid's music distribution platform, enabling natural language management of music catalogs, releases, files, analytics, royalties, webhooks, and distribution via a thin wrapper over the LabelGrid public API.844MIT- AlicenseCqualityBmaintenanceAn MCP server that gives an assistant access to the SoundCloud API — search and discovery, your library, playlist management, social actions, and messaging.32MIT
- FlicenseNot gradedqualityCmaintenanceEnables searching Spotify and managing playlists from any MCP client using natural language.-
TDQS
Scored across 22 tools
There is meaningful overlap between generic tools and specific ones: get_object vs get_show/get_user/get_tag, list_connection vs user_shows/genre_shows/browse, and me vs get_user/check_token. The detailed descriptions help clarify intended use, but an agent could still reasonably hesitate between several read/list tools.
Most names use snake_case, but the conventions are mixed: verb_noun (get_show, list_connection, follow_user), noun_verb or noun_phrase (user_shows, genre_shows, embed_html), and bare nouns/actions (search, browse, me, oembed, auth_url). It remains readable, but the pattern is not predictable.
With 22 tools, the server is on the heavy side for the Mixcloud API surface. Several tools are generic duplicates of more specific ones, so the count feels slightly inflated rather than perfectly scoped.
The surface covers search, reads, social actions, upload/edit lifecycle, and OAuth reasonably well. Minor gaps exist, such as no explicit delete_show and no comment-related tools, but core workflows are supported.