@cassette.diy/mcp
Related Servers
Alternatives to @cassette.diy/mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceMCP server for interacting with Discogs music collections. It enables AI assistants to search, manage, and analyze personal music libraries with OAuth authentication and intelligent features like mood mapping.MIT

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.843MIT- AlicenseNot gradedqualityCmaintenanceA comprehensive MCP server that enables AI assistants to control music playback, manage users and access, configure providers, and administer a Music Assistant setup through natural language commands.MIT
- AlicenseAqualityCmaintenanceAn MCP server that enables AI assistants to read, create, and manage issues, repositories, and releases on Gitea, Forgejo, or Codeberg instances via personal access tokens.21MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for storing, managing, and analyzing IETF vCon (Virtual Conversation) data with AI assistants.35 npm4MIT
- FlicenseAqualityCmaintenanceA lightweight MCP server that enables AI assistants like Cursor and Claude to control Spotify playback, playlists, and manage tokens via OAuth.152-
TDQS
Scored across 28 tools
Each tool targets a distinct resource and action (e.g., clips, tracks, footages, trends). Overlaps like cassette_create_clip vs cassette_start_clip_from_trend are clearly differentiated by context. All tools have clear, non-overlapping purposes.
All tools follow a consistent 'cassette_verb_noun' pattern in snake_case. Verbs like create, delete, get, list, update are used predictably. No mixing of conventions or vague names.
28 tools is slightly above the recommended range for a typical server. While each tool earns its place given the domain's complexity, the count feels heavy and could potentially be consolidated (e.g., merging manage_clip_shares into separate tools).
The tool surface covers core workflows for clips, tracks, footages, trends, and account management. Minor gaps exist, such as missing delete_track and list_tracks tools, but these are not critical and can be worked around.