MCP

Connect Your IDE

Each IDE uses a slightly different MCP config file, but the bridge command stays consistent: run Swylink over stdio with a setup token and an explicit IDE identifier.

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

Update the MCP config file

Edit .cursor/mcp.json for the selected IDE and paste the Swylink server block below.

CLI

Selected IDE config

{
  "mcpServers": {
    "swylink": {
      "command": "npx",
      "args": [
        "-y",
        "@swylink/cli",
        "start",
        "--ide",
        "cursor"
      ],
      "env": {
        "SWYLINK_SETUP_TOKEN": "YOUR_SWYLINK_SETUP_TOKEN"
      }
    }
  }
}

Section

Resulting bridge command

This is the exact command your IDE will execute once the MCP config is in place.

CLI

Bridge command

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

Section

Supported IDEs

Swylink supports all major MCP-capable IDEs. Use the IDE selector above to see the config for each one.

Cursor — `.cursor/mcp.json`
Claude Code — `.mcp.json`
Antigravity (Gemini) — `~/.gemini/antigravity/mcp_config.json`
OpenAI Codex — `~/.codex/config.toml`
Windsurf — `~/.codeium/windsurf/mcp_config.json`
Cline / RooCode — `~/.cline/data/settings/cline_mcp_settings.json`
GitHub Copilot — `.vscode/mcp.json`

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.