streamersonglist

This MCP server exposes a read-only set of tools from StreamerSongList, allowing you to query streamer configurations, current queues, full song libraries, and detailed song information. Tools include getStreamerByName, getQueue, getSongs, searchSongs, getSongDetails, and monitorQueue, all of which operate on public, read-only data from the StreamerSongList API. You can experiment with the tools via the MCP Inspector or by sending JSON-RPC like requests to the server. Typical usage involves specifying the tool name and appropriate arguments such as streamerName, query terms, or pagination details to retrieve structured results for planning, discovery, and automation tasks. The server is designed to work well with Claude Desktop and other MCP clients for conversational access to music data and streaming insights.

Prerequisites:

• Node.js 18+ installed on your machine
• npm (comes with Node.js)

Install and run locally:

1. Ensure Node.js 18+ is installed. Verify with: node -v npm -v
2. Install dependencies and start the server (from the project root): npm install npm start
3. Validate startup by querying the available tools via the inspector or a simple stdio interaction as shown in the docs. Example to test using stdio: printf '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}\n' | node src/server.js

Optional: if you want to run via npx (as recommended in the README): npx streamersonglist-mcp

Environment configuration (optional):

• You can set a default streamer name that is used when no streamerName is provided by clients: DEFAULT_STREAMER=public_streamer
• You can override the API base with SSL_API_BASE if needed (default is https://api.streamersonglist.com/v1).

These steps align with the repository's Quick Start and environment guidance in the README.

Tips and caveats:

• The server exposes read-only endpoints from StreamerSongList; do not rely on authentication for these endpoints as they are public.
• If you plan to run multiple clients, consider setting DEFAULT_STREAMER to a sensible default to improve UX in conversational interfaces.
• The environment example shows DEFAULT_STREAMER and SSL_API_BASE; you can override these via the mcp config env section or through your shell when launching the server.
• When testing, you can use the MCP Inspector tool to explore tools and run requests interactively. This helps validate responses and understand tool schemas before integrating into workflows.
• The project uses real API data; respect rate limits and avoid excessive polling to keep the StreamerSongList API healthy for everyone.
• The npm package name for this MCP server is streamersonglist-mcp; you can install or run via npm or npx as shown in the Quick Start.