Nuclear

Separate the player itself from streaming, metadata, and other content sources through plugins

Nuclear includes artist, album, and track search, queue management, favorites, playlists, shuffle, repeat, and other expected playback features. Its newer architecture moves major functionality toward a plugin-driven model: plugins can provide streaming sources, metadata, playlists, dashboard content, and more. Users can install them from the built-in plugin store, while developers can build custom integrations with @nuclearplayer/plugin-sdk. This allows the core player to remain stable while content and data providers change independently.

Sources: [1][2]

Expose playback controls through MCP so an AI agent can operate the player

The settings include a local MCP server that can be connected to Claude Code, Codex CLI, OpenCode, Claude Desktop, Cursor, Windsurf, and other MCP clients. That makes it possible to control playback from an agent conversation or let another tool use Nuclear as part of a wider workflow. The MCP surface runs locally, effectively adding an agent-facing control layer to a conventional desktop music player.

Sources: [1][2]

For users who want a desktop music experience they can extend without being tied to one playback provider

Nuclear fits people who want an ad-free desktop player and prefer a single interface that can work with different metadata and streaming sources instead of a service-specific application. It is especially interesting to developers who want to create their own provider plugins or connect music playback to an AI agent through MCP. Because the main application is built with Tauri and React, it is a local cross-platform application rather than a hosted music service.

Sources: [1]

What you can play, and under what terms, depends on the selected source and plugin

Nuclear does not itself own a music catalog. Search results, playback availability, quality, regional restrictions, and reliability depend on whichever streaming and metadata plugins are enabled. Plugins that connect to external services remain subject to those services' terms, APIs, and applicable copyright rules. Installing a plugin also means running code outside the core project, so its origin and behavior should be reviewed separately.

The core project is licensed under AGPL-3.0, so redistribution or network use of modified versions can carry source-availability obligations. Enabling the MCP server also creates a control surface that other configured tools can use, so the connected clients and exposure scope should be treated as part of the deployment configuration.

Sources: [1][3]