Skip to main content
Glama
nepomusic

Discogs MCP Server

by nepomusic

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
JWT_SECRETYesAny random string used to sign JWTs for authentication (e.g., generated with `openssl rand -hex 32`).
DEBUG_TOKENNoOptional: A secret token to access the /debug/budget diagnostic endpoint.
DISCOGS_CONSUMER_KEYYesYour Discogs consumer key from your Discogs developer application (created at discogs.com/settings/developers).
DISCOGS_RELAY_ORIGINNoOptional: URL of your relay proxy for Discogs API calls. Leave empty to call Discogs directly.
RELAY_ACCESS_CLIENT_IDNoOptional: Cloudflare Access service token client ID used to authenticate to your relay.
ALLOWED_DISCOGS_USER_IDNoOptional: Numeric Discogs user ID or comma-separated list of IDs to restrict who can authenticate to this instance. Leave empty to allow any Discogs user.
DISCOGS_CONSUMER_SECRETYesYour Discogs consumer secret from your Discogs developer application.
RELAY_ACCESS_CLIENT_SECRETNoOptional: Cloudflare Access service token client secret used to authenticate to your relay.

Instructions

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Capabilities

Server capabilities have not been inspected yet.

Tools

Functions exposed to the LLM to take actions

NameDescription

No tools

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nepomusic/discogs-mcp-nepomusic'

If you have feedback or need assistance with the MCP directory API, please join our Discord server