Get SLIMA_API_TOKEN

Local stdio Slima MCP needs an API token — two paths.

Path 1: CLI auth flow (recommended)

Run:

npx slima-mcp@0 auth

What happens:

1. Terminal says "Opening browser…"
2. Default browser opens Slima sign-in
3. Sign in (or if already, see authorize page)
4. Click "Authorize"
5. Redirect to localhost, browser closes
6. Token saved to ~/.slima/credentials.json (chmod 600)

Every slima-mcp client subsequently auto-reads this token.

Path 2: manual

If the CLI auth flow can't open a browser (server env, etc.):

1. Browser to slima.ai/account/api-tokens
2. "+ Create new token"
3. Name (e.g. "Claude Desktop", "My Mac")
4. "Create"
5. Copy the displayed token (shown once!)
6. Set the token in env or config:

# bash / zsh
export SLIMA_API_TOKEN="slima_..."

# or in config
echo '{"slima":{"command":"npx","args":["-y","slima-mcp@0"],"env":{"SLIMA_API_TOKEN":"slima_..."}}}'

Differences

	CLI auth	Manual
Where stored	~/.slima/credentials.json (auto)	env var / config (you)
Security	chmod 600, automatic	depends how you store
Best for	Most people	Automation / CI / multi-account

Can one token serve multiple clients?

Yes — same token across Claude Desktop + Cursor + Gemini works.

But one token per client is recommended — revoking one doesn't affect others.

See: Manage authorized apps

Related

• slima-mcp CLI commands
• Manage authorized apps
• Connect Claude Desktop