Nuclear Music Player
Search, play, and manage free music manually or through an AI assistant.
The MCP server must be explicitly enabled in settings and is configured on a loopback address, providing reasonable default scoping and user confirmation. The README claims no ads or tracking, but supplies no privacy statement, sensitive-data lifecycle, telemetry implementation, or inventory of streaming and plugin data flows. Frozen-lockfile installation and CI offer limited supply-chain control, while dependency auditing, vulnerability response, and plugin review are not evidenced. Playback, queues, favorites, playlists, and plugins can create external or persistent effects, yet per-action confirmation, effect previews, and recovery are undocumented. Author, repository, community channels, and licensing provide attribution; the unverified publisher identity is treated as unknown and earns no additional trust.
The README, package manifest, and CI are broadly consistent about pnpm, Turborepo, testing, building, and the principal technology stack. Platform packages, explicit tool versions, prerequisites, and frozen-lockfile installation make the dependency path reasonably clear, but availability, fallback behavior, and compatibility guarantees for external music sources and plugins are absent. Test helpers model HTTP errors, hanging and aborted requests, and corrupt responses with a concrete error string, but comprehensive user-facing or MCP-facing error semantics, retry policy, and recovery guidance are not shown.
The documentation identifies desktop listeners, plugin developers, and users controlling the player through Claude Code, Codex CLI, OpenCode, and similar clients, while covering all three major desktop operating systems. The MCP interface is called discoverable, but no tool inventory, parameter schemas, read-versus-write boundaries, authorization scopes, or precise activation rules are supplied, limiting capability-boundary and trigger-precision scores. Distribution formats and development prerequisites for Windows, macOS, and Linux are documented thoroughly, fully supporting environment fit.
The README has a clear structure spanning screenshots, downloads, features, plugins, MCP, development, community, and licensing. Binary installation formats, development prerequisites, startup steps, and validation commands are thorough. Nuclear branding, package scopes, and commands appear consistent, though the root package is version 0.0.10 and no stability policy is given. Several useful MCP client configurations are included, but there is no FAQ. Known limitations are not documented. The AGPL-3.0-only metadata, README notice, and full license text agree, justifying full license credit. A What's New screenshot and release-preparation command are only indirect versioning evidence; no changelog or release policy is supplied. Community channels exist, but ownership, support commitments, and security-reporting responsibility are unclear.
Screenshots and feature descriptions show usable search, playback, queue, playlist, theme, plugin, preference, and log interfaces, while MCP control adds an agent-oriented access path. Multi-source discovery, extensibility, and desktop integration provide reasonable marginal value over a basic player. The application is free and open source, reducing direct cost, but third-party streaming sources, plugins, and local desktop operation introduce unquantified legal, availability, security, and maintenance costs, preventing a thorough cost-benefit score.
Some development claims trace to the package manifest, CI workflow, and test helpers, and interface or platform claims have screenshot support. Core MCP tool behavior, the no-tracking claim, plugin permissions, and music-source mechanics lack corresponding implementation evidence in the supplied files. The sources cross-corroborate the stack, commands, license, and test workflow to a useful but incomplete degree. Promotional feature claims are not systematically separated from verified facts, and there is no claim-by-claim evidence map or explicit inference labeling.
- Inspect the actual MCP tool inventory and read/write permissions before enabling it; the supplied material does not establish whether an agent can modify or delete queues, favorites, playlists, or plugin state.
- The no-tracking claim lacks a privacy policy or implementation evidence; independently inspect telemetry, logs, search queries, streaming requests, and plugin communications.
- The built-in plugin store and third-party music sources expand supply-chain and data-exposure surfaces, but plugin review, sandboxing, signing, and revocation controls are not shown.
- No undo, backup, or recovery workflow is documented; use recoverable data or an isolated profile before allowing persistent agent actions.
- The dev:remote command binds to 0.0.0.0; use it only on a trusted network and verify authentication and access controls.
What does this agent do, and when should you use it?
Nuclear is an open-source desktop music player without ads or tracking, available for Windows, macOS, and Linux. It searches for songs, artists, and albums, streams music through plugin-provided sources, and manages queues, favorites, and playlists. The main application is built with Tauri using Rust, React, and TypeScript, inside a pnpm monorepo managed by Turborepo. Its built-in plugin store supports extensions that provide streaming sources, metadata, playlists, dashboard content, and other functionality, while @nuclearplayer/plugin-sdk supports custom plugin development. An optional local HTTP MCP server lets MCP clients such as Codex CLI, Claude Code, Claude Desktop, Cursor, Windsurf, and OpenCode drive the player. The application and playback state remain on the user's desktop, with the documented MCP endpoint exposed locally at 127.0.0.1:8800/mcp.
A user searches for a track, artist, or album in the desktop application, and Nuclear uses installed plugins to supply streaming sources and metadata for the results. Selected tracks enter a playback queue that supports shuffle, repeat, and drag-and-drop reordering. Users can save favorite tracks, albums, and artists, as well as create, import, and export playlists. Artist pages present biographies, discographies, and similar artists; album pages provide track listings. Extensions are discovered through the built-in plugin store or developed with @nuclearplayer/plugin-sdk. After the MCP server is enabled under Settings → Integrations, compatible clients discover and invoke player controls over http://127.0.0.1:8800/mcp, changing playback, queue, favorite, or playlist state in the local Nuclear application.
- A listener who wants an ad-free, tracking-free desktop player for finding and streaming free music on Windows, macOS, or Linux.
- A music collector who needs favorites, editable queues, playlist creation, import, and export in one application.
- A developer who wants Codex CLI or Claude Code to control music playback through a local MCP connection.
- A plugin author who wants to add a streaming source, metadata provider, playlist integration, or dashboard content using @nuclearplayer/plugin-sdk.
- A developer testing the remote-control UI from another device on the same LAN by running pnpm dev:remote.
What are this agent's strengths and limitations?
- One desktop application supports Windows, macOS, and Linux, with several native package formats for each ecosystem.
- The documented local HTTP MCP interface includes ready-to-copy configurations for Codex CLI, Claude Code, OpenCode, Claude Desktop, Cursor, and Windsurf.
- Plugins can replace or extend streaming sources, metadata, playlists, and dashboard content, backed by an integrated store and @nuclearplayer/plugin-sdk.
- The player combines search, queue controls, favorites, playlist import and export, themes, keyboard shortcuts, and localization.
- The project explicitly offers an ad-free, tracking-free experience and is licensed under AGPL-3.0.
- Search and playback depend on network access and on the availability of streaming-source plugins; a failing source may disrupt playback.
- Building from source requires a comparatively broad toolchain: Node.js, pnpm, stable Rust, and platform-specific Tauri dependencies.
- MCP control requires a running desktop application and manual enablement; the material documents only a loopback endpoint and provides no authentication or multi-user deployment guidance.
- AGPL-3.0 can introduce compliance obligations when modifying, distributing, or operating adapted versions, so adopters should assess its terms.
- The supplied material does not identify default streaming providers, quantify catalog coverage, or promise source availability.
How do you install or deploy this agent?
End users can download a release package from the repository's Releases page. Available formats are .exe and .msi for Windows, .dmg for Apple Silicon and Intel Macs, and .AppImage, .deb, .rpm, or .flatpak for Linux. Source development requires Node.js 22 or newer, pnpm 9 or newer, stable Rust, and the platform-specific Tauri prerequisites. Run:
git clone https://github.com/nukeop/nuclear.git
cd nuclear
pnpm install
pnpm devThe documented setup does not require API credentials. A network connection is needed to find and stream online music.
How do you use this agent?
Launch Nuclear, search for a song or artist, open artist or album pages, add tracks to the queue, and create playlists as needed. For AI control, enable the MCP server under Settings → Integrations. Connect Codex CLI with:
codex mcp add nuclear --url http://127.0.0.1:8800/mcpConnect Claude Code with:
claude mcp add nuclear --transport http http://127.0.0.1:8800/mcpOpenCode can define a nuclear MCP entry with type remote and the same URL. Claude Desktop, Cursor, and Windsurf can add that URL under mcpServers. The MCP interface is described as discoverable, and the repository also supplies an optional Nuclear MCP Skill for additional client context.