Skip to main content
Glama
ldgnu

mcp-slskd

by ldgnu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SLSKD_HOSTNoslskd API endpointhttp://127.0.0.1:5030
SLSKD_PASSNoslskd web UI passwordslskd
SLSKD_USERNoslskd web UI usernameslskd
SLSKD_API_KEYNoAPI key (alternative to user/pass)

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": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
search_musicA
Search for music files on Soulseek.

Args:
    query: Search text (artist, track, album)
    limit: Max results to return (default 20)

Returns:
    List of search results with username, filename, size, etc.
download_musicA
Download a file from a Soulseek user.

Args:
    username: Soulseek username who has the file
    filename: Full filename path as returned by search
    size: File size in bytes

Returns:
    Status message
download_statusA
Check status of active downloads.

Returns:
    List of active/queued downloads with progress
browse_userA
Browse a Soulseek user's shared files.

Args:
    username: Soulseek username to browse

Returns:
    List of directories and files shared by the user
search_last_resultsA
Get cached results from the last search for a query.

Args:
    query: The search text used previously

Returns:
    Cached results, or empty list if not found

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

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

A4.1/5.0

Scored across 5 tools

Disambiguation4/5

Tools are mostly distinct: browse_user explores a user's files, search_music performs a new search, download_music starts a download, download_status checks progress, and search_last_results fetches cached results. The only potential confusion is between search_music and search_last_results, but descriptions clarify that one performs a new query and the other retrieves previous results.

Naming Consistency5/5

All tool names follow a consistent verb_noun pattern in snake_case (browse_user, search_music, download_music, download_status, search_last_results). The pattern is predictable and readable, with no mixed conventions.

Tool Count5/5

Five tools is well-scoped for a music download client, covering the essential actions (search, browse, download, status) without unnecessary redundancy. The count feels appropriate for the domain.

Completeness4/5

The core workflow is covered: search for music, browse user shares, download files, and check download status. However, missing operations like cancel or pause downloads represent a minor gap that agents may need to work around, though not critical for basic usage.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources