Scrobblercontext MCP Server

Last.fm MCP Server - Search music, manage libraries, and scrobble tracks. The scrobblercontext mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 14 defined tools rather than through you.

What it actually does

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.

• Authentication — Secure browser OAuth flow with session persistence
• Artist Operations — Search artists, get detailed information, find similar artists
• Album Operations — Search albums, get track listings and metadata
• Track Operations — Search tracks, get details and recommendations
• User Data — Access listening history, statistics, and social features
• Scrobbling — Submit track plays, update now playing status, love/unlove tracks

Its toolset

Everything the assistant can do here goes through one of these:

• authenticate_browser — Start OAuth flow in browser
• set_session_key — Set existing session key
• check_auth_status — Check authentication status
• restore_session — Restore saved session
• logout — Clear authentication
• search_artist — Search for artists
• get_artist_info — Get artist details & biography
• get_similar_artists — Find similar artists
• get_artist_correction — Get corrected artist name
• get_artist_tags — Get artist tags
• get_artist_top_albums — Get artist's top albums
• get_artist_top_tracks — Get artist's top tracks

Configuration

You will need 2 environment variables: LASTFM_API_KEY, LASTFM_SECRET_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Installation goes through your MCP client rather than a global install: point it at scrobblercontext-mcp on npm and it is fetched when the client starts. The copy-paste blocks for Claude Desktop, Claude Code and Cursor are further down this page.

When to reach for it

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Scrobblercontext's toolset — authenticate_browser, set_session_key, check_auth_status and 11 more — is a fair guide to whether it matches your workflow. It is maintained by tfmart; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Scrobblercontext.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the scrobblercontext mcp server does with a few real requests.