Connect Claude Desktop

Claude Desktop uses stdio (not OAuth) — edit a config file, run npx -y slima-mcp@0.

Steps

1 · Get SLIMA_API_TOKEN

Fastest: npx slima-mcp@0 auth — browser opens, sign in, token stored at ~/.slima/credentials.json.

Or manually: Account → API tokens.

2 · Find Claude Desktop config

macOS:

~/Library/Application Support/Claude/claude_desktop_config.json

Windows:

%APPDATA%\Claude\claude_desktop_config.json

Create the file if missing.

3 · Edit config

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

No plaintext token needed — slima-mcp reads ~/.slima/credentials.json.

4 · Restart Claude Desktop

Full Quit and reopen (not reload).

5 · Verify

New chat, look for a "🔌 slima" icon near the input. Try:

List my Slima books

Multiple MCP servers

If you already have other MCP servers (e.g. filesystem):

{
  "mcpServers": {
    "slima": {
      "command": "npx",
      "args": ["-y", "slima-mcp@0"]
    },
    "filesystem": {
      "command": "npx",
      "args": ["-y", "@modelcontextprotocol/server-filesystem", "/path/to/docs"]
    }
  }
}

Advanced: plaintext token (not recommended)

If you don't want ~/.slima/credentials.json (e.g. multi-account):

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

Writes the token into the config file — ~/.slima/credentials.json with chmod 600 is safer.

Related

• Get SLIMA_API_TOKEN
• slima-mcp CLI
• Troubleshoot can't connect