MCP Setup

Use the installer in MCP mode for local host wiring:

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

The installer installs the CLI package, then MCP-mode setup writes supported host configuration and installs bundled skills where the host supports them. MCP-only setup does not configure CLI runtime authentication. Use this path when you want your agent to call Flywheel tools directly instead of shell 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 Codex in remote shells, select the host explicitly and use device auth:

curl -fsSL https://flywheel.paradigma.inc/install | sh -s -- \
  --mode mcp \
  --codex --yes --install-skill \
  --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 SetupCopy Anchor Link

Ask your MCP host to list available tools, then call flywheel_get_contract with {}. A successful response verifies that the host can authenticate and call Flywheel. Listing tools alone does not prove that an authenticated call works.

flywheel auth:status checks CLI credentials, not the host's MCP connection. It can report missing CLI configuration after a successful MCP-only setup. If the host cannot call Flywheel, use MCP troubleshooting and confirm its server URL is exactly https://flywheel.paradigma.inc/mcp-server.

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