Wolfy MCP
Query Wolfy and your Google Ads data from Claude, Cursor, or any MCP client.
The Wolfy gateway exposes your Wolfy agent to external tools like Claude Code as Streamable HTTP MCP tools. Instead of switching to the chat UI, an MCP client can ask Wolfy a question directly and get back its written answer, or pull raw Google Ads data to analyze itself.
Install the MCP server
Run the install command from Settings → Organisation settings → MCP, then create an API key on that same page to authenticate it.
Wolfy MCP server
Run this in your terminal to install the MCP server, then authenticate it with an API key from the MCP settings.
How a request is authorized
Every request is authenticated with a Wolfy API key, issued from Settings → Organisation
settings → MCP in Flowboost and sent as a bearer token (Authorization: Bearer <key>), never as a tool argument.
The gateway only ever stores a hash of the key, and resolving it gives:
- The organisation the key belongs to. This is what the key can actually reach: every Google Ads account connected to a project under that organisation, regardless of who is calling.
- The user who created the key, used only for usage accounting (token cost, plan limits).
Because authorization is organisation-wide rather than tied to a UI-selected project, a caller
just needs to pass which account it means (client_id and manager_id if it sits under an MCC)
on each call.
Available tools
| Tool | What it does |
|---|---|
ask_wolfy | Runs the full Wolfy agent on your question and returns its written, user-visible answer, the same kind of response you'd get in chat. |
retrieve_wolfy_data | Runs Wolfy's data retrieval without the report writer, so the calling LLM (not Wolfy) writes the analysis. Returns a summary; full rows are fetched with the two tools below. |
get_wolfy_query_results | Fetches full raw rows for a GAQL query previously run via retrieve_wolfy_data. |
get_wolfy_fixed_tool_results | Fetches full raw rows for one of Wolfy's fixed data-retrieval tools (as opposed to an ad-hoc GAQL query). |
list_connected_accounts | Lists the Google Ads accounts your API key can currently reach. |
submit_wolfy_feedback | Sends feedback on a Wolfy answer back to the team. |
ask_wolfy and the retrieve_wolfy_data family run against two independent engines under the
hood, so if you only need numbers to work with yourself, retrieve_wolfy_data avoids paying for a
report Wolfy writes and you then ignore.
Conversations carry state
Pass a stable conversation_id across related calls and the gateway keeps them coupled to the
same underlying Wolfy session, so a follow-up question keeps its account focus and any data
already retrieved, the same way a chat thread would.
Rate limits
Requests are rate-limited per user (sustained requests/min, with a small burst allowance on top). If you're scripting a lot of calls in a loop, space them out rather than firing them all at once.