Discogs MCP Server

Created By
thesimsguya year ago
Overview

what is Discogs MCP Server?

Discogs MCP Server is a server application that interfaces with the Discogs API, enabling users to perform music catalog operations, search functionalities, and more.

how to use Discogs MCP Server?

To use the Discogs MCP Server, you need to have Node.js installed and a personal access token from Discogs. You can run the server locally or via Docker, and configure it to work with the Claude desktop app.

key features of Discogs MCP Server?

  • Integration with the Discogs API for music catalog management.
  • Support for local development and Docker deployment.
  • MCP Inspector for testing and inspecting the server.

use cases of Discogs MCP Server?

  1. Managing personal music collections through the Discogs API.
  2. Searching for music catalog entries efficiently.
  3. Developing applications that require music data from Discogs.

FAQ from Discogs MCP Server?

  • What is required to run the server?

You need Node.js and a Discogs personal access token.

  • Can I run it using Docker?

Yes, the server can be run using Docker for easier setup.

  • Is there support for OAuth?

OAuth support is planned for a future release.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
thesimsguy
Star
0
Language
TypeScript
License
MIT 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)

a day ago