Hi team! 👋 I'm trying to use Rube to manage Spotify saved podcast episodes but hitting two blockers: Issue 1: Missing OAuth Scopes Tools

SPOTIFY_GET_USER_S_SAVED_EPISODES

and

SPOTIFY_REMOVE_USER_S_SAVED_EPISODES

exist but fail with:

403 Forbidden: "Insufficient client scope"

The default Spotify connection doesn't include

user-library-read

and

user-library-modify

scopes needed for these endpoints. Issue 2: Can't Use Custom Credentials as Workaround When I try to click "Modify Auth" to use my own Spotify OAuth credentials (which I think would let me request the scopes I need), I get:

404 Error: Request failed with status code 404

Request: Can anyone advise a workaround or tell me what I’m doing wrong? Thanks

Hey @mostflyprada, we are checking this.

Thank you!

@mostflyprada, we will add

user-library-modify

and

user-library-read

scopes to our default authConfig and there seems to be an issue with

SPOTIFY_REMOVE_USER_S_SAVED_EPISODES

and we'll push a fix for the same. For Issue 2, could you specify how you are trying to Modify Auth? you can actually Manage your auth config from dashboard or [programatically](https://docs.composio.dev/rest-api/auth-configs/patch-auth-configs-by-nanoid). https://cdn.discordapp.com/attachments/1453453740018499624/1453639798051836030/Screenshot_2025-12-25_at_12.11.22.png?ex=694e2f0f&is=694cdd8f&hm=69bf87d9af453716a94bf63ec839398be2bdda1304c8afbea0fdc39b08faca9d&

@Uday thank you! What’s the ETA on adding to the scopes so I have some context? For issue 2 - I’m using Rube and don’t see that. Should I try composio directly?

@mostflyprada, You should be able to modify the app to use your custom creds by disabling and re-enabling the app(ref attachment). Let me know if you are unable to perform the action along with a screen recording, as it'll help us in debugging. Also, the updated scopes should be live in around ~1-2 weeks. https://cdn.discordapp.com/attachments/1453453740018499624/1453806450601365559/Screenshot_2025-12-25_at_23.14.45.png?ex=694eca44&is=694d78c4&hm=73287ee0c457a03098843f19c2758bb99288fe32b37e1fa3a0bd89dbe833c9af&

Turns out I was using my own custom creds to begin with. Just created a new app and reconnected Spotify with those just to see that the requested scopes are hardcoded so it doesn’t matter if I have cusfom creds. Sorry about that. Rube chat told me that might solve the problem. I think I just have to wait for the scopes to be updated.

Hi, We've added the scopes to our default Auth config. Let me know if you face any issues.

@Uday Hey there. Im having almost the same problems using Composios MCP Server. My agent can play songs and read some info about my spotify account but most actions fail. cant create playlists, read playlists etc. "Scope Issue". I added an app in my spotify developer settings and connected it to composio (oauth2). is this the correct way? My agent then sent me a link to connect composio and spotify, which was successfull. been stuck on this issue for quite a while now and im beginning to believe its an issue on composios side

Hi there, Thanks for the nudge, and sorry this has dragged on. Two separate things are going on: • The 403 "insufficient scope": those saved-episode tools need

user-library-read

(read) and

user-library-modify

(remove). The scopes Composio requests for Spotify are set on our side, not by your own credentials, and those library scopes aren't in the default set yet, which is why the calls fail. You can't add them yourself. This is logged internally. I don't have a firm date to share, so I won't promise one. Once the scopes are in place, you'll need to disconnect and reconnect Spotify in Rube so they land on a fresh token. • The 404 on "Modify Auth": that's expected on Rube. Rube handles the OAuth connection inline and doesn't expose an auth config for you to edit or swap, so there's nothing for "Modify Auth" to point at. It isn't something you did wrong. If anything's still off after you reconnect, reply here with the tool name and the exact error and we'll dig in.