Install · Cursor

Add ChiefLab to Cursor in 60 seconds

Cursor is one of many runtimes that can call ChiefLab — see install · any agent for Telegram bots, voice agents, Python, custom SDKs, etc. Cursor has native MCP support so the install is a clean 60 seconds. Once installed, say "launch this" / "get users" / "market this" after building anything in your repo and Cursor's agent picks chiefmo_launch_product, gathers repo context, and returns a launch pack + signed reviewUrl.

Want to try it first? Run ChiefMO in your browser — no install, no API key. See exactly what your Cursor agent will get back.

Step 1 — Get an API key (60 seconds)

Go to chieflab.io/get-key. Fill the form, click. We mint your workspace and hand you a one-time delivery URL. Click it. See your key once. Copy it.

That's it. No email needed. No call. The key starts with clp_dev_ or clp_live_.

Step 2 — Add to Cursor

Open Cursor → Settings → MCP. Or edit your config file at ~/.cursor/mcp.json (create if missing).

Option A — Hosted MCP (recommended; no local install):

{
  "mcpServers": {
    "chieflab": {
      "url": "https://api.chieflab.io/api/mcp",
      "headers": {
        "Authorization": "Bearer clp_dev_<paste-your-key>"
      }
    }
  }
}

Cursor's hosted MCP support is recent. If the "url" field doesn't work in your Cursor version, update Cursor or check Cursor's MCP docs for the latest config format.

Step 3 — Restart Cursor

Fully quit Cursor (close all windows) and reopen. Open a chat — you should see ChiefLab tools in the tool picker (e.g. chiefmo_launch_product).

Step 4 — Try the killer flow (repo-aware)

From a project you just shipped, in a Cursor chat:

I just built this. Launch it.

Cursor's agent picks chiefmo_launch_product, gathers repoContext (recent commits, changed files, routes, README) and calls ChiefLab. You'll get back:

  • Positioning grounded in what you actually changed
  • Per-channel launch briefs (LinkedIn, X, Product Hunt, email, landing hero)
  • On-brand launch graphic (opt-in, ~$0.04/image via Gemini)
  • Proposed publish actions — all approval-gated
  • A signed reviewUrl like https://chieflab.io/runs/abc123?token=...

Click the reviewUrl. You'll land on a no-login page that renders the assets visually. Approve or reject. If you reject with feedback, the next run uses your feedback (per-tenant memory).

After ≥24h, ask Cursor to "check launch metrics" — it picks chiefmo_measure_launch_results and returns engagement + GA4 + Search Console + a next-iteration brief.

Multi-tenant: serving your own customers

If you're building an AI product that serves end-users, register each end-user as a tenant first:

chieflab_create_tenant({
  tenantId: "acme-co",
  name: "Acme Co",
  domain: "acme.co"
})

chieflab_set_tenant_context({
  tenantId: "acme-co",
  brand: "Acme Co",
  audience: "B2B SaaS founders",
  voice: "Direct, founder-led, no jargon"
})

Then call chiefmo_launch_product with tenantId: "acme-co" and ChiefMO grounds every output against that tenant's brand context.

Troubleshooting

  • Tools don't appear in Cursor: restart Cursor fully (close all windows + reopen). MCP config reload requires a full restart.
  • 401 Unauthorized: check the Bearer token matches your delivery URL key. Or get a new key via chieflab_signup_workspace.
  • 429 Too Many Requests: hit the per-workspace rate limit (60 calls/min). Wait or contact support.
  • Tool returns 503: the Supabase migrations haven't been applied yet. This is a server-side issue — email hi@chieflab.io.

More