StreamerSongList MCP Server

# StreamerSongList API Testing Report **Date**: October 12, 2025 **Test Streamer**: vu_vu (ID: 21108) **API Base URL**: https://api.streamersonglist.com/v1/ ## Executive Summary After comprehensive testing of the StreamerSongList API, we discovered significant discrepancies between the documented API capabilities (in SSLv1-keydata.md) and the actual live implementation. Only 4 out of 11+ documented endpoints are functional, with the rest returning 404 errors. ## Working Endpoints ✅ ### 1. Get Streamer Information **Endpoint**: `GET /v1/streamers/{streamerName}` **Status**: ✅ WORKING **Authentication**: None required **Response**: Comprehensive streamer configuration including: - Basic info (ID, name, creation date) - Queue settings (limits, permissions, request modes) - Attributes array (tags with subscriber restrictions) - Global commands (23 available commands) - Command messages (automated responses) - Moderator settings **Example Response Structure**: ```json { "id": 21108, "name": "vu_vu", "allowDuplicates": true, "requestsActive": true, "attributes": [...], "globalCommands": [...], "commandMessages": [...] } ``` ### 2. Get Current Queue **Endpoint**: `GET /v1/streamers/{streamerName}/queue` **Status**: ✅ WORKING **Authentication**: None required **Parameters**: `limit`, `offset` for pagination **Response**: Queue items with: - Position, song details, request information - Donation amounts, notes, creation timestamps - Full song objects embedded ### 3. Get Streamer Song List **Endpoint**: `GET /v1/streamers/{streamerName}/songs` **Status**: ✅ WORKING **Authentication**: None required **Parameters**: Pagination support **Response**: Complete song catalog (266 songs for vu_vu) including: - Song metadata (title, artist, creation date) - Play statistics (times played, last played) - Attribute associations - Minimum donation amounts ### 4. Get Individual Song Details **Endpoint**: `GET /v1/streamers/{streamerName}/songs/{songId}` **Status**: ✅ WORKING **Authentication**: None required **Response**: Detailed song information including: - Basic metadata (title, artist, active status) - Musical information (tabs, lyrics, chords, capo) - Play history and statistics - Attribute associations ## Non-Working Endpoints ❌ The following endpoints are documented but return **404 Not Found**: ### Queue Management - `GET /v1/streamers/{streamerName}/queue/stats` - Queue statistics - `POST /v1/streamers/{streamerName}/requests` - Create song request - `PUT /v1/streamers/{streamerName}/requests/{requestId}` - Update request - `DELETE /v1/streamers/{streamerName}/requests/{requestId}` - Delete request ### History & Analytics - `GET /v1/streamers/{streamerName}/history` - Play history - `GET /v1/streamers/{streamerName}/stats` - Stream statistics ### Advanced Features - `GET /v1/streamers/{streamerName}/overlay` - Overlay data - `GET /v1/streamers/{streamerName}/attributes` - Attribute management - `GET /v1/streamers/{streamerName}/polls` - Poll management - `GET /v1/streamers/{streamerName}/saved-queues` - Saved queues - `GET /v1/streamers/{streamerName}/offline-queues` - Offline queues ### Global Search - `GET /v1/songs/search` - Global song search - `GET /v1/songs/{songId}` - Global song details ## Authentication Testing ### Public Endpoints - Working endpoints require **no authentication** - CORS headers allow browser access - Rate limiting appears minimal or non-existent ### Protected Endpoints - POST requests to existing endpoints return "401 Unauthorized" - Suggests write operations require authentication - Authentication method not documented (likely API keys or OAuth) ## Data Quality Analysis ### Rich Data Available 1. **Streamer Configuration**: Comprehensive settings including request limits, subscriber tiers, command configurations 2. **Song Metadata**: Detailed information including tabs, lyrics, chords for musical performance 3. **Queue Management**: Real-time queue data with request details and donation information 4. **Attribute System**: Tag-based categorization with subscriber restrictions ### Missing Features 1. **Historical Data**: No access to play history or statistics 2. **Advanced Management**: No poll, saved queue, or overlay management 3. **Search Functionality**: No global or advanced search capabilities 4. **Analytics**: No statistics or analytics endpoints ## MCP Server Impact Assessment ### Current Implementation Status The existing MCP server (`src/server.js`) contains 11 tools, but only 4 have real API support: 1. **`getStreamerByName`** ✅ - Fully functional 2. **`getQueue`** ✅ - Fully functional 3. **`getQueueStats`** ❌ - Not implemented by this server; upstream endpoint returns 404 4. **`manageSongRequest`** ❌ - Returns simulated data 5. **`monitorQueue`** ✅ - Works with real queue data 6. **`getPlayHistory`** ❌ - Returns simulated data 7. **`searchSongs`** ❌ - Returns simulated data 8. **`getSongDetails`** ✅ - Fully functional 9. **`manageSongAttributes`** ❌ - Returns simulated data 10. **`getOverlayData`** ❌ - Returns simulated data 11. **`getStreamStats`** ❌ - Returns simulated data ### Recommendations #### Immediate Actions 1. **Update Documentation**: Correct README.md to reflect actual API capabilities 2. **Enhance Working Tools**: Improve the 4 functional tools with additional parameters and features 3. **Client-Side Features**: Implement search and filtering using the songs endpoint data #### Future Enhancements 1. **Authentication Integration**: Implement API key or OAuth authentication when available 2. **Simulated Data Improvement**: Enhance mock data for non-functional endpoints to be more realistic 3. **Alternative Data Sources**: Consider additional data sources for missing functionality ## Technical Findings ### API Performance - Response times: ~200-500ms for working endpoints - Data format: Consistent JSON structure - Error handling: Clear HTTP status codes and messages - Pagination: Supported on songs and queue endpoints ### API Design Patterns - RESTful design with proper HTTP methods - Consistent naming conventions - Logical resource hierarchy - Proper HTTP status codes ### Documentation Gaps - SSLv1-keydata.md describes comprehensive API that doesn't exist - No public OpenAPI/Swagger specification available - Authentication methods not documented - Rate limits not specified ## Conclusion The StreamerSongList API provides solid foundational functionality for basic streamer information, queue management, and song catalog access. However, the advanced features described in internal documentation are not available in the live implementation. The current MCP server appropriately handles this limitation by providing simulated data for advanced features while maintaining full functionality for available endpoints. For production use, the server should be updated to clearly document which features use real data versus simulated responses. **API Maturity Level**: Basic (Read-only public endpoints available) **Recommended for Production**: Yes, with clear documentation of limitations **Enhancement Potential**: High, pending API development or authentication access