SongPilot MCP Server
OfficialRelated Servers
Alternatives to SongPilot MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to connect their music distribution catalog and streaming analytics to Claude Desktop, Cursor IDE, and ChatGPT for querying stream trends, inspecting catalog compliance, and applying safe draft release fixes via natural language.22 npmApache 2.0
- AlicenseBqualityBmaintenanceEnables Claude to manage Spotify playlists and analyze personal listening history, including account reads, playlist writes, local analytics from data exports, and building playlists from track lists.35MIT
- AlicenseNot gradedqualityDmaintenanceConnects Claude to Spotify, enabling play control, playlist management, lyrics retrieval, and music recommendations through natural language.1MIT
- AlicenseNot gradedqualityAmaintenanceEnables compatible AI clients such as Claude, Cursor, VS Code, and Windsurf to read and manage workspaces, projects, tasks, and AI agents through natural-language prompts.2,807 npmMIT
- FlicenseDqualityDmaintenanceEnables Claude to interact with Spotify by searching songs, creating playlists, getting recommendations, and managing your music through your Spotify account.73-
- AlicenseAqualityDmaintenanceIntegrates Spotify with Claude to enable voice-controlled music playback, playlist management, and personalized recommendations through conversational AI. It provides comprehensive tools for searching tracks, managing liked songs, and analyzing listening habits.151MIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of an agent confusing it with another tool. Its purpose (routing natural-language requests to SongPilot specialists) is unambiguous by construction.
The lone name 'run_orchestrator' follows a clear verb_noun snake_case pattern. With a single tool, consistency is trivially satisfied and the name is readable and descriptive.
A single catch-all tool is very thin for the apparent breadth of the domain (artwork, release planning, bios, song status, artist profiles). The router pattern is deliberate, but agents get no discoverable capability surface beyond one opaque entry point.
There are no structured operations for core entities like songs, albums, artists, or releases — no list/get/create/update equivalents. Everything must go through free-text routing, so agents cannot perform predictable, verifiable actions and will fail on tasks requiring structured access.