Authentication

Both surfaces share the same key. The CLI stores it under ~/.dlazy/config.json; the MCP client reads it back from there or from DLAZY_API_KEY.

Get an API Key

Sign in to dLazy and create or copy a key from the dashboard: https://dlazy.com/dashboard/organization/api-key. Keys start with sk-.

CLI

# Browser-based device-code flow — works on remote SSH / containers.
dlazy login
dlazy login --local        # device-code against http://localhost:3000

# Or paste the key directly
dlazy auth set sk-xxxx

# Inspect / reveal
dlazy auth get             # masked: sk-***1234
dlazy auth get --show      # full key

# Clear
dlazy logout

Resolution Order

Every command resolves the key in this order — first hit wins:

1. --api-key <key> flag
2. DLAZY_API_KEY environment variable
3. ~/.dlazy/config.json (set by dlazy login / auth set)
4. Interactive device-code login (TTY only)

DLAZY_BASE_URL (or --base-url) overrides the API origin if you run a self-hosted server.

MCP

Send the key as a Bearer header on every request:

POST https://dlazy.com/mcp
Authorization: Bearer sk-xxxx

https://...?pid=<projectId> scopes generations to a project; models=a,b narrows the exposed tool set; generate=true enables auto-generate hints.