Reference

Command Reference

These are the operational commands you need for day-to-day CLI use.

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

Authentication

Use these commands to manage the local terminal session.

CLI

npx @swylink/cli auth login --api-base-url https://api.swylink.com

CLI

Who am I

npx @swylink/cli auth whoami --api-base-url https://api.swylink.com

CLI

Logout

npx @swylink/cli auth logout

Section

Guided setup and bridge

Use guided setup tokens to bootstrap each IDE/device and start the bridge.

CLI

Generate setup token

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

CLI

Start bridge

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

CLI

Start with token file

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

CLI

Start with profile

npx -y @swylink/cli start --server wss://api.swylink.com/ws --ide cursor --profile my-team

CLI

Start with language

npx -y @swylink/cli start --server wss://api.swylink.com/ws --ide cursor --lang pt

Section

Diagnostics

Use the doctor command to check for MCP config conflicts and verify your IDE setup.

When to use doctor

Run doctor when your IDE stays offline or you suspect a config conflict. It checks MCP config file paths, validates the server block, and reports any issues.

CLI

Run doctor

npx @swylink/cli doctor --ide cursor

CLI

Doctor with profile

npx @swylink/cli doctor --ide cursor --profile my-team

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.