am-mcp
Related Servers
Alternatives to am-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceIntegrates Apple Music with MCP clients to search the global catalog, manage personal playlists, and access library data. It enables users to perform actions like creating playlists, adding tracks, and viewing recommendations through natural language commands.1-
- FlicenseNot gradedqualityDmaintenanceEnables natural-language creation, management, and optimization of Spotify playlists via MCP tools like search, generate, analyze, and recommend.-
- AlicenseNot gradedqualityAmaintenanceCreate custom playlists, control apple music locally, search apple music catalog, use ai to generate play lists, and more all without needing an apple developer account or giving the MCP server special privileges.MIT
- AlicenseNot gradedqualityCmaintenanceEnables searching the Apple Music catalog, building playlists, and managing a library through the Apple Music API.11 npmMIT
- AlicenseAqualityBmaintenanceEnables MCP clients to build and edit Spotify playlists from natural language descriptions.781 npmMIT
- AlicenseNot gradedqualityCmaintenanceApple Music playback control, library search, playlist management, and queue operations via MCP.2MIT
TDQS
Scored across 13 tools
Each tool has a distinct resource+action, and the descriptions explicitly cross-reference alternatives (search_songs vs resolve_candidates, recently_played vs top_played, analyze_flow vs audit_playlist, analyze_flow vs optimize_order). An agent can reliably pick the right tool from the guidance provided.
Every tool uses a consistent am_ prefix followed by a verb_noun pattern (am_create_playlist, am_delete_playlist, am_add_tracks, am_analyze_flow). The only minor deviation is am_status, which is still readable and follows the prefix convention.
13 tools sit comfortably in the ideal 3-15 range and map cleanly onto the playlist-curation workflow (auth, discovery, resolution, creation, editing, auditing, optimization). Each tool earns its place without redundancy.
The surface covers the full lifecycle: search, resolve, create, add, delete, list, show, audit, analyze, optimize, plus status and listening history. Minor gaps exist—no remove-tracks-from-playlist or rename/update-metadata operation, and optimize_order cannot write an existing playlist's order.