MCP Setup

Use the installer in MCP mode for local host wiring:

curl -fsSL https://flywheel.paradigma.inc/install | sh -s -- --mode mcp

Setup installs the Flywheel runtime, writes host config for supported MCP clients, and installs bundled Flywheel skills where the host supports them. Use this path when you want your agent to call Flywheel tools directly instead of shelling out to flywheel commands.

On Windows, run setup in the same environment that launches your host. Use WSL for WSL-launched hosts and native PowerShell for native Windows hosts; the two environments write separate host config files.

In native PowerShell, use npm/npx instead of the POSIX shell installer:

npx --yes @paradigma-inc/flywheel@latest setup --mode mcp

For web connector hosts, use the host-native connector UI and provide:

https://flywheel.paradigma.inc/mcp-server

For remote shells, use device auth:

curl -fsSL https://flywheel.paradigma.inc/install | sh -s -- \
  --mode mcp \
  --auth-mode device \
  --base-url https://flywheel.paradigma.inc

Device auth prints an approval URL and setup code, then polls until the API key is issued. It is the right choice when the browser that completes auth is not running on the same machine as the installer. If browser auth does not open from WSL, copy the printed approval URL and setup code into your Windows browser.

Verify Setup

After setup, confirm both the CLI and your host can see Flywheel:

flywheel auth:status
flywheel help

Then ask your MCP host to list available tools. You should see Flywheel tool names such as graph, artifact, hook, and compute operations. If the host cannot see them, use MCP troubleshooting and confirm the configured server URL is exactly https://flywheel.paradigma.inc/mcp-server.

For setup flags and uninstall flags, see the generated CLI reference.