ScrobblerContext - Last.fm MCP Server

Created By
tfmarta year ago
MCP Server for Last.FM APIs, built in Swift
Overview

What is ScrobblerContext?

ScrobblerContext is a Model Context Protocol (MCP) server that provides access to Last.fm's music database, built in Swift. It enables AI assistants to search for music, manage user libraries, and scrobble tracks.

How to use ScrobblerContext?

To use ScrobblerContext, install it via npm, set up your Last.fm API credentials, and run the server. You can also build it from source if preferred.

Key features of ScrobblerContext?

  • Secure authentication with OAuth flow
  • Search and retrieve detailed information about artists, albums, and tracks
  • Access user data including listening history and statistics
  • Scrobble tracks and manage now playing status

Use cases of ScrobblerContext?

  1. Integrating music search capabilities into AI assistants.
  2. Managing personal music libraries and scrobbling tracks.
  3. Analyzing user listening habits and preferences.

FAQ from ScrobblerContext?

  • What is MCP?
    MCP stands for Model Context Protocol, a standard for communication between clients and servers.

  • Is ScrobblerContext free to use?
    Yes! ScrobblerContext is open-source and free to use under the MIT license.

  • What are the prerequisites for installation?
    You need Swift 6.0+ and Last.fm API credentials to run ScrobblerContext.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
tfmart
Star
0
Language
Swift
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

29 minutes ago