discogs-mcp v3.7.0 — Current MCP protocol, safer destructive tools

The server now speaks the current MCP protocol revision (2026-07-28), tells your client which tools can delete things, and asks self-hosters for one fewer secret. Older MCP clients keep working through the compatibility lane. Breaking changes If you use the manual login flow and your client passed the session as an Mcp-Session-Id header, that header is no longer read. Connect with the ?session_id= query parameter instead, which is what the login page has always handed out. What's new The server speaks MCP 2026-07-28 natively. Clients on that revision connect without an initialize handshake; clients on the 2024 and 2025 revisions still connect the way they did before. Every tool carries the MCP annotations that tell a client what it does: reads are marked read-only, additive writes are marked non-destructive, and only remove_from_collection, remove_from_wantlist, delete_folder, and edit_custom_field are flagged as destructive. A client that confirms destructive actions can now do so…