Swylink Docs
CLI setup, auth, keys, and IDE wiring
Runtime

Install and Verify

The CLI can run through npx, which keeps onboarding light for MVP users and avoids stale global installs.

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

Verify Node and CLI access

You do not need a global install for the first run. `npx` is enough.

CLI
Node version
node --version
CLI
CLI help
npx @swylink/cli --help
Section

When to pin a version

For team rollouts, pin the CLI version in IDE configs or internal docs once you validate a production release.

  • Use `npx -y @swylink/cli@<version>` if you need deterministic onboarding
  • Keep the backend and docs aligned before rotating production instructions
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.