Skip to content

Windsurf ChiefLab chieflab_continue_launch_loop

How to: Windsurf ChiefLab chieflab_continue_launch_loop

client:Windsurf transport:streamable-http tool:chieflab_continue_launch_loop

Add ChiefLab to Windsurf

  1. 01

    Open ~/.codeium/windsurf/mcp_config.json and merge this in. Keep any servers already there.

{
  "mcpServers": {
    "chieflab": {
      "serverUrl": "https://api.chieflab.io/api/mcp"
    }
  }
}
  1. 02

    Save the file and restart Windsurf.

  2. 03

    Ask for something chieflab_continue_launch_loop does. Windsurf lists the server's tools on connect and calls chieflab_continue_launch_loop itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that ChiefLab's identifier in your config matches the one above exactly.

Global only — Windsurf has no per-project MCP config. Refresh Cascade after saving. Windsurf docs

Set these first

ChiefLab will not start until these are set, so chieflab_continue_launch_loop never becomes available.

  • CHIEFLAB_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.