Use Cursor Automations for Agentic Stale Feature Flag Removal

Описание: 70% of feature flags are never removed from codebases. They accumulate technical debt and eventually cause failures. Removing them is tedious, so nobody does it.

Cursor just launched Automations—cloud agents that run on a schedule or in response to events. One of the sample automations is "cleanup feature flags." But the prompt has a problem: how does the agent know which flags are stale?

In this video, I modify Cursor's cleanup automation to use GrowthBook's MCP server, which has a stale flag detection tool that gives the agent the exact context it needs. The result: a weekly automation that fetches all flags from GrowthBook, cross-references them in the codebase, identifies which ones are stale (and what values to replace them with), then opens a PR removing 9 stale flags—all autonomously.

No toy project. This is running against GrowthBook's real production codebase.

Links
GrowthBook MCP Server Docs: https://docs.growthbook.io/integratio...
GrowthBook MCP Server on GitHub: https://github.com/growthbook/growthb...
GrowthBook MCP Server on npm: https://www.npmjs.com/package/@growth...

Cursor Automations Blog Post: https://cursor.com/blog/automations
Cursor Automations Docs: https://cursor.com/docs/cloud-agent/a...

Get started with GrowthBook (free): https://www.growthbook.io
GrowthBook on GitHub: https://github.com/growthbook/growthbook

Chapters
0:00 The stale flag problem
0:18 Cursor Automations and the cleanup prompt
0:42 The missing context problem
0:55 Adding GrowthBook's MCP server
1:18 Modifying the automation steps
1:50 Running the automation
2:05 Results: flag detection and staleness analysis
2:45 Code changes and the PR
3:25 CI/CD checks and review
3:40 Wrap up