Nuclear MCP Server

Content

Nuclear MCP Server is the built-in Model Context Protocol server in Nuclear Music Player. Once enabled in the desktop app, it exposes a local Streamable HTTP endpoint that lets Claude inspect available music-player methods, understand their parameters, describe return types, and execute approved player actions.

Use it when Claude should help drive a local Nuclear session, inspect the queue, control playback, add tracks, work with favorites or playlists, browse dashboard data, or route through Nuclear's music providers without giving the assistant a general-purpose browser or shell.

Source Review

• https://github.com/nukeop/nuclear
• https://raw.githubusercontent.com/nukeop/nuclear/master/packages/docs/integrations/mcp-server.md
• https://raw.githubusercontent.com/nukeop/nuclear/master/README.md
• https://raw.githubusercontent.com/nukeop/nuclear/master/LICENSE
• https://raw.githubusercontent.com/nukeop/nuclear/master/package.json
• https://raw.githubusercontent.com/nukeop/nuclear/master/packages/docs/development/mcp-architecture.md
• https://raw.githubusercontent.com/nukeop/nuclear/master/packages/player/src-tauri/src/mcp/mod.rs
• https://raw.githubusercontent.com/nukeop/nuclear/master/packages/player/src-tauri/src/mcp/tools.rs
• https://raw.githubusercontent.com/nukeop/nuclear/master/packages/player/src-tauri/src/mcp/metadata.rs
• https://raw.githubusercontent.com/nukeop/nuclear/master/packages/player/src/services/mcp/mcpHandler.ts

These sources were reviewed on 2026-06-06. Prefer the live repository, MCP integration guide, README, license, package metadata, MCP architecture guide, Rust server implementation, tool definitions, metadata source, and settings handler for current setup and behavior details.

Features

• Enable a built-in local Streamable HTTP MCP server from Nuclear settings.
• Discover API domains with list_methods.
• Inspect method names, parameters, and return types with method_details.
• Inspect complex data shapes such as tracks, queues, queue items, and playlists with describe_type.
• Execute player API methods through the call tool.
• Work across Queue, Playback, Metadata, Favorites, Playlists, Dashboard, and Providers domains.
• Bind to localhost on port 8800, or the next available port through 8809.

Installation

Install Nuclear Music Player, open Settings > Integrations, and enable the MCP server. Nuclear shows the actual local server URL after startup. The default host and path are:

127.0.0.1:8800/mcp

Add it to Claude Code with Streamable HTTP transport:

claude mcp add nuclear --transport http <copy-url-from-nuclear-settings>

For MCP clients that accept URL-based server configuration:

{
  "mcpServers": {
    "nuclear": {
      "url": "<copy the MCP Server URL from Nuclear Settings>"
    }
  }
}

If Nuclear chooses a different port, replace 8800 with the port shown in the MCP Server URL field.

Use Cases

• Ask Claude what playback, queue, playlist, favorite, dashboard, metadata, or provider methods are available before taking action.
• Build a listening queue from a prompt, then review the proposed tracks before adding them.
• Create or update playlists from approved artists, albums, or tracks.
• Inspect favorites or queue state while planning a listening session.
• Control playback in a local desktop session without giving the assistant shell access.
• Explore Nuclear provider behavior with bounded, user-confirmed actions.

Safety and Privacy

Nuclear MCP Server is local, but it still lets an agent change the state of a running desktop music player. Require confirmation before modifying playlists, favorites, queue entries, provider settings, or any action that starts playback.

Treat searches, queue contents, listening history, favorites, playlists, provider choices, metadata, local settings, and MCP transcripts as personal data. Keep the server bound to localhost, and do not expose the local MCP endpoint over a network unless you have reviewed the access controls.

Duplicate Check

No nukeop/nuclear, Nuclear Music Player MCP, Nuclear MCP Server, or matching source URL entry was found in content/mcp or README.md. Existing browser, media conversion, and search MCP entries do not cover Nuclear's built-in music player control server.