[ethan] Spotify MCP#133
Open
OccultSlolem wants to merge 6 commits into
Open
Conversation
Collaborator
Author
… overconfidence bugs and logo.
Collaborator
Author
|
The new commits address the following:
|
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.


Adds limited Spotify support to OpenSwarm! This is accomplished by opening Google Chrome on the user's machine and using the Playwright MCP with remote debugging to click all the buttons. The MCP will prevent changes on Spotify's end from breaking this functionality. Since Chrome is launched with the remote debugger flag attached, the user won't have to enable CDP or see a scary popup asking for permission to allow debugging. Also, once the user logs in on this Chrome window, they won't have to log in again. When Chrome is launched by a Python automation, macOS security normally blocks login cookies from being saved - this is worked around by use of the
--password-store=basicargument when launching Chrome, which uses a local encryption key. The--restore-last-sessionarg is also provided just in case.Features:
Limitations:
Future additions: