Soulseek MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DOWNLOAD_PATH | No | Directory for downloaded files | ./downloads |
| SOULSEEK_PASSWORD | Yes | Your Soulseek account password | |
| SOULSEEK_USERNAME | Yes | Your Soulseek account username |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| searchC | Search for songs/files on the Soulseek network. Returns a list of available files matching the query. |
| downloadB | Download a file from a Soulseek peer. Use the username and filename from search results. |
| get_statusA | Check the current connection status to the Soulseek network. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose with no overlap: download handles file retrieval, get_status checks network connectivity, and search finds files. The descriptions clearly differentiate their functions, making misselection unlikely.
All three tools follow a consistent verb_noun pattern (download, get_status, search), with clear and descriptive names that align well with their functions. There are no deviations in naming style.
With only 3 tools, the server feels thin for a file-sharing network like Soulseek. While it covers basic operations (search, download, status), it lacks tools for managing downloads, user interactions, or advanced search features that might be expected in this domain.
The tools cover core workflows (search and download) but have notable gaps. There is no way to manage downloads (e.g., pause, cancel, list active), interact with users (e.g., messaging, browsing shares), or handle errors, which could lead to agent failures in more complex scenarios.