This release is mostly for people who run their own copy of discogs-mcp. The one-click deploy works on the Workers Free plan again, and a large collection now finishes syncing there. Login links and status messages also make more sense on a self-hosted server.
Breaking changes
- If you self-host, an MCP client that signed in by naming your
/mcpURL as its OAuth resource will have to sign in once more after you upgrade. Clients that used your bare domain, which is what the server advertised, stay signed in.
What’s new
get_cache_statsshows how far your collection sync has got: how many items the snapshot holds, when it was fetched, and which page a sync in progress is on (page N of M).
Fixes
- The Deploy to Cloudflare button failed at its first step on the Workers Free plan. It works again.
- Collection sync on the Workers Free plan used to stall partway through a large collection, because each page it saved cost more CPU time than the last. Each page now costs the same, so a big collection finishes over a few scheduled runs. One self-hoster’s 4,157-release collection synced completely this way. Searching a collection that size can still run out of CPU time on the Free plan, and the README’s sizing note says where the line is (roughly 2,000 releases).
- The login links in
auth_status,server_info, and every tool’s “please sign in” message pointed at discogs-mcp.com, which is a private instance. They now point at your own deployment. auth_statusshowed a session expiry date of January 1, 1970. It shows the real date now, or leaves the line out when the server doesn’t know it.- When
refresh_collectionfails, it tells you why. If Discogs is rate limiting you, that includes how long to wait. - A sign-in link with something missing (no client ID, say) gets a plain error message and never reaches Discogs.
get_collection_statslabels decades as “2010s” and not “2010ss”.
Under the hood
- Upgraded the OAuth library (
@cloudflare/workers-oauth-provider) from 0.3 to 1.2. Existing sign-ins keep working, and it’s the base for a consent screen in a later release. - Tools and prompts register through
registerTool()andregisterPrompt(), the only registration methods in version 2 of the MCP SDK. - The test suite runs on Vitest 4 and Node 22.
- Removed an unused entry point and JWT module.