Skip to main content
Glama
wjmonde

lastfm-mcp

by wjmonde

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
HOSTNoHost interface to bind the HTTP server to. Often required to be '0.0.0.0' for cloud/container deployments.
LASTFM_API_KEYYesYour Last.fm API key for the server/operator.
LASTFM_USERNAMENoOptional default Last.fm username. If omitted, every tool call must include a username.
LASTFM_USER_AGENTNoUser agent string for Last.fm API requests. Defaults to 'lastfm-mcp/0.3.0' if not set.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
recent_scrobblesA

Get a Last.fm user’s most recent scrobbles. Read-only. Pass a username unless the server has a local default.

top_itemsB

Get top artists, albums, or tracks for a Last.fm user over a selectable period. Pass a username unless the server has a local default.

artist_historyA

Check whether a Last.fm user has listened to an artist and return the approximate total scrobble count. Pass a username unless the server has a local default.

rediscovery_candidatesA

Find historically significant artists with little or no listening in a recent Last.fm period. Uses an explainable heuristic, not a Last.fm recommendation endpoint.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.9/5.0

Scored across 4 tools

Disambiguation5/5

Each tool targets a clearly distinct purpose: top_items returns rankings, recent_scrobbles returns a listening stream, artist_history checks a specific artist, and rediscovery_candidates surfaces overlooked artists. There is little risk of an agent selecting the wrong tool for a given task.

Naming Consistency5/5

All four tool names follow the same lowercase snake_case noun-phrase pattern. Though not verb_noun, the convention is perfectly consistent and predictable across the set.

Tool Count5/5

Four tools form a compact, purposeful set for a niche Last.fm listening-history server. Each tool earns its place and the scope feels appropriately focused rather than bloated or thin.

Completeness4/5

The set covers the core Last.fm user-listening workflow: top items, recent activity, specific artist checks, and rediscovery candidates. Minor gaps like user profile info or detailed artist metadata are absent, but agents can still complete meaningful tasks without major dead ends.

Maintenance

ActivityMaintained
ResponsivenessNo issues