ChiefLab
/
activation console
Paste your product URL. We run the actual launch loop in a shared sandbox — same 13 skills, same per-channel drafts your agent would render. If you like what you see, create a workspace key and your IDE agent picks up where the preview left off.
// sandbox is read-only — nothing publishes. With your own workspace, the same drafts come back wired to approval-gated publish actions.
You can still — sandbox is decorative.
We will show the right config after your workspace key is created.
So the launch loop picks the right channels. One click.
Email is optional — only used for run digests + critical security alerts. Leave blank to stay anonymous.
rate-limit: 5 keys / ip / hour · no card · free tier
Copy once — never shown again. Paste into your MCP config (snippet below) and your agent can call ChiefLab.
// ~/.cursor/mcp.json
{
"mcpServers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp",
"headers": {
"Authorization": "Bearer "
}
}
}
}# Claude Code (one command — agent-friendly, paste verbatim):
claude mcp add --transport http chieflab https://api.chieflab.io/api/mcp \
--header "Authorization: Bearer "
# Claude Desktop: paste into claude_desktop_config.json
# (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json)
# (Windows: %APPDATA%\Claude\claude_desktop_config.json)
{
"mcpServers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp",
"headers": {
"Authorization": "Bearer "
}
}
}
}// ~/.codex/mcp.json
{
"mcpServers": {
"chieflab": {
"url": "https://api.chieflab.io/api/mcp",
"headers": {
"Authorization": "Bearer "
}
}
}
}# Manual fallback when you already have a key.
# Preferred product path for a repo is launch-here:
# npx -y @chieflab/cli launch-here --intent "launch this"
# Windows PowerShell if npx is blocked by execution policy:
# npx.cmd -y @chieflab/cli launch-here --intent "launch this"
npx -y @chieflab/cli login --key
npx -y @chieflab/cli launch-here --intent "launch this"Stuck? Cursor · Claude · Codex · try in browser
If you keep hitting this, email hi@chieflab.io with the error message above and we'll look at it.