Get into Favoright and connect your assistant

1. Open Sign in, enter your email, complete Turnstile, and enter the six-digit code.
2. In the app header, connect Apple Music (always available) or Spotify when it appears in the platform switcher.
3. Browse Home, Favorites, Library, or Lists for the selected provider.
4. Optional: connect an MCP client with OAuth, sync favorite songs, ask your assistant to search and create a playlist draft, then open the approval URL yourself to review and create the playlist.

1. Open Sign in from the landing page, this help page, or the app when prompted.
2. Enter the email address you want to use with Favoright.
3. Complete the Turnstile check, then press Send sign-in code.
4. Check your inbox for a six-digit code and enter it on the next screen.
5. After verification, Favoright opens the app. If you arrived from MCP authorization, you return to the consent screen automatically once signed in.

Sign-in troubleshooting

• Code delayed or expired — request a new code from the email step. Codes are short-lived.
• Wrong email — use Use a different email to restart with the correct address.
• Turnstile failed — refresh the page and complete the check again before submitting.
• No password — Favoright uses email codes only; there is nothing to reset except requesting a new code.

1. After signing in, look at the header platform switcher when more than one provider is registered.
2. Apple Music is always available. Spotify appears only when enabled for your deployment.
3. Select the provider you want to work with, then follow its Connect prompt when library or playback requires authorization.
4. Complete authorization at the provider and return to Favoright.
5. Switching the selected provider changes which library, favorites, playlists, and playback context you see. Both connections can remain authorized when available.

Home

Returns you to recent favorites and playlists for the currently selected music provider.

Favorites

• Switch among songs, albums, and artists for the selected provider.
• Search and sort items already loaded in the view.
• Favorite songs where the provider supports it. Apple Music can add favorites here; removing them has to be done in the Apple Music app.
• Play songs and add tracks to playlists from song actions.
• Semantic search requires a Favoright account plus a favorite-song sync. Only favorite song metadata is cached for this feature — sync from Favorites when prompted.

Library

• Browse library songs, albums, and artists for the connected provider.
• Search according to provider capability, paginate through results, play songs, and add songs to playlists.

Lists

• Provider playlists — open a playlist, view tracks, and create or edit playlists where supported.
• MCP drafts — separate tab for assistant-generated drafts. Open a draft, review title, description, and tracks, edit if needed, connect music if required, then explicitly create the approved playlist. MCP never writes directly to your music account.

Player and Settings

• The persistent player at the bottom controls playback for the active provider. Some providers require an active connection or subscription for playback.
• Settings shows your account, connected MCP apps, and personal access tokens.
• Revoke MCP access under Connected apps. Create or rotate personal access tokens only when OAuth is unavailable.

http://localhost:3000/mcp

Connect with Codex

Run these commands in your terminal. Codex discovers Favoright metadata, registers a public PKCE client, opens the browser for email login and consent, then stores credentials locally.

codex mcp add favoright -- http://localhost:3000/mcp
codex mcp login favoright

What happens during OAuth

1. The client fetches Favoright protected-resource and authorization-server metadata, then registers a public PKCE client.
2. Your browser opens Favoright. Sign in with email if you are not already signed in.
3. The consent screen shows the MCP client name and requested scopes.
4. After you approve, the browser returns an authorization code to the local MCP client.
5. The client exchanges the code, stores access and refresh tokens, and can call exposed tools.

Other OAuth-capable MCP clients

• Add a remote Streamable HTTP MCP server in your client.
• Enter the MCP endpoint URL shown above.
• Choose browser or OAuth authentication when the client asks.
• Complete the same email login and consent flow in your browser.
• Clients must support remote Streamable HTTP and OAuth 2.1 — Favoright does not verify vendor-specific menu paths here.

Scopes and tools

First successful MCP workflow

1. Sign in to Favoright and connect your music provider.
2. Sync favorite songs in Favorites if you want semantic search tools to work well.
3. Connect your MCP client with OAuth using the endpoint above.
4. Ask the assistant to find music and create a playlist draft.
5. Open the returned approval URL in your own browser, review or edit the draft, and explicitly create the playlist in Favoright.

• Assistants with drafts:write can assemble playlist drafts through MCP tools.
• Each draft write returns an approval URL for you to open personally.
• Review title, description, and tracks in Lists → Drafts or from the approval link.
• Connect the target music provider in Favoright if the draft requires it.
• Press create explicitly when you are ready. MCP does not create provider playlists directly.

• Connected apps lists OAuth MCP clients, their scopes, and last-used times.
• Revoke any client you no longer trust. The next MCP request returns unauthorized and the client should prompt you to sign in again.
• Personal access tokens are a secondary developer fallback for headless CI or clients without OAuth.

Email login and Turnstile

• Request a fresh code if the previous one expired.
• Verify the email address and complete Turnstile before each submit.
• If MCP authorization sent you to login, finish sign-in to return to consent.

Music provider and favorites

• Connect the provider shown in the header before expecting library or playback features.
• Semantic favorite search needs a completed favorite-song sync for the selected platform.
• Switch providers in the header when content looks empty for the wrong service.

MCP client compatibility

• The client must support remote Streamable HTTP and OAuth 2.1.
• Clients without those capabilities need the personal access token fallback instead of OAuth.

Connection refused after consent

• This usually means the local MCP callback server closed or a stale authorization tab was reused.
• Keep the MCP client open, start login again, and approve promptly when the browser opens.
• On Favoright’s Finish MCP sign-in page, try Continue sign-in or the alternate localhost link if one host fails.
• Close old OAuth tabs before retrying.

Revoked or expired MCP access

• Run the client login flow again (for Codex: codex mcp login favoright).
• Remove stale grants in Settings → Connected apps if you need a clean reconnect.