# growth.engineer

> MIT agent-readable GTM catalog — tools, functions, workflows via MCP

**Category:** AI Agents  
**Pricing:** open-source  
**URL:** https://www.growth.engineer  
**GitHub:** https://github.com/GetBrew/growth-engineer  
**Added:** 2026-10-04

---

## The Hook

growth.engineer is a MIT catalog of go-to-market tools and workflows written as markdown files agents can run — connect once to the read-only MCP and stop scraping human docs for “which key, which endpoint, what it costs.”

## What's Good

MIT (GetBrew/growth-engineer). Live site + MCP at `https://www.growth.engineer/mcp` (HTTP 200); Claude Code / Codex / Cursor HTTP MCP one-liners in README. Catalog entries and workflows are files in the repo; self-host with `pnpm dev` if you want your own origin. ★~138.

## The Catch

Read-only catalog MCP — it does not execute vendor APIs for you; you still need each tool’s own keys when a workflow says so. Vs Apify MCP / generic awesome-lists: Apify runs Store Actors; this catch is GTM tool+workflow markdown as MCP prompts/tools. Vendor accuracy drifts — treat entries as starting maps, pin commits if you fork.

## Verdict

MIT GTM catalog MCP when agents need operator maps for growth tools — not Apify scrape Actors and not a static awesome-list dump.