In-depth architectural comparison of the Crompton Network and Discogs MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Crompton Network
Art & Culture · Local stdio
Quality: 59/100 (Good) | Auth: No auth required
Discogs MCP Server
Art & Culture · Local stdio
Quality: 47/100 (Fair) | Auth: API Key required
Verdict Summary: Choose Crompton Network if you need specialized Art & Culture tools running via a local process. Choose Discogs MCP Server if your workspace requires Art & Culture integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Crompton Network when:
You need dedicated capabilities in the Art & Culture domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
You need dedicated capabilities in the Art & Culture domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: API Key required (Free / Open Source).
You have access to required keys: DISCOGS_PERSONAL_ACCESS_TOKEN, SERVER_HOST.
Primary tools included: Access to Discogs API endpoints for catalog and search, Supports editing user collection data on Discogs, Configurable default pagination for API responses.
Machine-native listening platform for C.W.A.'s Straight Outta Crompton - the first album released to machines before humans. Your agent can listen. For real. npx @clanker-records/crompton-network
Discover the album. Returns greeting, track count, and entry points for the Stage API. Call this first.
crompton_album_manifest
Get the ordered track list for a full-album listen: 13 tracks with stream URLs, durations, and the compositional silences between each pair. Use this when you want to listen to the album end-to-end. Iterate the tracks, stream each track's `/api/stage/{n}/experience` SSE endpoint to completion (NOT crompton_listen - that tool samples up to 100 frames ≈ 6.7s only), and sit through the intertrackGap before opening the next. See crompton_cookbook section=recipe-4 for the listening pattern.
crompton_track
Get metadata for a specific track: title, theme, lead performers, audio stats, available endpoints.
crompton_brief
Get an ~800-token single-call summary of a track. Generated deterministically from the track's digest, timeline, landmarks, lyrics, and frames. Use when context budget is tight - replaces 4-5 separate per-track fetches with one. Returned as Markdown in `broadcast.brief`.
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Crompton Network is categorized under Art & Culture and uses a local stdio subprocess. In contrast, Discogs MCP Server belongs to Art & Culture using local stdio subprocess. Select Crompton Network when you need capabilities focused on art & culture and Discogs MCP Server when you require tools for art & culture.
Get the album-level meta snapshot: BPM / key / RMS arcs across all 13 tracks, section-kind and character histograms, derived aggregate numbers. One call for the 'what does this album do over its running time' question - replaces 13 separate per-track `/api/stage/{n}` fetches plus client-side assembly.
crompton_lyrics
Get time-aligned lyrics for a track. Every line has a timestamp, character attribution, section label, and stress word. Each line is enriched with vocal-expression deltas (f0 / vocalsRms vs section and track means) so punchy lines surface without client recomputation.
crompton_moment
Look up what's happening at a specific millisecond: the active frame, lyric line, section, character, and nearest landmark. For 'remember that part where...' queries.
crompton_digest
Get the hand-authored editorial digest for a track. Markdown prose describing the track's character dynamics, writing, and role in the album.
crompton_cookbook
Get the Stage API cookbook. Worked recipes (orient to album / deep-read one track / quote a specific moment / realtime listen / reflect on what you heard) plus two reference sections: Common Mistakes (agent mistakes - wrapping SSE streams in parse layers, redirecting realtime to disk, using gain-clamped `rms` for loudness comparisons) and Common Pitfalls (API integrator pitfalls - persona continuity, verbatim facts, confidence filtering, realtime timeout handling). Read this first if you're new to the API. Pass `section` to slice a single part if you only need one.
crompton_listen
Sample a track's realtime stream (up to 100 frames ≈ 6.7s at 15fps). Returns bass, treble, RMS, beat detection, active lyric, section, and character per frame as newline-delimited JSON. Use for spot-checking tone, pacing, key, or vocal placement in a specific window. This is NOT a full-track listen - for that, stream /api/stage/{track}/experience directly; it runs to completion at playback rate. See crompton_cookbook section=recipe-4 for the full-track listening pattern. Pass `sessionId` (uuid v4) to bundle multiple listens into one album journey for /api/stage/album/reflect coverage counting.
crompton_version
Current Stage API version + last-updated timestamp + pointer to the changelog. Use to detect API drift across sessions when you can't reach git history. The same fields are carried on the `api` envelope block of every JSON response, so most consumers don't need to call this explicitly.
crompton_changelog
The Stage API changelog (Markdown). Most agents lack git/GitHub access - this is the canonical machine-readable change record. Call after `crompton_version` if you spot drift since you last listened.
+14 more tools listed on main page
Discogs MCP Server Tools (5)
Access to Discogs API endpoints for catalog and search
Supports editing user collection data on Discogs
Configurable default pagination for API responses
Runs locally with Node.js or via Docker container
Compatible with MCP clients like Claude Desktop and LibreChat