Wires this session up to the user's own Cognitum Music account (music.cognitum.one) via the cogmusic MCP bridge. This is a one-time, per-machine/per-project setup — run it before any other music-* skill if mcp__cogmusic__* tools aren't already loaded.
mcp__cogmusic__* tools are visible yet.claude mcp get cogmusic reports the server missing, disconnected, or unhealthy.```bash
claude mcp get cogmusic
```
If it reports ✔ Connected, you're already set up — stop here.
https://music.cognitum.one/mcpcogmcp_ and is shown exactly onceclaude mcp add, which stores it in local config, not in conversation history):```bash
claude mcp add cogmusic --env COGMUSICTOKEN=cogmcp... -- npx -y cogmusic@latest
```
Pin to cogmusic@0.1.1 or later — earlier 0.1.0 has no fetch timeout and failscreate_production calls that run past Node's ~5-minute default (see
ADR-0001).
```bash
claude mcp get cogmusic
```
Expect ✔ Connected. If it shows CONNECTION_CLOSED or a 404, the cogmusic npm package version pinned in the command may be stale or unpublished — check npm view cogmusic version and retry with an explicit version.
```bash
claude mcp remove cogmusic -s local
claude mcp add cogmusic --env COGMUSICTOKEN=cogmcp... -- npx -y cogmusic@latest
```
mcp__cogmusic__* tools (list_productions, get_production, create_production, separate_stems, extract_midi, master) become available — proceed to music-generate or music-list.music.cognitum.one/mcp — this plugin has no way to mint or revoke one programmatically, and should never attempt to guess, cache elsewhere, or transmit it anywhere other than the local claude mcp add registration.mcp__cogmusic__* tools still aren't listed after a successful claude mcp get cogmusic, tell the user to start a fresh session.