Migrate from global install to `npx`

Older docs may say npm install -g slima-mcp — that approach is no longer recommended. The new pattern: write npx straight into config, don't install globally.

Slima Authorized Apps: clients still appear here after migrating from npm install -g to npx -y slima-mcp@0

Why the change

Global install	Dynamic npx
Manual `npm update` needed	Auto-takes latest 0.x each run
Confusing across multiple node versions	Doesn't matter
Each user installs separately	First run downloads, cached
Version management overhead	`@0` handles it

Migration

1 · Remove the global install

npm uninstall -g slima-mcp

Verify:

which slima-mcp
# should be: not found

2 · Update client config to npx

Change from:

"slima": {
  "command": "slima-mcp"
}

to:

"slima": {
  "command": "npx",
  "args": ["-y", "slima-mcp@0"]
}

3 · Restart the client

Full Quit Claude Desktop / Cursor, reopen.

4 · Verify

@slima list books

Should work as before.

Token is unaffected

~/.slima/credentials.json is standalone — has nothing to do with the npm install. So migration doesn't affect your token.

No more manual upgrades

The new pattern npx -y slima-mcp@0 auto-checks for the latest 0.x on every run — you don't need to do anything to upgrade.

(Only when 1.0 ships will you manually flip @0 to @1 — see Version pinning.)