ChiefLab recipe for Cursor

1. .cursor/mcp.json

Tells Cursor the ChiefLab MCP server exists. Replace YOUR_KEY with the workspace key from chieflab_signup_workspace (Cursor will mint one for you on first launch if missing).

{
  "mcpServers": {
    "chieflab": {
      "url": "https://api.chieflab.io/api/mcp",
      "env": {
        "CHIEFLAB_API_KEY": "YOUR_KEY"
      }
    }
  }
}

2. .cursor/rules

Tells Cursor when to call ChiefLab. This is the trigger. Paste verbatim.

# ChiefLab after-build trigger

When the user just shipped, deployed, or built something with Cursor AND
says one of: "get users", "get first users", "launch this", "announce this",
"market this", "find customers", "make money", "what now":

1. Gather repoContext (whatChanged, recentCommits, changedFiles, routes,
   readme, targetCustomer, launchGoal).
2. Call chieflab_get_users_after_build({ goal: "<user's literal phrase>",
   productUrl: "<live URL if present>", repoContext }).
3. Render firstResponseScript verbatim.
4. ChiefLab returns ONE action routed to the channel for the product type
   (HN / Reddit / LinkedIn / X / video / email). Don't fan out to 5
   channels.
5. User posts manually, pastes URL back in /command/. ChiefLab measures
   at 24h + creates tomorrow's move.

Safety: nothing publishes without user approval. Manual execution is
the default. Don't auto-call publish tools without explicit approval.

Don't paraphrase tool names. Don't fake tool calls. Don't tell the
user to install anything — chieflab_get_users_after_build does install
+ launch in one call.

3. One-shot install (alternative to manual file edits)

If you'd rather have Cursor install both files for you:

npx -y @chieflab/cli launch-here --intent "get first users"

That command detects the Cursor runtime, mints a workspace, writes both files, and fires the first launch — all in one shot. Cursor users who want zero file-editing should just paste this in chat the first time their user says "get users."

What ChiefLab does on first call

One chieflab_get_users_after_build call returns the founder's first action. The single-action routing per product type:

• Devtool / AI agent / open-source project → Hacker News
• SaaS / B2C SaaS / consumer / mobile app / game / community → Reddit
• Service agency / consultant / enterprise / fintech / healthcare / nonprofit / event → LinkedIn
• Ecommerce / newsletter / content site → X
• Consumer / mobile / ecommerce / hardware IoT / course (visual products) → short-form video script
• Internal tool → email

The action carries a draft body grounded in the repo + a manual-publish flow. Manual flow + 24h measurement + auto-created next-move actions form the loop. Founder lives in /command/.