To connect Flyweel MCP to Continue.dev, add a streamable-http MCP server to your Continue config.yaml with url set to https://api.flyweel.co/mcp-server/mcp and an X-API-Key header. Continue supports secret interpolation, so you can keep your token out of version control.

Step 1: Get your API token

Go to app.flyweel.co
Click Settings, then API Tokens
Click Create New Token, name it “Continue”
Click Generate and copy the fwl_… token

Step 2: Open your Continue config

Global config lives at ~/.continue/config.yaml. Per-assistant config can also live in the Continue Hub.

Step 3: Add Flyweel under mcpServers

mcpServers:
  - name: Flyweel
    type: streamable-http
    url: https://api.flyweel.co/mcp-server/mcp
    requestOptions:
      timeout: 30000
      headers:
        X-API-Key: fwl_YOUR_TOKEN_HERE

Replace fwl_YOUR_TOKEN_HERE with your token.

Using secrets (recommended)

Keep the token out of the file by referencing a secret:

mcpServers:
  - name: Flyweel
    type: streamable-http
    url: https://api.flyweel.co/mcp-server/mcp
    requestOptions:
      headers:
        X-API-Key: ${{ secrets.FLYWEEL_API_KEY }}

Set FLYWEEL_API_KEY in Continue’s secret store (Continue Hub, or ~/.continue/secrets).

Step 4: Reload Continue

Continue picks up config changes live. If tools do not appear, run Continue: Reload from the command palette.

Step 5: Test it

In Continue’s chat, ask:

What Google Ads accounts do I have connected to Flyweel?

Troubleshooting

YAML parse error

Indentation mismatch. YAML is whitespace-sensitive.

Fix: Use exactly 2-space indentation and no tabs. Paste into a YAML linter if unsure.

”Authentication error”

Token is invalid, revoked, or malformed.

Fix: Regenerate at app.flyweel.co, then Settings, then API Tokens.

Tools not loading

Continue has not refreshed the tool list.

Fix: Reload the Continue extension, or restart VS Code / JetBrains.

Continue.dev