Local Music Collection Mcp

Created By
gorumsa year ago
A powerful Model Context Protocol (MCP) server that provides intelligent access to your local music collection through advanced metadata management, album type classification, and comprehensive analytics.
Overview

What is Local Music Collection MCP?

Local Music Collection MCP is a powerful Model Context Protocol (MCP) server designed to provide intelligent access to your local music collection through advanced metadata management, album type classification, and comprehensive analytics.

How to use Local Music Collection MCP?

To use the Local Music Collection MCP, you can either perform an automated setup using a single command or manually install it by setting up dependencies and running the server. The automated setup is recommended for ease of use.

Key features of Local Music Collection MCP?

  • Smart Music Discovery: Intelligent scanning with 8-type album classification (Album, EP, Live, Demo, Compilation, Single, Instrumental, Split)
  • Advanced Analytics: Collection maturity assessment, health scoring, and personalized recommendations
  • Flexible Organization: Support for multiple folder structures with automated migration and compliance scoring
  • High Performance: Optimized scanning (20-30% faster), batch operations, and intelligent caching
  • AI Integration: Works seamlessly with Claude Desktop and other MCP clients
  • Automated Setup: One-command installation with configuration generation

Use cases of Local Music Collection MCP?

  1. Organizing and managing large local music collections.
  2. Analyzing music collections for insights and recommendations.
  3. Integrating with AI tools for enhanced music discovery and management.

FAQ from Local Music Collection MCP?

  • Can I use Local Music Collection MCP with any music format?

Yes! It supports various music formats as long as they are organized in the specified directory structure.

  • Is there a graphical user interface?

Currently, it operates as a server and is designed for integration with clients like Claude Desktop.

  • How do I troubleshoot issues?

You can run health checks and validate your music structure using provided scripts.

Server Config

{
  "mcpServers": {
    "music-collection": {
      "command": "python",
      "args": [
        "/path/to/music-mcp-server/main.py"
      ],
      "env": {
        "MUSIC_ROOT_PATH": "/path/to/your/music",
        "CACHE_DURATION_DAYS": "30",
        "LOG_LEVEL": "INFO"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
gorums
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

4 hours ago
Gpt Scrambler

a day ago