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/functions/v1/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 tokenLink to this section
- Go to app.flyweel.co
- Click Settings → API & MCP
- Under Advanced: use an API key instead, click Generate API key (or Create Token to name your own)
- Copy the
fwl_…token once — it won’t be shown again
Step 2: Open your Continue configLink to this section
Global config lives at ~/.continue/config.yaml. Per-assistant config can also live in the Continue Hub.
Step 3: Add Flyweel under mcpServersLink to this section
mcpServers: - name: flyweel-mcp-server type: streamable-http url: https://api.flyweel.co/functions/v1/mcp-server/mcp requestOptions: timeout: 30000 headers: X-API-Key: fwl_YOUR_TOKEN_HEREReplace fwl_YOUR_TOKEN_HERE with your token.
Using secrets (recommended)Link to this section
Keep the token out of the file by referencing a secret:
mcpServers: - name: flyweel-mcp-server type: streamable-http url: https://api.flyweel.co/functions/v1/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 ContinueLink to this section
Continue picks up config changes live. If tools do not appear, run Continue: Reload from the command palette.
Step 5: Test itLink to this section
In Continue’s chat, ask:
What Google Ads accounts do I have connected to Flyweel?TroubleshootingLink to this section
YAML parse errorLink to this section
Indentation mismatch. YAML is whitespace-sensitive.
Fix: Use exactly 2-space indentation and no tabs. Paste into a YAML linter if unsure.
”Authentication error”Link to this section
Token is invalid, revoked, or malformed.
Fix: Regenerate at app.flyweel.co, then Settings → API & MCP.
Tools not loadingLink to this section
Continue has not refreshed the tool list.
Fix: Reload the Continue extension, or restart VS Code / JetBrains.