Upnext

io.github.tothienbao6a0Published by GitHub account tothienbao6a0v0.3.1Updated Oct 24, 2026

One audio queue across Spotify, the browser, local files and whatever is already playing.

VerifiedSTDIODesktop onlyProductivity & Workflow Media & Design

Server details

Identifier: io.github.tothienbao6a0/upnext
Transport: STDIO
Runtime: Desktop only
Trust: Verified
Published: Sep 16, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified the GitHub account tothienbao6a0 for this listing. That does not show the account is the product's maker.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/io.github.tothienbao6a0%2Fupnext.svg)](https://sourceweft.com/mcp/io.github.tothienbao6a0%2Fupnext?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Local MCP server that gives an assistant one audio queue spanning Spotify, browser tabs, local files and whatever is already playing on the machine.

What you can do: Inspect playback: see what is playing in the queue and elsewhere on the machine, and list the queue with entry ids
Add to the queue: enqueue a link, file path, Spotify URI or plain description, or adopt what is already playing
Control transport: play, pause, next, and seek to a position where the source allows it
Edit the queue: move and remove entries by id, and search the sources that support searching
Check setup: report which backends are wired and what they can do
When to use it: Useful when you want an assistant to answer what is playing and to queue music or audio without interrupting the current track, across mixed sources on a desktop machine. Best suited to Mac-style setups where Spotify, a browser and a local music folder are in play.
Requirements: Runs locally over stdio, typically launched with npx from the upnext-mcp npm package, so Node.js is needed. A music library path can be passed as a command-line argument, and a Spotify Web token can be supplied through the SPOTIFY_TOKEN environment variable so descriptions can be resolved to titles. Desktop only; no web executable.

Before you install

The optional SPOTIFY_TOKEN environment variable is a credential and should be kept out of shared configs. The server changes playback and queue state on the machine, including pausing, skipping, reordering and removing entries. Descriptions cannot be resolved without a searcher, so requests may silently fail to find a title unless a library or token is configured.

Installation

In SourceWeft

Open Upnext in the dashboard and add it to a workspace.
Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

upnext-mcp

[npm] [license]

An MCP server for your machine's audio. One queue across Spotify, the browser, local files, and whatever is already playing.

json

{  "mcpServers": {    "upnext": {      "command": "npx",      "args": ["-y", "upnext-mcp", "--library", "/Users/me/Music"]    }  }}

{  "mcpServers": {    "upnext": {      "command": "npx",      "args": ["-y", "upnext-mcp", "--library", "/Users/me/Music"]    }  }}

Drop that in Claude Desktop, Cursor, Windsurf, or anything else that speaks MCP.

What it lets an agent do

you:  what am I listening to?      → ❚❚ Acquired — Jensen Huang (Google Chrome)
you:  let that finish, then play Bad Habit      → adopted "Acquired — Jensen Huang" as q_0001        up next:          q_0001  Acquired — Jensen Huang          q_0002  Bad Habit — Steve Lacy

you:  what am I listening to?      → ❚❚ Acquired — Jensen Huang (Google Chrome)
you:  let that finish, then play Bad Habit      → adopted "Acquired — Jensen Huang" as q_0001        up next:          q_0001  Acquired — Jensen Huang          q_0002  Bad Habit — Steve Lacy

The first line reads a browser tab — no extension. The second puts it in the queue as a real entry, so the agent adds to what someone is doing rather than cutting across it.

Tools

tool
`media_now`	what's playing, in the queue and elsewhere on the machine
`media_queue`	the queue, with the id of each entry
`media_enqueue`	add a link, file path, Spotify URI, or a plain description
`media_play` · `media_pause` · `media_next`	transport
`media_seek`	jump to a position — says so plainly if the source can't
`media_move` · `media_remove`	reorder and drop, by id
`media_search`	search the sources that can search
`media_adopt_current`	put what's already playing into the queue
`media_setup`	what's wired here, and what it can do

Every mutation is addressed by id, and every response includes the queue with ids in it. That's deliberate: a model working from positions races anything else touching the queue, and by the time its call lands, position 2 is a different song.

It tells the model the truth

Two places where this behaves differently from most tool servers, both for the same reason — a model that gets a silent no-op will confidently tell the user it worked.

media_seek on a source that can't seek returns a sentence, not an error:

the current source (spotify-desktop) cannot seek. Nothing changed.

media_search with nothing wired to search explains itself:

nothing found for "bad habit". playing through: spotify-desktop, nowplaying, local titles will NOT resolve: nothing wired here can search…

Titles need a searcher

A link says exactly what to play. A description has to be looked up, and not every backend can. The Spotify desktop app plays a URI you hand it but cannot search a catalogue — so on a plain Mac setup, media_enqueue with "bad habit" has nothing to resolve against.

Give it one of these:

jsonc

// index a music folder"args": ["-y", "upnext-mcp", "--library", "/Users/me/Music"]
// or a Spotify Web token, via the environment"env": { "SPOTIFY_TOKEN": "..." }

// index a music folder"args": ["-y", "upnext-mcp", "--library", "/Users/me/Music"]
// or a Spotify Web token, via the environment"env": { "SPOTIFY_TOKEN": "..." }

media_setup will tell you which you have.

Embedding it instead

If your product already has a queue, expose that one rather than starting a second that competes with it:

import { createServer } from 'upnext-mcp';import { serveStdio } from '@modelcontextprotocol/server/stdio';
serveStdio(() => createServer(myExistingRuntime));

import { createServer } from 'upnext-mcp';import { serveStdio } from '@modelcontextprotocol/server/stdio';
serveStdio(() => createServer(myExistingRuntime));

This package is a transport, and nothing more — ordering, capability negotiation, resolution and reconciliation all happen in upnext-core. It lives apart because a transport is an opinion, and nobody importing the runtime should inherit this one.

Full docs: https://github.com/tothienbao6a0/upnext · Apache-2.0

Source: packages/mcp/README.md at commit 93a48da

Tools

SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

v0.3.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
License10 pts