Figma MCP Server vs Spotify MCP Server

Figma MCP Server and Spotify MCP Server are both MCP servers but differ in their categories and capabilities. Figma MCP Server (coding, media) is There are three different Figma MCP servers and the install command on most listings belongs to the one Figma no longer leads with, so start with which you are choosing. **Figma's recommended server is now the hosted remote one at `https://mcp.figma.com/mcp`** — nothing to install, OAuth in the client, attached with `claude mcp add --transport http figma https://mcp.figma.com/mcp`. It is also the only one with the write and cross-file tools (`use_figma`, `generate_figma_design`, `generate_diagram`, `create_new_file`, `search_design_system`, asset upload and download). **The Dev Mode desktop server ships inside the Figma Desktop app** — enable it in Dev Mode (Shift+D) from the MCP server section of the inspect panel and the app opens a local endpoint at `http://127.0.0.1:3845/mcp`. Figma's docs now describe the desktop server as being for specific organisation and enterprise cases and recommend the remote one instead. Because it runs in the app, it reads whatever you have selected on the canvas: exact colors, typography, spacing, auto-layout constraints, component variants, and — the part a token-based reader cannot do — your Code Connect mappings, so it emits your component names rather than generic divs. It requires a Dev or Full seat on a paid plan and the desktop app must be open. The repository linked here is `figma/mcp-server-guide`, Figma's own setup guide; Figma does not publish the server's source. **The community alternative is Figma-Context-MCP by GLips** (15,500+ stars), installed as `npx figma-developer-mcp --figma-api-key=YOUR_FIGMA_ACCESS_TOKEN`. It authenticates with a Personal Access Token from Figma Settings → Personal Access Tokens and calls the REST API, so it needs no desktop app, works headlessly in CI, and can read any file your account can open — including from a free plan. It exposes the document JSON, node lookup by ID, component listing, text extraction, and rendered-image download. The practical split: pick the official server when design-to-code fidelity and Code Connect matter and you are already paying for Dev Mode; pick GLips when you need automation, a free plan, or a machine with no Figma app installed. Both let an assistant translate a frame into accurate React, Tailwind, or plain HTML/CSS instead of guessing from a screenshot. while Spotify MCP Server (media) is Marcel Marais's Spotify MCP Server is a lightweight TypeScript bridge between AI assistants and the Spotify Web API, letting Claude control playback and search a listener's library through natural language. It exposes tools for searching tracks/albums/artists/playlists, controlling playback (play, pause, skip, queue management), reading and modifying the current queue, and browsing a user's playlists and saved library. Authentication uses standard Spotify OAuth (client ID/secret from the Spotify Developer Dashboard) with a one-time login flow to obtain a refresh token, after which the server runs locally via the MCP stdio transport. Typical use: ask Claude to "queue up some upbeat workout music" or "what's currently playing," and it calls the Spotify API directly rather than requiring the user to switch to the Spotify app..

Choose Figma MCP Server if you need coding capabilities and prefer remote installation. Choose Spotify MCP Server if you need media capabilities and prefer npm installation. Consider your specific use case and integration requirements.

Yes, you can use multiple MCP servers together in Claude Desktop, Cursor, VS Code, and other MCP-compatible clients.Figma MCP Server and Spotify MCP Servercan complement each other if their capabilities don't overlap.