@flowboost/mcp

One command to connect Claude Code to Wolfy.

npx @flowboost/mcp <your-wolfy-api-key>

That's it. Given your Wolfy API key it:

1. Registers the wolfy MCP server (user scope) — claude mcp add --transport http ….
2. Raises MCP_TOOL_TIMEOUT to 600000ms (10 min) in ~/.claude/settings.json, merge-preserving any existing settings — reports can take minutes and the default timeout would cut them off.
3. Installs the wolfy-analyst and wolfy-data-retrieval sub-agents into ~/.claude/agents/ (or the project's .claude/agents/ if you choose).

Then restart Claude Code, run /mcp, and you should see wolfy ✓ connected with the Wolfy tools (ask_wolfy, retrieve_wolfy_data, get_wolfy_query_results, get_wolfy_fixed_tool_results).

Getting an API key

Can't be automated — generate it in the Wolfy web app:

Settings → API Keys → Generate key (copy it immediately; it's shown only once).

The key is tied to your Wolfy account — it uses your connected Google Ads accounts and counts against your plan/billing. Don't share it.

Options

npx @flowboost/mcp <api-key> [options]

  --url <url>     Gateway MCP URL (default: the production gateway)
  --scope <s>     Sub-agent location: user (default) | project
  --no-timeout    Skip the MCP_TOOL_TIMEOUT change
  --no-agent      Skip installing the Wolfy sub-agents
  -y, --yes       Don't prompt; accept defaults
  -h, --help      Show help

The key can also be supplied via the WOLFY_API_KEY env var, and the gateway URL via WOLFY_GATEWAY_URL (useful for the dev / acp gateways).

Requirements

• Node 18+ (run via npx, no install needed)
• The claude CLI on your PATH (Claude Code)

Development

This package lives in the Wolfy backend repo alongside gateway/ so the gateway URL and the sub-agent definitions stay in sync with the service they target. Edit prompts in templates/wolfy-analyst.md (finished reports) and templates/wolfy-data-retrieval.md (raw data).

Publishing is automated by .github/workflows/publish-cli.yml via npm Trusted Publishing (OIDC, no token). Bump version in package.json, then push a matching cli-v* tag:

npm version patch          # or minor / major
git push && git push --tags

# local smoke test
node bin/mcp.js --help