Spotify Listening History Parser MCP Server for WindsurfGive Windsurf instant access to 1 tools to Parse Spotify History

Name: Spotify Listening History Parser
Price: 29 USD
Availability: InStock
Rating: 5.0 (1 reviews)
Author: Vinkius

GDPR Free for Subscribers

Windsurf brings agentic AI coding to a purpose-built IDE. Connect Spotify Listening History Parser through Vinkius and Cascade will auto-discover every tool. ask questions, generate code, and act on live data without leaving your editor.

Ask AI about this MCP Server for Windsurf

Open in ChatGPT Open in Claude Open in Perplexity

The Spotify Listening History Parser MCP Server for Windsurf is a standout in the Industry Titans category — giving your AI agent 1 tools to work with, ready to go from day one.

Built for AI Agents by Vinkius

Vinkius delivers Streamable HTTP and SSE to any MCP client

Claude

ChatGPT

Cursor

Gemini

Windsurf

VS Code

JetBrains

Vercel

+ other MCP clients

Classic Setup·json

{
  "mcpServers": {
    "spotify-listening-history-parser": {
      "url": "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    }
  }
}

RecommendedModern Approach — Zero Configuration

Vinkius Desktop App

The modern way to manage MCP Servers — no config files, no terminal commands. Install Spotify Listening History Parser and 4,000+ MCP Servers from a single visual interface.

Download Free Open SourceNo signup required

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 Listening History Parser MCP Server

Spotify lets you request your full listening history via Privacy settings. The result is a massive JSON file with every song you ever played. This MCP aggregates it locally into actionable insights: top 30 artists, top 30 tracks, total hours, and unique counts.

Windsurf's Cascade agent chains multiple Spotify Listening History Parser tool calls autonomously. query data, analyze results, and generate code in a single agentic session. Paste Vinkius Edge URL, reload, and all 1 tools are immediately available. Real-time tool feedback appears inline, so you see API responses directly in your editor.

The Superpowers

Smart Aggregation: Millions of plays → clean top-30 rankings.
Total Hours Calculated: Know exactly how many hours you spent listening.
100% Local. Your music taste stays private.

The Spotify Listening History Parser MCP Server exposes 1 tools through the Vinkius. Connect it to Windsurf in under two minutes — credentials fully managed, no infrastructure to provision, no vendor lock-in. Your configuration, your data, your control.

All 1 Spotify Listening History Parser tools available for Windsurf

When Windsurf connects to Spotify Listening History Parser through Vinkius, your AI agent gets direct access to every tool listed below — spanning data-parsing, music-analytics, listening-history, and more. Every call runs in a secure, isolated environment with full audit visibility. Beyond a simple connection, you get real-time monitoring of agent activity, enterprise governance, and optimized token usage.

parse

Parse spotify history on Spotify Listening History Parser

The file is usually a JSON array of listening events. Parse a Spotify listening history JSON export (from Spotify Privacy or Google Takeout) and aggregate top artists, tracks, and total listening hours

Connect Spotify Listening History Parser to Windsurf via MCP

Follow these steps to wire Spotify Listening History Parser into Windsurf. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.

Open MCP Settings

Go to Settings → MCP Configuration or press Cmd+Shift+P and search "MCP"

Add the server

Paste the JSON configuration above into mcp_config.json

Save and reload

Windsurf will detect the new server automatically

Start using Spotify Listening History Parser

Open Cascade and ask: "Using Spotify Listening History Parser, help me...". 1 tools available

Why Use Windsurf with the Spotify Listening History Parser MCP Server

Windsurf provides unique advantages when paired with Spotify Listening History Parser through the Model Context Protocol.

Windsurf's Cascade agent autonomously chains multiple tool calls in sequence, solving complex multi-step tasks without manual intervention

Purpose-built for agentic workflows. Cascade understands context across your entire codebase and integrates MCP tools natively

JSON-based configuration means zero code changes: paste a URL, reload, and all 1 tools are immediately available

Real-time tool feedback is displayed inline, so you see API responses directly in your editor without switching contexts

Spotify Listening History Parser + Windsurf Use Cases

Practical scenarios where Windsurf combined with the Spotify Listening History Parser MCP Server delivers measurable value.

Automated code generation: ask Cascade to fetch data from Spotify Listening History Parser and generate models, types, or handlers based on real API responses

Live debugging: query Spotify Listening History Parser tools mid-session to inspect production data while debugging without leaving the editor

Documentation generation: pull schema information from Spotify Listening History Parser and have Cascade generate comprehensive API docs automatically

Rapid prototyping: combine Spotify Listening History Parser data with Cascade's code generation to scaffold entire features in minutes

Example Prompts for Spotify Listening History Parser in Windsurf

Ready-to-use prompts you can give your Windsurf agent to start working with Spotify Listening History Parser immediately.

"What was my most listened artist in 2024?"

"How many total hours did I spend on Spotify?"

"Show my top 5 most played songs of all time."

Troubleshooting Spotify Listening History Parser MCP Server with Windsurf

Common issues when connecting Spotify Listening History Parser to Windsurf through Vinkius, and how to resolve them.

Server not connecting

Check Settings → MCP for the server status. Try toggling it off and on.

Spotify Listening History Parser + Windsurf FAQ

Common questions about integrating Spotify Listening History Parser MCP Server with Windsurf.

How does Windsurf discover MCP tools?

Windsurf reads the mcp_config.json file on startup and connects to each configured server via Streamable HTTP. Tools are listed in the MCP panel and available to Cascade automatically.

Can Cascade chain multiple MCP tool calls?

Yes. Cascade is an agentic system. it can plan and execute multi-step workflows, calling several tools in sequence to accomplish complex tasks without manual prompting between steps.

Does Windsurf support multiple MCP servers?

Yes. Add as many servers as needed in mcp_config.json. Each server's tools appear in the MCP panel and Cascade can use tools from different servers in a single flow.