In-depth architectural comparison of the MCP Claude Spotify and MCP Graphql Forge 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
MCP Claude Spotify
Other Tools and Integrations · Local stdio
Quality: 61/100 (Good) | Auth: API Key required
MCP Graphql Forge
Other Tools and Integrations · Remote HTTP/SSE
Quality: 57/100 (Good) | Auth: No auth required
Verdict Summary: Choose MCP Claude Spotify if you need specialized Other Tools and Integrations tools running via a local process. Choose MCP Graphql Forge if your workspace requires Other Tools and Integrations integration with remote web transport. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose MCP Claude Spotify when:
You need dedicated capabilities in the Other Tools and Integrations domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (BYOK (Pay Provider Direct)).
You have access to required keys: SPOTIFY_CLIENT_ID, SPOTIFY_CLIENT_SECRET.
An integration that allows Claude Desktop to interact with Spotify using the Model Context Protocol (MCP).
A lightweight, configuration-driven MCP server that exposes curated GraphQL queries as modular tools, enabling intentional API interactions from your agents.
Category & Scope
Tools & Capabilities Breakdown
MCP Claude Spotify Tools (25)
query
Search text
type
Type of search (track, album, artist, playlist)
limit
Number of results (1-10, default: 5)
trackId
Spotify track ID
deviceId
(Optional) Spotify device ID to play on
offset
(Optional) Index of the first playlist to return (default: 0)
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
MCP Claude Spotify is categorized under Other Tools and Integrations and uses a local stdio subprocess. In contrast, MCP Graphql Forge belongs to Other Tools and Integrations using remote streaming HTTP/SSE transport. Select MCP Claude Spotify when you need capabilities focused on other tools and integrations and MCP Graphql Forge when you require tools for other tools and integrations.
(Optional) Whether the playlist should be collaborative (must set public to false first)
trackIds
Array of track IDs
+13 more tools listed on main page
MCP Graphql Forge Tools (16)
name
The name of the MCP tool
description
The description of the MCP tool
query
The GraphQL query to execute
inputs
The list of inputs defined by the MCP tool and passed into the GraphQL query as variables
type
The parameter type; can be 'string' or 'number'
required
Boolean value specifying if the attribute is required
annotations
MCP annotations that provide hints about the tool's behavior (optional)
title
A human-readable title for the tool, useful for UI display (optional)
readOnlyHint
If true, indicates the tool does not modify its environment (optional, default: false)
destructiveHint
If true, the tool may perform destructive updates (only meaningful when readOnlyHint is false) (optional, default: true)
idempotentHint
If true, calling the tool repeatedly with the same arguments has no additional effect (only meaningful when readOnlyHint is false) (optional, default: false)
openWorldHint
If true, the tool may interact with an "open world" of external entities (optional, default: true)