How do I get a Spotify Access Token?

Go to the Spotify Developer Dashboard, log in with your Spotify account, click 'Create App', and generate a token. The token expires every hour.

What are 'Audio Features'?

Audio features are data points Spotify calculates for every track, including Danceability (0-100%), Energy (0-100%), Tempo (BPM), and Valence (Positivity). You can use `get_audio_features` to analyze a song's vibe.

Can I control playback on any device?

Yes! The player tools (`play`, `pause`, `add_to_queue`) work on your currently active Spotify device, whether it's your phone, computer, or smart speaker.

Does it support podcasts?

This integration currently focuses on music and library management. Podcast playback is not directly exposed as native commands.

Spotify Music MCP Server for CrewAI 13 tools — connect in under 2 minutes

Name: Spotify Music
Availability: InStock
Author: Vinkius

docs.crewai.com/mcp/overview

Built by Vinkius GDPR 13 Tools Framework

Connect your CrewAI agents to Spotify Music through Vinkius, pass the Edge URL in the `mcps` parameter and every Spotify Music tool is auto-discovered at runtime. No credentials to manage, no infrastructure to maintain.

Get MCP Server for AI Agents

ASK AI ABOUT THIS MCP SERVER

Open in ChatGPT Open in Claude Open in Perplexity

Vinkius supports streamable HTTP and SSE.

python

from crewai import Agent, Task, Crew

agent = Agent(
    role="Spotify Music Specialist",
    goal="Help users interact with Spotify Music effectively",
    backstory=(
        "You are an expert at leveraging Spotify Music tools "
        "for automation and data analysis."
    ),
    # Your Vinkius token. get it at cloud.vinkius.com
    mcps=["https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"],
)

task = Task(
    description=(
        "Explore all available tools in Spotify Music "
        "and summarize their capabilities."
    ),
    agent=agent,
    expected_output=(
        "A detailed summary of 13 available tools "
        "and what they can do."
    ),
)

crew = Crew(agents=[agent], tasks=[task])
result = crew.kickoff()
print(result)

Fully ManagedVinkius Servers

60%Token savings

High SecurityEnterprise-grade

IAMAccess control

EU AI ActCompliant

DLPData protection

V8 IsolateSandboxed

Ed25519Audit chain

<40msKill switch

Stream every event to Splunk, Datadog, or your own webhook in real-time

* Every MCP server runs on Vinkius-managed infrastructure inside AWS - a purpose-built runtime with per-request V8 isolates, Ed25519 signed audit chains, and sub-40ms cold starts optimized for native MCP execution. See our infrastructure

About Spotify Music MCP Server

Connect Spotify to any AI agent and turn your voice or text prompts into music actions — search millions of tracks, analyze audio features, get personalized recommendations, and control your playback.

When paired with CrewAI, Spotify Music becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call Spotify Music tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

What you can do

Search Library — Find any track, artist, album, or playlist by name
Player Control — Play, pause, and add tracks to your queue directly
Audio Analytics — Get deep insights like danceability, energy, valence, and tempo
Recommendations — Discover new music based on your favorite artists or genres
Library Management — View your playlists and get details about albums or artists
New Releases — Discover the newest albums dropping on Spotify

The Spotify Music MCP Server exposes 13 tools through the Vinkius. Connect it to CrewAI in under two minutes — no API keys to rotate, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

How to Connect Spotify Music to CrewAI via MCP

Follow these steps to integrate the Spotify Music MCP Server with CrewAI.

Install CrewAI

Run pip install crewai

Replace the token

Replace [YOUR_TOKEN_HERE] with your Vinkius token from cloud.vinkius.com

Customize the agent

Adjust the role, goal, and backstory to fit your use case

Run the crew

Run python crew.py. CrewAI auto-discovers 13 tools from Spotify Music

Why Use CrewAI with the Spotify Music MCP Server

CrewAI Multi-Agent Orchestration Framework provides unique advantages when paired with Spotify Music through the Model Context Protocol.

Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the `mcps` parameter and agents auto-discover every available tool at runtime

Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

Spotify Music + CrewAI Use Cases

Practical scenarios where CrewAI combined with the Spotify Music MCP Server delivers measurable value.

Automated multi-step research: a reconnaissance agent queries Spotify Music for raw data, then a second analyst agent cross-references findings and flags anomalies. all without human handoff

Scheduled intelligence reports: set up a crew that periodically queries Spotify Music, analyzes trends over time, and generates executive briefings in markdown or PDF format

Multi-source enrichment pipelines: chain Spotify Music tools with other MCP servers in the same crew, letting agents correlate data across multiple providers in a single workflow

Compliance and audit automation: a compliance agent queries Spotify Music against predefined policy rules, generates deviation reports, and routes findings to the appropriate team

Spotify Music MCP Tools for CrewAI (13)

These 13 tools become available when you connect Spotify Music to CrewAI via MCP:

add_to_queue

Add a track to the playback queue

get_album

Get information about a specific album

get_artist

Get information about a specific artist

get_audio_features

Get audio features for a track (Danceability, Energy, Tempo, etc)

get_current_track

Returns empty if nothing is playing. Get the track currently playing on the user's device

get_new_releases

Get a list of new album releases

get_playlist

Get details of a specific playlist

get_recommendations

Get recommended tracks based on seed artists, genres, or tracks

get_track

Get detailed information about a specific track

get_user_playlists

Get the current user's playlists

pause

Pause playback on the user's device

play

Start or resume playback on the user's device

search

Search for tracks, artists, albums, or playlists on Spotify

Example Prompts for Spotify Music in CrewAI

Ready-to-use prompts you can give your CrewAI agent to start working with Spotify Music immediately.

"Play some energetic Jazz for studying."

"What are the audio features for 'Blinding Lights'?"

"Show me the top 5 new releases."

Troubleshooting Spotify Music MCP Server with CrewAI

Common issues when connecting Spotify Music to CrewAI through the Vinkius, and how to resolve them.

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Spotify Music + CrewAI FAQ

Common questions about integrating Spotify Music MCP Server with CrewAI.

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.