4,500+ servers built on MCP Fusion
Vinkius
Last.fm logo
Vinkius
CrewAI logo

How to Use the Last.fm MCP in CrewAI

Orchestrate specialized AI agent teams to analyze and curate Last.fm music profiles using CrewAI.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

Last.fm MCP on Cursor AI Code Editor MCP Client Last.fm MCP on Claude Desktop App MCP Integration Last.fm MCP on OpenAI Agents SDK MCP Compatible Last.fm MCP on Visual Studio Code MCP Extension Client Last.fm MCP on GitHub Copilot AI Agent MCP Integration Last.fm MCP on Google Gemini AI MCP Integration Last.fm MCP on Lovable AI Development MCP Client Last.fm MCP on Mistral AI Agents MCP Compatible Last.fm MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
CrewAI

Connect Last.fm MCP to CrewAI

Create your Vinkius account to connect Last.fm to CrewAI and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Run collaborative music research crews

The `get_artist_info` tool gives your research agent immediate access to artist bios and tags. Meanwhile, a separate analyst agent uses `get_top_albums` to map out discographies. CrewAI coordinates this collaboration by sharing memory between the agents. They build a comprehensive profile of an artist's career without making duplicate API calls.

Deploy autonomous curators with this MCP Server

The `get_loved_tracks` tool serves as the primary data source for your curation agent. It hands off the raw list to a secondary styling agent that drafts personalized music newsletters. You set up this multi-agent team to run completely autonomously. They pull the data via the MCP Server, analyze listening trends, and format the output.

Track listening trends across user segments

The `get_top_tracks` and `get_recent_tracks` tools allow your crew to monitor real-time shifts in user taste. One agent flags sudden spikes in play counts while another cross-references those tracks with popular tags. This multi-agent setup isolates the analytical heavy lifting from the retrieval process. Your application stays fast because the agents run their background evaluations asynchronously.

Setup guide

Set up Last.fm MCP in CrewAI

Prerequisites

  • Python 3.10+ installed
  • crewai package (pip install crewai)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Install CrewAI

    Run pip install crewai to install the framework. MCP support is built-in via the mcps parameter.

  2. 2

    Add the MCP URL to your agent

    Pass your Vinkius endpoint directly to the mcps list. Replace [YOUR_TOKEN_HERE] with your token from cloud.vinkius.com. CrewAI handles tool discovery and caching automatically.

  3. 3

    Kick off your crew

    Create a Crew with your agent and tasks. Call crew.kickoff() — the agent will automatically invoke Last.fm tools as needed.

crew.py
from crewai import Agent, Task, Crew

agent = Agent(
    role="Last.fm Analyst",
    goal="Access and analyze Last.fm data via MCP.",
    backstory="Expert analyst with direct Last.fm access.",
    mcps=[
        "https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp"
    ],
)

task = Task(
    description="List recent Last.fm transactions",
    agent=agent,
    expected_output="A summary of recent activity",
)

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

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about Last.fm MCP in CrewAI

You pass the server URL directly in the agent's mcps array or filter tools using the MCPServerHTTP class. This lets you give the researcher agent access to get_artist_info while reserving get_loved_tracks for the analyst agent.
Yes, the crew can run parallel tasks using get_user_info across several accounts. The manager agent then aggregates the listening trends into a single collaborative report.
It connects via standard HTTP or SSE transports. You simply provide the endpoint URL to your CrewAI tools configuration, and the framework parses the tool schemas automatically.
Yes, you can use a tool filter to restrict access. This prevents your creative writing agent from accidentally triggering raw data calls like get_top_tags.
Only your local CrewAI process sees the raw loved tracks and profile data. Vinkius handles the MCP connection through a zero-trust gateway, ensuring no personal music data is cached or exposed.

Start using the Last.fm MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 10 tools

We've already built the connector for Last.fm. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 10 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.