A
licenseNot graded
qualityC
maintenanceEnables programmatic control of Cursor's cloud-based AI agents for automated code generation and repository management via standardized MCP tools.
5 npm
6
MIT
Spotify MCP
by ashwanth1109
Related Servers
Alternatives to Spotify MCP
No user-submitted related servers found.
Related Servers
- FlicenseBqualityDmaintenanceEnables to manage notes and collections in Fastidious AI application through natural language, supporting CRUD operations and search via MCP protocol.11-
- AlicenseNot gradedqualityAmaintenanceEnables MCP clients such as Claude, Cursor, VS Code, and Windsurf to manage workspaces, projects, tasks, and AI agents through natural language.2,760 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables using Meta AI Demos (aidemos.meta.com) tools from Cursor via MCP, including SAM3 template management, media upload, and GraphQL calls.1MIT
- AlicenseAqualityAmaintenanceLocalBridge MCP is a bridge between an online AI chats and your computer. Most online AI chats can reason, and write code, but they normally cannot touch the local files, terminals, and scripts that make real work happen. This gives a trusted assistant a controlled doorway into a machine you own, so it can inspect files, edit text, search a project, run tests, use Git, and operate a shell.173Apache 2.0
- FlicenseNot gradedqualityDmaintenanceA CLI-first semantic code search tool with MCP integration for AI assistants, enabling semantic search, AST-aware parsing, and code analysis across 13 languages.300 PyPI55-
TDQS
B3.2/5.0
Scored across 21 tools
Disambiguation4/5
Most tools have distinct purposes targeting specific Spotify resources and actions, with clear boundaries between playback control, queue management, and content retrieval. However, some overlap exists between 'skip_tracks' and 'next_track'/'previous_track', and 'start_playback' vs 'start_playback_track'/'start_playlist_playback' could cause confusion about which to use for resuming vs starting specific content.
Naming Consistency4/5
The server maintains strong consistency with snake_case naming throughout and mostly follows verb_noun patterns (e.g., 'get_current_track', 'add_to_queue', 'search_spotify'). Minor deviations include 'get_item_info' (noun_verb) and some tools using 'playback' while others use 'track'/'playlist' in similar contexts, but the overall pattern remains clear and predictable.
Tool Count3/5
With 21 tools, this feels borderline heavy for a music streaming interface. While Spotify's API is feature-rich, the tool set includes some redundancy (e.g., multiple skip/playback variants) that could potentially be consolidated. The count is manageable but approaches the upper limit of what feels well-scoped for this domain.
Completeness5/5
The tool surface provides comprehensive coverage of Spotify's core functionality including playback control (play/pause/skip/seek/repeat), queue management, content retrieval (tracks/artists/playlists/recommendations), search capabilities, and user data access. There are no obvious gaps for typical agent workflows, with CRUD-like operations well-represented across the music streaming domain.
Maintenance
ActivityInactive
ResponsivenessNo issues