# Flowboost MCP

> Use Flowboost and Wolfy from Claude, Claude Code or Codex, signed in with your own Flowboost account.

Flowboost has an **MCP server**, so an AI app such as Claude, Claude Code or Codex can work with
your Flowboost workspace for you. Once connected, it can:

- Read your organisations, projects, automations, reports and Labelizers with their runs.
- Create a project and link one of your Google Ads accounts to it. Connecting Google itself still happens in Flowboost.
- Rename, remove or restore projects, manage their guests and contacts, and group projects under a manager project.
- Manage organisation invitations and members, change Member and Admin roles, and configure Slack insights using an existing Slack connection. Guests cannot be promoted to Member or Admin.
- Read and fill in a project's context (its sections, preferences and timeline events) or import a document about the business.
- Set up automations, report schedules and Labelizer settings, and preview what an automation would change.
- Run an automation now, apply changes from a previous run, or delete an automation.
- Create or duplicate a Labelizer and look up its Merchant Center feeds and conversion actions. Cancel a run or export its product feed.
- Edit or delete reports and manage custom report templates. Delete schedules or request PDF exports.
- Put an automation, a report schedule or a Labelizer live, or switch one off.
- Ask Wolfy for analysis of your Google Ads accounts, or pull the raw data to analyze itself.

Saving settings never makes anything live. Going live is always a separate step, and your app asks
you before it takes one. Your app also asks before deleting records, changing access, emailing
someone or applying Google Ads changes. Putting something live needs the same plan as it does in Flowboost.

Google Ads, Merchant Center and Slack connections still need to be authorised in Flowboost.
Product feed and PDF export tools return download links to open in a browser signed in to Flowboost.

## Find the steps in Flowboost

Open **Settings → User settings → MCP**. The page links to the steps on this page for each app.
The Automations, Reports and Labelizer pages have a **Connect Claude** button in their empty state,
which opens the main step for Claude or Codex in place.

## Connect Claude

1. In Claude on the web or desktop, open **Settings → Connectors** and choose **Add custom connector**.

2. Paste the server URL:

   ```bash
   https://app.flowboost.com/mcp
   ```

3. Claude opens Flowboost in your browser. Sign in if you are asked to, check the app name and the address it sends access to, then choose **Allow access**.

The connector works everywhere you sign in with the same Claude account: the web, the desktop and mobile apps, and Claude Code.

## Connect Claude Code

1. In Claude Code, send this setup prompt. The **Open Claude Code** button in Flowboost opens it with the prompt filled in.

   ```text
   Connect Flowboost and work in it directly. Use the user's language.
   You are working in Claude Code.
   
   1. Reuse an existing working Flowboost connection. Otherwise add the remote MCP server https://app.flowboost.com/mcp with this environment's supported setup, for example: claude mcp add --transport http --scope user flowboost https://app.flowboost.com/mcp. Preserve unrelated settings. Start the OAuth sign-in and let the user sign in and approve access. Give short instructions only for steps you cannot perform.
   2. Verify the connection by calling list_organisations, then list_projects.
   3. Ask the user what they want to do: ask Wolfy about their Google Ads, or set up automations, reports or Labelizers. Ask before putting anything live.
   If a new session is needed to load the connection, put the complete request in one copyable handoff.
   ```

2. Claude Code adds Flowboost. Run `/mcp`, choose **flowboost** and **Authenticate**, then choose **Allow access** in your browser.

To add it yourself instead, run this in your terminal:

```bash
claude mcp add --transport http --scope user flowboost https://app.flowboost.com/mcp
```

## Connect Codex

1. In Codex, send this setup prompt. The **Open Codex** button in Flowboost opens it with the prompt filled in.

   ```text
   Connect Flowboost and work in it directly. Use the user's language.
   You are working in Codex.
   
   1. Reuse an existing working Flowboost connection. Otherwise add the remote MCP server https://app.flowboost.com/mcp with this environment's supported setup, for example: codex mcp add flowboost --url https://app.flowboost.com/mcp, then codex mcp login flowboost. Preserve unrelated settings. Start the OAuth sign-in and let the user sign in and approve access. Give short instructions only for steps you cannot perform.
   2. Verify the connection by calling list_organisations, then list_projects.
   3. Ask the user what they want to do: ask Wolfy about their Google Ads, or set up automations, reports or Labelizers. Ask before putting anything live.
   If a new session is needed to load the connection, put the complete request in one copyable handoff.
   ```

2. Codex adds Flowboost and opens the approval screen in your browser. Sign in if you are asked to and choose **Allow access**.

To add it yourself instead, run these in your terminal:

```bash
codex mcp add flowboost --url https://app.flowboost.com/mcp && codex mcp login flowboost
```

The Codex app, the Codex CLI and the Codex IDE extension share their MCP settings, so you connect once on each computer.

## What an app can reach

An app acts as you. It reaches the organisations where you are an Owner, Admin or Member and every
project in them. Guest access stays in Flowboost and is unavailable through MCP. Removing you from
an organisation removes its access there too. Every change it makes
is recorded against your account, the same as a change you make in Flowboost.

When you belong to more than one organisation, tell the app which one you mean, or let it list your
organisations first.

## See and disconnect connected apps

**Settings → User settings → MCP** lists every app you approved, where it sends access,
when you connected it and when it was last active. Choose **Disconnect** to remove one. It loses
access at once, and you have to approve it again to use it again.

## Project context

Your app can read what Wolfy knows about a project and add to it. What you tell it in the
conversation is saved as you said it. Anything it works out by itself only fills empty fields, and
a change to a value you already have, or to goals, budget or constraints, waits as a suggestion.

To bring in context you keep elsewhere, such as a client brief or old notes, ask the app to import
the document. Everything it finds becomes a suggestion. Review them on the project's **Context**
page, in the **Suggestions** tab. Each change shows in the **History** tab, where you can undo it.

## Asking Wolfy

Wolfy takes a few minutes to answer, so your app starts the question and then checks back for the
answer. To keep a follow up question in the same Wolfy conversation, the app passes the same
conversation id each time, the way a chat thread keeps its context.