# AI use cases for Growth Engineer (GetBrew/growth-engineer) Repo: [GetBrew/growth-engineer](https://github.com/GetBrew/growth-engineer) | Use cases: 4 | Page: https://dedupedai.com/use-cases/getbrew-growth-engineer/ growth.engineer is an open-source catalog of go-to-market companies, tools and workflows, written as markdown files that AI agents can follow, with a read-only MCP server. This file holds every use case of this repo. Each one starts with a "## " heading and ends with its URL. - Connect an agent to the growth.engineer catalog: https://dedupedai.com/use-cases/getbrew-growth-engineer/connect-agent-to-go-to-market-catalog/ - Run a funding-signal outbound workflow with an agent: https://dedupedai.com/use-cases/getbrew-growth-engineer/run-workflow-file-in-agent/ - Add a company and its tools to the catalog: https://dedupedai.com/use-cases/getbrew-growth-engineer/add-tool-or-company-to-catalog/ - Give an agent the full catalog in one document: https://dedupedai.com/use-cases/getbrew-growth-engineer/load-whole-catalog-into-agent-context/ ## How to connect an agent to the growth.engineer catalog with Growth Engineer Repo: [GetBrew/growth-engineer](https://github.com/GetBrew/growth-engineer) | Difficulty: Beginner | Time: 15 minutes | Basis: From the README Add the read-only MCP server so an agent can search workflows, tools and companies. **Who it is for:** A marketer or founder who wants their agent to look up go-to-market plays without copying docs by hand. **The problem:** Vendor docs are written for people, and growth plays often live in private notes an agent cannot read. **The outcome:** The agent can search the catalog and fetch any workflow, tool or company file through the growth.engineer MCP server. ### Steps 1. In Claude, open Settings, choose Connectors, click Add, then Add custom connector. 2. Name it growth.engineer, paste https://www.growth.engineer/mcp and click Add. 3. For Claude Code, run `claude mcp add --transport http growth-engineer --scope user https://www.growth.engineer/mcp`. 4. For Codex, run `codex mcp add growth-engineer --url https://www.growth.engineer/mcp`. 5. Ask the agent to search the catalog for a goal, such as funding signals, and to open the matching workflow with get. ### Prompt to paste into your agent ```text Use the growth-engineer MCP server at https://www.growth.engineer/mcp to search for workflows about . Return the title and key of each match and open the first one with get. Check that the returned file has a title, inputs and steps before you report back. ``` ### Caveat The server is read-only for search and get, but the submit_feedback tool sends your text to the maintainers, so do not include private data in feedback. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/getbrew-growth-engineer/connect-agent-to-go-to-market-catalog/ ## How to run a funding-signal outbound workflow with an agent with Growth Engineer Repo: [GetBrew/growth-engineer](https://github.com/GetBrew/growth-engineer) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Paste a workflow file into an agent that asks for inputs before it sends or spends. **Who it is for:** A sales lead who has a target list and wants an agent to run a repeatable outbound play step by step. **The problem:** A working growth play usually lives in someone's notes, where no agent can run it. **The outcome:** The agent asks for the workflow inputs, sets up each tool, runs the steps and stops for approval before any message is sent, money is spent or data is changed. ### Steps 1. Fetch the workflow with `curl https://www.growth.engineer/workflows/funding-signal-outbound.md`. 2. Paste the file into your agent, or add the workflow as an MCP prompt if you use the connector. 3. Answer the inputs the agent asks for, such as your target segment and your ideal customer profile. 4. Connect each tool the workflow names, using the credential that the company file lists. 5. Review each draft or action the agent proposes and approve it before the agent continues. ### Prompt to paste into your agent ```text Read the funding-signal-outbound workflow from https://www.growth.engineer/workflows/funding-signal-outbound.md, ask me for every input it lists, and run its steps in order. Before any message is sent, money is spent or data is changed, stop and ask me, then report each completed step with its result. ``` ### Caveat The README says the file tells the agent to ask before it sends a message, spends money or changes data, but the workflow still runs real vendor calls once you approve them. Risk, credentials: The workflow needs API keys or logins for each vendor tool it calls, so store those keys in your agent's secret settings and not in the pasted file. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/getbrew-growth-engineer/run-workflow-file-in-agent/ ## How to add a company and its tools to the catalog with Growth Engineer Repo: [GetBrew/growth-engineer](https://github.com/GetBrew/growth-engineer) | Difficulty: Intermediate | Time: 60 minutes | Basis: From the README Open a pull request that adds a company file and its tool files, checked by pnpm. **Who it is for:** A developer or go-to-market engineer who uses a vendor tool that the catalog does not yet cover. **The problem:** An agent cannot call a tool that has no file, and the vendor's docs do not say which key, endpoint or MCP server to use. **The outcome:** A pull request that adds a validated company file and tool files, with each tool linking the docs page that documents its call. ### Steps 1. Run `pnpm install` in your clone of the repository. 2. Use the research-company skill in .agents/skills/research-company/SKILL.md, or follow companies/README.md, to write companies//company.md and tools/.md. 3. Link the vendor docs page that documents each tool's call. 4. Run `pnpm content:check` and fix every problem it reports, with each one tied to its file. 5. Open a pull request, since CI runs the same check. ### Prompt to paste into your agent ```text In the growth-engineer repository, use the research-company skill to add a company file and its tool files for , citing the vendor's own documentation for each tool. Run pnpm content:check and report the result, and do not finish until it passes. ``` ### Caveat The README says facts come from each vendor's own documentation, so an entry is only as current as the docs page it links. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/getbrew-growth-engineer/add-tool-or-company-to-catalog/ ## How to give an agent the full catalog in one document with Growth Engineer Repo: [GetBrew/growth-engineer](https://github.com/GetBrew/growth-engineer) | Difficulty: Intermediate | Time: 30 minutes | Basis: From the README Load llms-full.txt, or run the site locally, so an agent can reason over every file. **Who it is for:** A team lead building an internal agent who needs every company, tool and workflow in one place. **The problem:** Fetching files one at a time is slow, and the agent may miss a tool that fits the job. **The outcome:** The agent has one document with every company, tool and workflow file and can choose which play fits a goal. ### Steps 1. Fetch the full catalog with `curl https://www.growth.engineer/llms-full.txt`. (inferred, check the README) 2. Save the output to a file and attach it to your agent's context or project. 3. Ask the agent to list the workflows whose inputs you already have. (inferred, check the README) 4. To run the site locally, run `pnpm install` and then `pnpm dev`. 5. Open http://localhost:3000 and add .md to any company, tool or workflow URL to see the file an agent gets. ### Prompt to paste into your agent ```text Read the catalog at https://www.growth.engineer/llms-full.txt and list every workflow whose inputs match . Report the workflow titles and the tools each one uses, and confirm that each title appears in the document before you list it. ``` ### Caveat The full document is generated from the catalog at build time, so it shows the published state of the site and not any unmerged pull request. Disclaimer: Third-party repos we don't own or vouch for. AI-generated use cases can be wrong: review everything and run at your own risk. Full text: https://dedupedai.com/disclaimer/ URL: https://dedupedai.com/use-cases/getbrew-growth-engineer/load-whole-catalog-into-agent-context/