
Spotify Playlist Contact Extractor
Deprecated
Pricing
$6.00/month + usage

Spotify Playlist Contact Extractor
Deprecated
Discover a groundbreaking tool to supercharge your music promotion on Spotify! This intelligent actor connects directly with Spotify's API to find playlists based on your specific keywords, while also extracting key contact information from the playlist creators.
0.0 (0)
Pricing
$6.00/month + usage
0
Total users
3
Monthly users
3
Last modified
9 months ago
You can access the Spotify Playlist Contact Extractor programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, youโll need an Apify account and your API token, found in Integrations settings in Apify Console.
{ "mcpServers": { "apify": { "command": "npx", "args": [ "mcp-remote", "https://mcp.apify.com/sse?actors=ekodarkfirez/spotify-playlist-contact-extractor", "--header", "Authorization: Bearer <YOUR_API_TOKEN>" ] } }}
Configure MCP server with Spotify Playlist Scraper with User Contact Information
You have a few options for interacting with the MCP server:
Use
mcp.apify.com
viamcp-remote
from your local machine to connect and authenticate using OAuth or an API token (as shown in the JSON configuration above).Set up the connection directly in your MCP client UI by providing the URL
https://mcp.apify.com/sse?actors=ekodarkfirez/spotify-playlist-contact-extractor
along with an API token (or use OAuth).Connect to
mcp.apify.com
via Server-Sent Events (SSE), as shown below:
{ "mcpServers": { "apify": { "type": "sse", "url": "https://mcp.apify.com/sse?actors=ekodarkfirez/spotify-playlist-contact-extractor", "headers": { "Authorization": "Bearer <YOUR_API_TOKEN>" } } }}
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.