Add ChiefLab to Base44
Base44 ships full-stack apps generatively. ChiefLab adds the post-build last mile — positioning, briefs, on-brand graphics, real publish via Zernio, real email via Resend, 24h post-launch metrics. One MCP connection, then your Base44 agent has 72 launch tools available.
Try first: run ChiefMO in your browser. Same output your Base44 agent will see.
Step 1 — Get an API key
One click at chieflab.io/get-key. Save the clp_dev_ key.
Step 2 — Add the MCP server in Base44
Open your Base44 project → Settings → MCP / Connectors / Tools → Add server.
- Type: HTTP MCP server
- URL:
https://chieflab.io/api/mcp - Auth header:
Authorization: Bearer clp_dev_<your-key> - Save → Base44's agent reads the 72 ChiefLab tools on next message.
If Base44 doesn't yet expose raw MCP server URLs in your build, fall back to direct HTTPS calls from your Base44 backend — POST to https://chieflab.io/api/mcp with the Bearer key.
Step 3 — Try the closed loop
I just shipped this Base44 app at <url>. Use ChiefMO to launch it. Base44 picks chiefmo_launch_product, returns a launch pack + signed reviewUrl. Approve in browser. Base44 fires chiefmo_publish_approved_post + chiefmo_send_approved_email for each approved action.
Multi-tenant: serving Base44 end-users
If your Base44 app serves multiple end-users (each with their own brand), provision a tenant per user the first time they ask to launch:
chieflab_create_tenant({ tenantId: user.id, name: user.brand, domain: user.domain })
chieflab_set_tenant_context({ tenantId: user.id, brand, voice, audience, pillars })
chiefmo_launch_product({ tenantId: user.id, productUrl, goal }) Same as everywhere else
- For agents (instruction text): /for-agents
- Tool catalog: /llms.txt · /.well-known/mcp.json
- Other runtimes: Cursor · Claude Desktop · Codex · Lovable · Bolt · OpenClaw · Hermes
- SDK alternative for serverside:
npm install @chieflab/sdk