Skip to main content
Glama
frank-lautfm

lautfm-mcp

by frank-lautfm
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to lautfm-mcp

No user-submitted related servers found.

    Related Servers

    • lastfm-mcp

      ndyakov
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server for the Last.fm API, exposing artist, album, track, chart, and user data as read-only tools. Supports optional writes, auth, and experimental methods over stdio or HTTP.
      MIT

    • mcp-radio

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that wraps the Radio Browser API to search radio stations, list countries, and discover genres. Enables AI agents to find and browse radio stations without authentication.
      51 npm
      MIT

    • lastfm-mcp

      dkfancska
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for the Last.fm API that enables LLM agents to access music data including user profiles, listening history, top charts, search, and artist/album/track metadata.
      16
      MIT

    • radiobrowser-api-mcp

      maxim75
      F
      license
      B
      quality
      B
      maintenance
      Enables searching and browsing internet radio stations from the Radio Browser directory, retrieving live now-playing track information from station streams via ICY/Shoutcast metadata, and interacting with directory data through MCP tools without requiring API keys.
      29
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.1/5.0

    Scored across 40 tools

    Disambiguation4/5

    The tools are largely distinct, with clear resource+action separation across playlists, tracks, schedules, users, automation, and live info. A few pairs like get_track_stats/get_track_stats_period and get_all_track_tags/get_track_tags_for_ids could momentarily confuse, but descriptions disambiguate.

    Naming Consistency4/5

    All names use snake_case with a verb_noun structure, which is highly predictable. Minor inconsistencies exist in verb choice: creation uses both add_ (add_playlist) and create_ (create_automation_algorithm), and deletion uses both remove_ (remove_station_user) and delete_ (delete_playlist).

    Tool Count2/5

    With 40 tools, the surface is well beyond the recommended 3-15 range and likely increases cognitive load and misselection risk. Although the domain is broad, this count feels excessive for an MCP server.

    Completeness4/5

    The surface covers CRUD for playlists, tracks, automation, users, and schedules, plus live info and stats. Missing track creation/upload and station creation/deletion are notable gaps for full lifecycle coverage, though they may be outside the API scope.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources