Spotify Listening History Parser MCP Server for LlamaIndexGive LlamaIndex instant access to 1 tools to Parse Spotify History
GDPR Free for SubscribersLlamaIndex specializes in data-aware AI agents that connect LLMs to structured and unstructured sources. Add Spotify Listening History Parser as an MCP tool provider through Vinkius and your agents can query, analyze, and act on live data alongside your existing indexes.
Ask AI about this MCP Server for LlamaIndex
The Spotify Listening History Parser MCP Server for LlamaIndex is a standout in the Industry Titans category — giving your AI agent 1 tools to work with, ready to go from day one.
Vinkius delivers Streamable HTTP and SSE to any MCP client
Geminiimport asyncio
from llama_index.tools.mcp import BasicMCPClient, McpToolSpec
from llama_index.core.agent.workflow import FunctionAgent
from llama_index.llms.openai import OpenAI
async def main():
# Your Vinkius token. get it at cloud.vinkius.com
mcp_client = BasicMCPClient("https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp")
mcp_tool_spec = McpToolSpec(client=mcp_client)
tools = await mcp_tool_spec.to_tool_list_async()
agent = FunctionAgent(
tools=tools,
llm=OpenAI(model="gpt-4o"),
system_prompt=(
"You are an assistant with access to Spotify Listening History Parser. "
"You have 1 tools available."
),
)
response = await agent.run(
"What tools are available in Spotify Listening History Parser?"
)
print(response)
asyncio.run(main())
* 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.
LlamaIndex agents combine Spotify Listening History Parser tool responses with indexed documents for comprehensive, grounded answers. Connect 1 tools through Vinkius and query live data alongside vector stores and SQL databases in a single turn. ideal for hybrid search, data enrichment, and analytical workflows.
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 LlamaIndex 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 LlamaIndex
When LlamaIndex 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 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 LlamaIndex via MCP
Follow these steps to wire Spotify Listening History Parser into LlamaIndex. The entire setup takes under two minutes — your credentials stay safe behind Vinkius.
Install dependencies
pip install llama-index-tools-mcp llama-index-llms-openaiReplace the token
[YOUR_TOKEN_HERE] with your Vinkius tokenRun the agent
agent.py and run: python agent.pyExplore tools
Why Use LlamaIndex with the Spotify Listening History Parser MCP Server
LlamaIndex provides unique advantages when paired with Spotify Listening History Parser through the Model Context Protocol.
Data-first architecture: LlamaIndex agents combine Spotify Listening History Parser tool responses with indexed documents for comprehensive, grounded answers
Query pipeline framework lets you chain Spotify Listening History Parser tool calls with transformations, filters, and re-rankers in a typed pipeline
Multi-source reasoning: agents can query Spotify Listening History Parser, a vector store, and a SQL database in a single turn and synthesize results
Observability integrations show exactly what Spotify Listening History Parser tools were called, what data was returned, and how it influenced the final answer
Spotify Listening History Parser + LlamaIndex Use Cases
Practical scenarios where LlamaIndex combined with the Spotify Listening History Parser MCP Server delivers measurable value.
Hybrid search: combine Spotify Listening History Parser real-time data with embedded document indexes for answers that are both current and comprehensive
Data enrichment: query Spotify Listening History Parser to augment indexed data with live information before generating user-facing responses
Knowledge base agents: build agents that maintain and update knowledge bases by periodically querying Spotify Listening History Parser for fresh data
Analytical workflows: chain Spotify Listening History Parser queries with LlamaIndex's data connectors to build multi-source analytical reports
Example Prompts for Spotify Listening History Parser in LlamaIndex
Ready-to-use prompts you can give your LlamaIndex 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 LlamaIndex
Common issues when connecting Spotify Listening History Parser to LlamaIndex through Vinkius, and how to resolve them.
BasicMCPClient not found
pip install llama-index-tools-mcpSpotify Listening History Parser + LlamaIndex FAQ
Common questions about integrating Spotify Listening History Parser MCP Server with LlamaIndex.
How does LlamaIndex connect to MCP servers?
Can I combine MCP tools with vector stores?
Does LlamaIndex support async MCP calls?
Explore More MCP Servers
View all →
Facebook Pages
12 toolsManage your Facebook Pages via AI — publish posts, list feed, track insights, and engage with comments directly through your agent.
ChargeDesk
8 toolsManage billing and payments via ChargeDesk — track charges, refund payments, and manage customers across multiple gateways directly from any AI agent.
CrowdStrike Falcon
8 toolsDetect threats, manage endpoints, investigate incidents, and query telemetry from CrowdStrike Falcon — the #1 endpoint detection and response platform.
Tuputech Moderation
10 toolsBring Tuputech's Advanced Anti-Spam and AI Evaluation endpoints to your server. Scan text, images, and audio automatically via AI.