Bring Data Parsing
to Windsurf
Learn how to connect Spotify Listening History Parser to Windsurf and start using 1 AI agent tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code.
GDPR Free for SubscribersCompatible with every major AI agent and IDE
Gemini
What is the 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.
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.
Built-in capabilities (1)
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
Why Windsurf?
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.
- —
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 in Windsurf
Spotify Listening History Parser and 4,000+ other MCP servers. One platform. One governance layer.
Teams that connect Spotify Listening History Parser to Windsurf through Vinkius don't need to source, host, or maintain individual MCP servers. Every tool call runs inside a hardened runtime with credential isolation, DLP, and a signed audit chain.
Raw MCP | Vinkius | |
|---|---|---|
| Server catalog | Find and host yourself | 4,000+ managed |
| Infrastructure | Self-hosted | Sandboxed V8 isolates |
| Credential handling | Plaintext in config | Vault + runtime injection |
| Data loss prevention | None | Configurable DLP policies |
| Kill switch | None | Global instant shutdown |
| Financial circuit breakers | None | Per-server limits + alerts |
| Audit trail | None | Ed25519 signed logs |
| SIEM log streaming | None | Splunk, Datadog, Webhook |
| Honeytokens | None | Canary alerts on leak |
| Custom domains | Not applicable | DNS challenge verified |
| GDPR compliance | Manual effort | Automated purge + export |
Why teams choose Vinkius for Spotify Listening History Parser in Windsurf
The Spotify Listening History Parser 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. All 1 tools execute in hardened sandboxes optimized for native MCP execution.
Your AI agents in Windsurf only access the data you authorize, with DLP that blocks sensitive information from ever reaching the model, kill switch for instant shutdown, and up to 60% token savings. Enterprise-grade infrastructure, zero maintenance.
* 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
How Vinkius secures
Spotify Listening History Parser for Windsurf
Every tool call from Windsurf to the Spotify Listening History Parser MCP Server is protected by DLP redaction, cryptographic audit chains, V8 sandbox isolation, kill switch, and financial circuit breakers.
Frequently asked questions
How do I get my Spotify data?
Go to spotify.com/account/privacy. Request your data. Spotify emails you a download link within 30 days.
Does it work with Apple Music?
This parser is optimized for Spotify's JSON format. Apple Music exports use a different structure.
Is my listening data sent to the cloud?
No. All aggregation happens locally. Only the top-30 lists and totals are sent to the AI.
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.
Server not connecting
Check Settings → MCP for the server status. Try toggling it off and on.
Explore More MCP Servers
View all →
Steam
7 toolsAccess game data, player profiles, and community content from the world largest PC gaming platform and digital storefront.
ClockShark
10 toolsTrack field crew hours with GPS-verified timesheets, job costing, and scheduling that keeps construction teams on budget.
Leadfeeder
9 toolsBring Leadfeeder B2B visit intelligence to your AI. Discover which companies visit your website natively.
KeyPay
10 toolsManage payroll, employees, and pay runs via the Employment Hero Payroll (KeyPay) API.