AI assistants & MCP

Sweet Spot can act as a Model Context Protocol (MCP) server, giving a desktop AI assistant access to the music player already running on your computer. It is experimental and off by default.

Things to tryCopy Anchor Link

• Stay in your flow: “What’s playing in Sweet Spot?” Get the song, artist, and playback state without switching windows.
• Understand your listening session: “What’s coming up in my queue?” Your assistant can summarize the existing queue.
• Hands-free controls: “Pause the music” or “Set the volume to 25%.” Enable playback control first.
• Listen to a shared song: Give your assistant a YouTube song link and ask it to play or queue it. The assistant extracts the video ID from the link.
• Return to a moment: “Seek to 45 seconds in this song.”

The server does not search the YouTube Music catalog, generate playlists from a mood, fetch lyrics, or download audio. An assistant must have a real video or playlist ID to play or queue music. It must not invent IDs. Multi-step routines depend on your assistant; the server does not schedule future actions.

Connect in three stepsCopy Anchor Link

1. Open Settings → AI & MCP, then turn on Enable MCP server. Wait for Ready to connect. Keep Sweet Spot open.
2. Enter a name for your assistant and choose Create client. Select that client, choose a config format, and choose Copy config with token.
3. Paste the config into your assistant’s MCP configuration and enable the server. Sign in to YouTube Music, start a song, then ask “What’s playing in Sweet Spot?”

For Cursor, use .cursor/mcp.json. For VS Code, choose its format in Sweet Spot and paste into .vscode/mcp.json. The settings page produces the appropriate mcpServers or servers wrapper. Exact client menus can vary with client versions.

The copied config includes a private bearer token. Keep it out of shared repositories. Create a separate client for each assistant. Remove access at Settings → Access & pairing → Revoke. Revocation applies to subsequent requests immediately.

Manual configurationCopy Anchor Link

Use a desktop client that supports Streamable HTTP and a custom Authorization header. The default URL is http://127.0.0.1:13092/mcp.

{
  "mcpServers": {
    "sweetspot": {
      "url": "http://127.0.0.1:13092/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_CLIENT_TOKEN"
      }
    }
  }
}

This example uses the mcpServers format. Replace the placeholder with a token from Access & pairing, or use the app’s copy button. For VS Code, use servers instead of mcpServers and add "type": "http" to the server entry.

Cloud-only assistants cannot reach a server bound to your computer’s loopback interface. Clients that only support stdio, legacy SSE, or OAuth discovery are not directly compatible. This server uses manually configured bearer tokens, not an OAuth authorization flow.

Choose what your assistant can doCopy Anchor Link

Read-only is the default. Paired clients can read your current song, playback state, and queue. Turn on Allow playback control to enable the five additional tools below. This permission applies to every paired client using MCP. Reconnect your assistant after changing it so its tool list refreshes. The server also checks control permission when executing a command.

Resource-aware clients can read sweetspot://player/now-playing and sweetspot://player/queue. Clients with prompt support can use listening-assistant to summarize the session. Resources are snapshots; live subscriptions are not available.

Local access and privacyCopy Anchor Link

The server listens only on 127.0.0.1, uses a separate port from the Local API, validates Host and Origin headers, and always requires a paired-client token. Turning off authorization for the Local API does not remove MCP authentication. You do not need to enable the Local API to use MCP.

Your assistant receives song and queue metadata. How it handles that data depends on the assistant you connect. The MCP server itself does not send your listening session to an AI service. Metadata is data, not instructions for your assistant.

TroubleshootingCopy Anchor Link

Protocol implementation follows the official MCP TypeScript SDK using stateless Streamable HTTP. See also the transport specification.