Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SONORA_MODENoEither `read-only` or `playback`. In `playback` mode the write tools (`play`, `pause`) are registered.read-only
XDG_CONFIG_HOMENoBase directory for `sonora-mcp/tokens.json` where OAuth tokens are stored.~/.config
SONORA_LOG_LEVELNoOne of `error`, `warn`, `info`, `debug`. Logs go to stderr, redacted.info
SPOTIFY_CLIENT_IDYesClient ID of your Spotify app. Required.
SPOTIFY_REDIRECT_PORTNoLoopback callback port (register the matching redirect URI at http://127.0.0.1:<port>/callback).8888

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Features and capabilities supported by this server

Protocol revision2025-11-25

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
searchB

Search the Spotify catalog for tracks, albums, artists or playlists. Returns names, URIs and links.

now_playingA

Get what is currently playing on the user's Spotify account (track or episode, progress and device).

list_devicesA

List the user's available Spotify Connect devices (phone, computer, speaker). Returns the id to pass as device_id to play or transfer_playback. A device only appears while its Spotify app is open.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 3 tools

Disambiguation5/5

Each tool has a clearly distinct target: catalog search, current playback state, and device enumeration. There is no plausible confusion between them, and their scopes (catalog vs. playback vs. devices) do not overlap.

Naming Consistency3/5

The set mixes conventions: `search` is a bare verb, `list_devices` is verb_noun, and `now_playing` is a noun phrase describing state. It is still readable, but there is no predictable pattern an agent could generalize from.

Tool Count3/5

Three tools is thin for a Spotify integration whose apparent purpose is playback control and discovery. The surface feels like a partial slice rather than a well-scoped toolset.

Completeness2/5

`list_devices` explicitly tells the agent to pass a device_id to `play` or `transfer_playback`, but neither tool exists in this server, creating a hard dead end. There is also no pause/skip, queue, or playlist management, so the playback lifecycle is largely uncovered.

Maintenance

ActivityMaintained
ResponsivenessOutdated data