Spotify MCP vs Metmuseum MCP — MCP Server Comparison | AllMCPs
Side-by-Side Model Context Protocol Comparison
Spotify MCP vs Metmuseum MCP
In-depth architectural comparison of the Spotify MCP and Metmuseum MCP MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Spotify MCP
Art & Culture · Local stdio
Quality: 52/100 (Good) | Auth: No auth required
Metmuseum MCP
Art & Culture · Local stdio
Quality: 64/100 (Good) | Auth: No auth required
Verdict Summary: Choose Spotify MCP if you need specialized Art & Culture tools running via a local process. Choose Metmuseum MCP if your workspace requires Art & Culture integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Spotify MCP when:
You need dedicated capabilities in the Art & Culture domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Conversational Spotify control with intent-shaped tools: play by description, queue, devices, playlists, and library, plus a 2-minute PKCE setup wizard. Built for the post-Feb-2026 Spotify Web API. npx -y @xavifabregat/spotify-mcp
Metropolitan Museum of Art Collection API integration to search and display artworks in the collection.
Category & Scope
Tools & Capabilities Breakdown
Spotify MCP Tools (11)
play
Play by free-text query (search → best match → play) or Spotify URI
Spotify MCP is categorized under Art & Culture and uses a local stdio subprocess. In contrast, Metmuseum MCP belongs to Art & Culture using local stdio subprocess. Select Spotify MCP when you need capabilities focused on art & culture and Metmuseum MCP when you require tools for art & culture.
Show a playlist's tracks (own/collaborative only — API restriction)
modify_playlist
Create a playlist; add tracks
library
Save / remove / check items in your library
authenticate
Run the Spotify login from inside a conversation
Metmuseum MCP Tools (4)
list-departments
List all departments in the Metropolitan Museum of Art (Met Museum)
search-museum-objects
Search for objects in the Metropolitan Museum of Art (Met Museum). Will return Total objects found, followed by a paginated list of Object Ids. If the Met Explorer app (open-met-explorer) is open and the user is referring to its existing results, prefer using those results from context instead of calling this tool. The parameter title should be set to true if you want to search for objects by title. The parameter hasImages is false by default, but can be set to true to return only objects with images. Additional optional filters are available for highlights, tags, on-view status, artist/culture match, medium, geographic location, and date range. Use page and pageSize to paginate results.
get-museum-object
Get a museum object by its ID, from the Metropolitan Museum of Art Collection. Use this when the user asks for deeper details on a specific object ID.
open-met-explorer
Open the interactive Met Explorer app for browsing and filtering objects. For exploration intents, pass q so the app can run a live search on open. After opening, keep your chat handoff short and UI-focused. For deeper details on a specific object ID, prefer get-museum-object.