Guided Setup

Generate Setup Tokens

Create one-time setup tokens in Dashboard -> Connections. The CLI exchanges them for local device credentials and reuses them automatically.

Selected IDE

Cursor

.cursor/mcp.json

Swylink keeps the bridge explicit for this IDE by rendering --ide cursor and the correct MCP config path everywhere in the docs.

Section

Bootstrap a new device

Generate a setup token in Dashboard -> Connections and run the bridge once with that token.

Token hygiene

Setup tokens are one-time and short-lived. If a device is compromised, revoke the generated device credential from the dashboard connections view.

CLI

Create setup token

# Dashboard -> Connections -> Generate setup token for cursor

CLI

Use token on first start

SWYLINK_SETUP_TOKEN=YOUR_SWYLINK_SETUP_TOKEN npx -y @swylink/cli start --server wss://api.swylink.com/ws --ide cursor

Section

For CI/CD or automated environments, you can store the setup token in a file instead of an environment variable.

File vs environment variable

The `--setup-token-file` flag reads the token from a file. This avoids exposing the token in process arguments or shell history.

CLI

Token file

npx -y @swylink/cli start --setup-token-file /path/to/token.txt --server wss://api.swylink.com/ws --ide cursor

Continue

Move through the full CLI path from auth to IDE connection, or jump back to the start if you are documenting onboarding for a new user.