Swylink Terminal Docs

CLI Getting Started

Install the CLI, authenticate in your terminal, generate a setup token in the dashboard, and connect your IDE with guided bootstrap.

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

What you need

Swylink CLI is designed for local IDE integrations. You authenticate once in the terminal, create a one-time setup token in Dashboard -> Connections, and bootstrap a local device credential.

Node.js 20 or newer on the machine running the IDE
A Swylink account with an active session you can log into
An active Swylink subscription before creating setup tokens or starting the bridge
An IDE that supports MCP over stdio (Cursor, Claude Code, Codex, Windsurf, Antigravity, Cline/RooCode, or GitHub Copilot)

Section

Happy path

This is the shortest secure path from zero to a live IDE connection.

Why guided setup matters

Setup tokens are one-time bootstrap credentials. After first use, Swylink stores a local device credential and avoids long-lived secrets in command arguments.

CLI

Authenticate

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

CLI

Generate setup token

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

CLI

Attach the bridge to your IDE

SWYLINK_SETUP_TOKEN=YOUR_SWYLINK_SETUP_TOKEN npx -y @swylink/cli start --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.